RB2011 How connect ports from differ HW switch ?

Hello,

I use Trunk at Ether1 with vlan 80,81,82,83 - easy for now.
Ether3,4 both are Hybrid (Trunk 81,82,83 and 80 as Untagged ) by switch menu and fallback.

How add AccessPort from ether7 who is on separate switch-chip-2 ??
RB2011 not support “Bridge VLAN Filtering” and I cannot setup vlans in new way like (third generation of vlan configuration).

Interfaces with Bridge and vlans
uHKOeQpER2.png
Bridge Ports work well as 81,82,83 to manage them only as Trunk/AccessPort, not as Hybrid.
In this setup point of time the ether7 works because a software bridge port connect it but it’s not work as Hybrid :frowning:
ZaNoJmc9sy.png
Hybrid on Ether3,4 done in Switch menu.
Now the Server untagged traffic works as PVid 80 but the ether7 from second switch chip stop working.
ekGDLuX6Ye.png
I cannot access only that traffic from Ether7 who should work.
How fix it.
I try differ ways and I cannot found a proper way.

There is no good way to do hardware offloading across multiple switch chips, see https://help.mikrotik.com/docs/display/ROS/Layer2+misconfiguration#Layer2misconfiguration-VLANfilteringwithmultipleswitchchips

There are also issues with Atheros fast ethernet (10/100Mbps) switch chips, they do not support hardware offloaded hybrid ports and see the comments at the bottom of the section https://help.mikrotik.com/docs/display/ROS/Switch+Chip+Features#SwitchChipFeatures-HostTable regarding mixing hardware and non-hardware offloaded ports.

Using a single VLAN-aware bridge works fine but you do loose hardware offloading, only really an issue if you have significant traffic between ports within the same VLAN

tdw write

I see the two paragraph
Solution 1) Two software Bridge and routing between them.
Cannot be done because I use the same network, this breake adressation etc.

Solution 2) Connect switch1 and switch2 by cable as Trunk
This is some of a way of workaround but insted that better will be add other Manged Switch to Gb swith1 and that way do better workaround.
Diffrence of configuration is show here, ether 5,6 used as wire-trunk between switch-es who connect two separate software bridge1 and bridge2
opera_V6T4xtLF3b.png

There are also issues with Atheros fast ethernet (10/100Mbps) switch chips, they do not support hardware offloaded hybrid ports and see the comments at the bottom of the section > https://help.mikrotik.com/docs/display/ROS/Switch+Chip+Features#SwitchChipFeatures-HostTable > regarding mixing hardware and non-hardware offloaded ports.

This is not a big issue, the transfers are very small.
Hybrid port is a need only at switch1 what works fine by


Using a single VLAN-aware bridge works fine but you do loose hardware offloading, only really an issue if you have significant traffic between ports within the same VLAN

Seams like best solution but I not understand what you want say by this. One Interface can be used only ones in bridge port and I cannot have separate bridge for one vlan becasue second br cannnot use used trunk interface.

Summary:
If software bridge port have option to add interface as Hybrid then this will solve my problems but RB2011 not support the newest vlan configuration like on CCR/CSR..
Seams I can connect both switch1,2 by wire or just by adding a managed switch to switch1 port.

With vlan-filtering=no, the software bridge ignores VLAN tags on frames completely. So you can choose one VLAN per port to be tagless (so a hybrid port) but it must be the same VLAN on all ports of the bridge, including the virtual one facing towards the virtual router.

The ability to add and remove tags, allowing the same VLAN to be available as tagged on one port and as tagless on another, is provided by vlan-filtering=yes, which, however, deactivates switch chip forwarding on low-end switch chips.


What CRS does is that it integrates the settings controlled by /interface ethernet switch port and /interface ethernet vlan on lower end models into the /interface bridge port and /interface bridge vlan configuration. It can do that because the switch chip it is built around has sufficient capabilities to deal with the vlan-filtering capability.

My personal understanding is that the gigabit switch chips (8327/8337), like switch1 in the 2011, could be used this way too, but I don’t have the datasheet so I cannot be sure. The 8227 chip, used as switch2 in the 2011, lacks both the ability to selectively untag egress frames and the switch chip rules allowing to redirect STP and other “link-local” frames to CPU, so it cannot be integrated into the bridge/switch fusion.

sindy

Seams like one NativeVlan for one bridge - for me greate but there set it if we not use new vlan way bcs vlan-filtering=no ?
For AccessPort is always easy to add a interface to proper next bridge who have bridge-port’s of vlan and specific interface.
For Hybrid is always just not exist until vlan-filtering=yes who not work at RB2011 and that’s why I use HW Switch menu but then I cannot use AccessPort from second switch2 chip..



The ability to add and remove tags, allowing the same VLAN to be available as tagged on one port and as tagless on another, is provided by > vlan-filtering=yes> , which, however, deactivates switch chip forwarding on low-end switch chips.

For me is not problem to not have HW acceleration and a new way of vlans by vlan-filtering=yes I can configure but documentation say at this RB2011 it’s not supported and I not try.
But not only vlan-filtering=yes give us have trank and untagged, from years I use just Second Bridge with BridgePort ( vlan on bridge-lan + separate interface) who set interface as AccessPort.



[quote=“, post:3, topic:155494”]
RB2011 not support the newest vlan configuration like on CCR/CSR..
[/quote]

What CRS does is that it integrates the settings controlled by > /interface ethernet switch port > and > /interface ethernet vlan > on lower end models into the > /interface bridge port > and > /interface bridge vlan > configuration. It can do that because the switch chip it is built around has sufficient capabilities to deal with the > vlan-filtering > capability.

You means the vlan-filtering=yes works on RB2011 ? If yes then this software way is proper for me.

This is so hard with RouterOS and differ hardware. I always put all stuff into vlans when work with MikroTik because by years HybridPort is always problematic. Maybe RouterOS v8 give us final one way to configure AccessPort/Trunk/Hybrid.

It does, but without any hardware offload. I’m actually running the following on a 2011 (ether1-4 & ether7-9 as access ports, ether5-6 as hybrid ports to an HP1810-8G and hAP ac lite respectively):
/interface bridge
add add-dhcp-option82=yes admin-mac=XX:XX:XX:XX:XX:XX auto-mac=no dhcp-snooping=yes ingress-filtering=yes name=bridge protocol-mode=none vlan-filtering=yes
/interface vlan
add interface=bridge name=bridge.42 vlan-id=42
add interface=bridge name=bridge.44 vlan-id=44
add interface=bridge name=bridge.45 vlan-id=45
/interface bridge port
add bridge=bridge ingress-filtering=yes interface=ether1-bridge pvid=44
add bridge=bridge ingress-filtering=yes interface=ether2-bridge pvid=44
add bridge=bridge ingress-filtering=yes interface=ether3-bridge pvid=44
add bridge=bridge ingress-filtering=yes interface=ether4-bridge pvid=44
add bridge=bridge ingress-filtering=yes interface=ether5-bridge pvid=44 trusted=yes
add bridge=bridge ingress-filtering=yes interface=ether6-bridge pvid=44 trusted=yes
add bridge=bridge ingress-filtering=yes interface=ether7-bridge pvid=42
add bridge=bridge ingress-filtering=yes interface=ether8-bridge pvid=42
add bridge=bridge ingress-filtering=yes interface=ether9-bridge pvid=42
/interface bridge vlan
add bridge=bridge tagged=bridge,ether5-bridge,ether6-bridge vlan-ids=42
add bridge=bridge tagged=bridge vlan-ids=44
add bridge=bridge tagged=bridge,ether5-bridge,ether6-bridge vlan-ids=45