Problem: once I add the VLANs, untagged traffic is no longer bridged to bridge-secure. The access point is using untagged traffic to get a DHCP address from the router (and who knows what else). Anyway, it’s not working if the router ignores untagged traffic. I know since I have a different access point (with other shortcomings) that allows me to set a vlan for management traffic, then all works (after removing the line “add interface=ether1 bridge=bridge-secure”).
Summary: how do I bridge both tagged and untagged traffic on ether1?
I’ve configured a DHCP server for each bridge (works fine).
I’m adding my configuration. The first part just sets up two bridges with dhcp. The second part bridges ether1 to bridge-usecure, and sets up VLAN 20 on ether1 and bridges that to bridge-secure to route tagged traffic to the secure bridge. Untagged traffic gets to bridge-secure. Torch shows both untagged and tagged traffic, but tagged traffic “gets lost” and clients do not even get an IP address from the DHCP server.
add interface=ether1 bridge=bridge-unsecureIf upgrading to ROS 6 really solves the problem I will try to do that. But I am concerned about what it breaks. At least qos.
I bit the bullet and upgraded to V6: now indeed it’s working!!! Should have listened right away …
(but the upgrade did break quite a few things and took me several hours to fix - not sure I’m done yet).
I bit the bullet and upgraded to V6: now indeed it’s working!!! Should have listened right away …
(but the upgrade did break quite a few things and took me several hours to fix - not sure I’m done yet).
You should be able to now move your config away from bridges to just using the switch chip for VLAN tagging. This will speed up any L2 communications on your device.
Not sure how to do this, or if it’s even possible: I’m using a firewall to regulate traffic between bridges: traffic can pass between some, not others, and it also depends on the service called.
If your regulating the traffic via L2 bridge firewall rules then that make sense. If you are doing it at L3 which is what I assumed looking at the small config snip then you could move away from the bridges. That said it would probably only benefit you use multiple ports on your RB2011 to connect to upstream devices that may use the VLANs. This way any L2 switching would stay on the switch chip and not need to traverse the CPU thus freeing up CPU time and BW to the CPU.
If you don’t need to utilize the switch then removing the bridges will likely only free up CPU time because there would be fewer steps in the packet processing.
See this wiki article on configuring the switch chip.