I think thats backwards... Personally I'd set ALL of the masters to NONE... create a bridge and place them all into it... then setup bridge rules for each traffic you want to allow... Setting the ethers master port puts them into a switch group... don't think you really want to do that here.Probably create a bridge interface. Set ether1's master port to "none", ether2's master port to "none" and then every other port's master port set to "ether2". Then put ether2 in the bridge port interface list.
Uh... didn't even think about doing it that way... much simpler ruleset... Nice job!I put all interfaces in same bridge group then did this.
/interface bridge filter
add action=drop chain=forward in-interface=!ether1 out-interface=!ether1
Seems to work.
Beautiful, yes ... I misunderstood you.I put all interfaces in same bridge group then did this.
/interface bridge filter
add action=drop chain=forward in-interface=!ether1 out-interface=!ether1
I'd suspect this kills performance for the CRS, cause as soon as you use interfaces as non switch port, everything is done in software....Beautiful, yes ... I misunderstood you.I put all interfaces in same bridge group then did this.
/interface bridge filter
add action=drop chain=forward in-interface=!ether1 out-interface=!ether1
I suspect your right but if I still get close too 1gbps out of uplink port I am not sure I care. I am sure there are better ways but this works and gives the throughput I need.I'd suspect this kills performance for the CRS, cause as soon as you use interfaces as non switch port, everything is done in software..../interface bridge filter
add action=drop chain=forward in-interface=!ether1 out-interface=!ether1
Until they implement more of the CRS feature set I don't know another way to do it...I suspect your right but if I still get close too 1gbps out of uplink port I am not sure I care. I am sure there are better ways but this works and gives the throughput I need.I'd suspect this kills performance for the CRS, cause as soon as you use interfaces as non switch port, everything is done in software..../interface bridge filter
add action=drop chain=forward in-interface=!ether1 out-interface=!ether1
I highly doubt, that you will anything even near to 1Gbps, if the CRS design was done like all aother RBs with integrated switch chip, then there is a single 1G link from the switch chip to the CPU. So if you add all ports including the uplink to a software bridge you trying to push the traffic of 24x ports through one 1G link. Even the traffic between the ports.I suspect your right but if I still get close too 1gbps out of uplink port I am not sure I care. I am sure there are better ways but this works and gives the throughput I need.I'd suspect this kills performance for the CRS, cause as soon as you use interfaces as non switch port, everything is done in software..../interface bridge filter
add action=drop chain=forward in-interface=!ether1 out-interface=!ether1
Reached 300mbps on a PPPoE connection going through it. That cap was caused by the PPPoE client router(RB2011) hitting 100 percent CPU not cloud router acting as switch. The cloud router was at about 50 percent but I think part of that was me being logged in it on winbox. Will need to find a different mikrotik box and do raw IP to see if I can do 1gps flowing through the uplink on it but I bet it comes close. Wander if turning connection tracking off would help. Mostly only seeing PPPoE packets so I am not sure what it would change.I highly doubt, that you will anything even near to 1Gbps, if the CRS design was done like all aother RBs with integrated switch chip, then there is a single 1G link from the switch chip to the CPU. So if you add all ports including the uplink to a software bridge you trying to push the traffic of 24x ports through one 1G link. Even the traffic between the ports.
I was talking about the effect bridging all ports will have. If you take a look at the picture troy linked, you will see what I'm talking about. Bridging all ports in ROS, will force them all through the 1G link to the CPU.Reached 300mbps on a PPPoE connection going through it. That cap was caused by the PPPoE client router(RB2011) hitting 100 percent CPU not cloud router acting as switch. The cloud router was at about 50 percent but I think part of that was me being logged in it on winbox. Will need to find a different mikrotik box and do raw IP to see if I can do 1gps flowing through the uplink on it but I bet it comes close. Wander if turning connection tracking off would help. Mostly only seeing PPPoE packets so I am not sure what it would change.I highly doubt, that you will anything even near to 1Gbps, if the CRS design was done like all aother RBs with integrated switch chip, then there is a single 1G link from the switch chip to the CPU. So if you add all ports including the uplink to a software bridge you trying to push the traffic of 24x ports through one 1G link. Even the traffic between the ports.
I see exactly what you are saying. When bridging all ports traffic likely cannot exceed 1gbps simplex total for router. It likely depends how the traffic is flowing through the ports. Hopefully Mikrotik addresses this in future with more SWOS features?I was talking about the effect bridging all ports will have. If you take a look at the picture troy linked, you will see what I'm talking about. Bridging all ports in ROS, will force them all through the 1G link to the CPU.
Please, could you give some details about the setup of your RB2011? Number of pppoe conns, queues (simple/tree), firewall rules, overclock...Reached 300mbps on a PPPoE connection going through it. That cap was caused by the PPPoE client router(RB2011) hitting 100 percent CPU not cloud router acting as switch. The cloud router was at about 50 percent but I think part of that was me being logged in it on winbox. Will need to find a different mikrotik box and do raw IP to see if I can do 1gps flowing through the uplink on it but I bet it comes close. Wander if turning connection tracking off would help. Mostly only seeing PPPoE packets so I am not sure what it would change.