Sorry for being slow to get back.
@Buckeye
After a long read through this post RouterOS bridge mysteries explained I understand why the non-management vlan interfaces are not needed on the switch. Fixed.
The duplicate ip addresses on the bridge ports was a major error. Have fixed the duplication. But I have this vague idea that the ip address is needed for routing. Your reply suggests this is not correct.
@vingjfg
I will set the admin-mac and set auto-mac=no. Also will set the ether switch ports as edge=yes. I was playing with the routes in an effort to solve some of the problems. Didn’t work. But with changes per you and @Buckeye plus fixes to issues mentioned below things are now working as expected.
I had some some fundamental problems with my setup that had nothing to do with RouterOS. They were simple engineering stupidity and should have been addressed first. Always test your test bed before assuming it works as expected!
-
I am using a pair of Windows laptops and failed to verify that Windows Defender firewall rules were appropriate to the testing setup. Pings on "public networks" were NOT allowed!
-
The sfp ports on the RB5009 and the L009 are not identical and I am not using Mikrotik sfp modules. The mismatch caused problems with traffic via the trunk setup between the sfp ports. The interconnect was at times not seen and at other times provided erratic data transfer.
The Mikrotik recommended solution:Since RouterOS v7.12
/interface
ethernet set sfp-sfpplus1 auto-negotiation=no speed=1G-baseX `Older RouterOS `
/interface
ethernet set sfp-sfpplus1 auto-negotiation=no speed=1Gbps
full-duplex=yes`
Again, thanks to each of you.