Lan ports aren't accessible for WiFi client for the first 250-330 seconds after connection

General discussion
,
18

I tried to understand how to setup that, but settings vlans was easier. Also I afraid that having multicast for all the packets would make too much unneeded load.

Looks like I manage to fix the issue by pushing all the traffic through CPU with following commands:

bridge vlan add dev lan0 vid 10 pvid untagged
bridge vlan add dev lan1 vid 11 pvid untagged
bridge vlan add dev lan2 vid 12 pvid untagged
bridge vlan add dev lan3 vid 13 pvid untagged
bridge vlan add dev lan4 vid 14 pvid untagged
bridge vlan del dev lan0 vid 1               
bridge vlan del dev lan1 vid 1               
bridge vlan del dev lan2 vid 1               
bridge vlan del dev lan3 vid 1               
bridge vlan del dev lan4 vid 1

So bridge vlan looks like:

root@ap:~# bridge v                          
port    vlan ids                             
lan0     10 PVID Egress Untagged             
lan1     11 PVID Egress Untagged             
lan2     12 PVID Egress Untagged             
lan3     13 PVID Egress Untagged                  
lan4     14 PVID Egress Untagged             
br-guest_turris  1 PVID Egress Untagged      
br-lan   1 PVID Egress Untagged              
wlan1    1 PVID Egress Untagged              
wlan0    1 PVID Egress Untagged

BTW, I also find out that Asus RT-AC68U with Asus original firmware has similar bug. I hope I’ll be able to fix it in the similar way after flashing it with OpenWRT.

Thank you for all the advises!

1 Like