it used to be in this setup v5.xx
Port 1 master port2-5 slaved
Port 6 master port 6-10 slaved
BRIDGE port 1+6
port 11 WAN
port 12-13 unassigned
Updated to most current 5.xx, then 6.xx, updated firmware newest:
I changed it up to have NO Bridge, with 7 subnets and 5 vlans. (1 subnet for each vlan, and one for port 1 and one for port 6). NOT bridging 1and6 as no traffic needs to pass between the lan ports.
It did not used to show any stats on the slaved ports, but now it does. Any ideas why? I want to make sure the slaved ports are working correctly to make sure i am being processor efficient.
Since one of the latest RouterOS 6.x versions the traffic per port is shown, even when ports are set to have a master-port.
You probably are used to not see any traffic on any slaved ports, which was the case on RouterOS 5.x and the beginning of RouterOS 6.x.
But they made it better and included the per-interface traffic counters work even when ports are slaved.
Also, i was watching throughput earlier, and noticed that every few seconds, it would show “0” for throughput on many of the interfaces for a moment, then show the rates again.
Proc was about 30% with 120mbps throughput
wondering if this is simply the winbox view not showing things right, OR if indeed users are experiencing momentary pauses in data.
Should i bridge my 2 switch groups? I dont have any reason for data to cross them, and each switch going to this router is vlaned to its own subnet, so broadcast traffic should not be trying to cross either (causing proccessor overhead?). If i do need to access something while managing the lan, packets will jump through the processor right?
so is a bridge a good idea or not matter since i have things seperated via 2 subnets on each switch master interface?
If you have two vlan’s split over the two available switch chips and there is no reason for broadcast traffic to flow over the two switch chips I do not see any reason to bridge them. It will only cause unwanted traffic and unneeded load for the CPU.
