Turris OS 6.0 broke VLAN AP

I have an separate VLAN and Wifi for my IoT devices. My homeserver is connected to the Turris Omnia with a single Ethernet port. The untagged part does the regular internet (which works fine). Additionally there is a tagged VLAN on this connection. I have a Wifi configured that is bridged to that VLAN. It has a separate FW zone. Apart from not being able to access the internet it has the same configuration as the regular Wifi.

Now the problem is that I cannot access devices on the Wifi from my homeserver through the tagged VLAN. When I try to ping them I always get “Destination Unreachable” by the Turris. This has worked fine until the update. Does anyone have a solution for this?

The network looks roughly like this:
172.21.1.1 (homeserver) <-tagged VLAN → 172.21.1.254 (TO) ← Wifi → 172.21.1.10… (Devices).

VLAN configuration changed quite a lot with TOS 6. Have a look at Network → Interfaces and then the tab to the right.

You mean the tab ATM bridges? Tbh I have no idea what these settings do. Is there documentation about that? At least while googling I didn’t find anything.

Correction (I didn’t had access to the interface when I wrote the previous message): You can find the VLAN config in LuCI under Network → Interfaces. Then determine the right device → Configure → Bridge VLAN Filtering.

So I have 2 devices, IoT and IoT.9. The latter is the VLAN with tag 9. I can edit this device but it doesn’t contain the VLAN bridge filtering option.
When I edit IoT I see the VLAN filtering option. But it’s not clear to me what I have to set there. I tried different combinations and all just lead to the result that I cannot reach any device at all, neither the one via VLAN nor the ones in the Wifi (without VLAN).

Look at this → How to make VLAN work again after update from TOS 5 to 6?

2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.