doesn't work: I can't ping the router from my computer (on LAN1) and the phone doesn't work.
May it be related to the MT76 and how the CPU port is treated (there is just one big eth0 interface and also the WAN is DSA managed).
However, it doesn't solve the "problem". I'll give some more details.
The VoIP device expects tagged traffic on vlan 5 and unfortunately there is no way to access the management page to modify this setting. VoIP credentials of my ISP, however, work even without the tag (I can set up Linphone on my Mac and phone using the normal - untagged - internet). So I wanted to reuse without using the 5-tag on the WAN.
So in 19.07, I created a eth0.5 interface and bridged it to eth0.1 interface, so that the ATA box could receive the DHCP setting from the router and be pingable from other hosts in the LAN. The bridge automatically added and removed vlan tags to and from the ATA box.
I know that I could set up another bridge interface on the other VLAN and set up a new DHCP server, but my goal was to have a single one on the same subnet and just "remove "the vlan tag from the box.
The setting was the following:
I can't get the same result in 21.02. I can use a different dhcp server on br-lan.5 of course to reach the ATA box; another option is to add lan4.5 to br-lan so I can have the box on the same subnet, but not reachable because the bridge itself is not able to correctly remove and add vlan tag (but on the forum i found out that it seems to be a problem of MT76, that the CPU port - eth0 - is not tagged).
To sum up, I don't really need a different VLAN scenario, just a way to remove the tag from the device when added to the bridge.
Do you need the tagged VLAN 1 on the LAN side anyway?
If not, remove the VLAN 1, set lan1~3 to untagged in VLAN 5, and set LAN interface's device to br-lan.5.
I tried that as well and still it doesn't work.
I'm really starting to believe that there is a bug in the MT7530 switch, as if the packet is not sent over the bridge but directly on fabric without adding the tag, unfortunately I don't have other chipsets to try.
Hello, maybe you can help me with the following problem. Wi-Fi Access Point (WDS) doesn't work when VLAN filtering is enabled. I can connect to this AP. but don't have access to the network. When I set WiFi as a client (WDS) it works fine.
I tried to ping from my PC (untagged vlan on LAN1, when I took the screenshot the cable was not attached yet) and the ATA box received it. On the router itself, I ran a tcpdump on br-lan interface and noticed that I could see the ICMP packets: this makes perfect sense, since the bridge is in charge of removing and adding the tag and so traffic has to flow over it.
Pinging another pc on an untagged port works perfectly and no traffic appear on br-lan; also this makes sense because, in this case, since we are in the default vlan1, all traffic goes through fabric and the bridge is not involved.
Now let's go to 21.02. Right now, the best way to have the voip device working is the following, that you don't approve of
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4.5'
config bridge-vlan
option device 'br-lan'
option vlan '5'
list ports 'lan1:u*'
list ports 'lan2:u*'
list ports 'lan3:u*'
list ports 'lan4:t*'
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
list ports 'lan4'
config interface 'lan'
option proto 'static'
............
option device 'br-lan.5'
Still, I don't get why simply bridging different VLANs as in 19.07 (without putting everything on the same VLAN and without setting the PVID) doesn't work. Probably I'll have to dig deeper in the DSA architecture.
The ATA box from my ISP broke down and I bought another one that doesn't need the tagged interface.
There is no way in 21.02 to have the same behaviour as 19.07.
Thanks, this helped and now starts to make sense.
Apparantly now with DSA you have to specify VLAN ID to the virtual interface as well to bind it to the VLAN.