Connections between clients stop working (GL-BE93000)

Router
1

Just setup the router today (Flint 3). Started with upgrading firmware to latest one (4.8.4).

After a while I’m unable to connect between two wireless hosts. The Internet on both works just fine. I can ssh to the router itself and it can ping both clients, but the clients themselves can’t ping or connect to each other directly over LAN. arp -n shows correct addresses on both. Looks to me like bridging is just not working(?). Rebooting router fixes the issue, for a while.

2

Hi

Could you please help check or try the following:

  1. Are both clients connected to the Main Wi-Fi instead of the Guest Wi-Fi?
  2. Is ping working normally between wired clients, and between wired and wireless clients?
  3. Are both clients connected to the same band? If using MLO, please try switching to a non-MLO band and see if that helps.
4
  1. I don’t even have guest wi-fi enabled.
  2. I don’t have any wired clients except for some home automation
  3. Yes, they were connected to MLO. I only had 2.4 also connected.

I have not observed this behavior for the whole day today. Yesterday evening I disabled the 2.4Mhz wifi completely, so only MLO is enabled (with all sub-bands(?)), but I’m not sure if it had anything to do with it.

Hopefully the issue does not reappear, but if it does I’ll report back.

5

Thank you for the update—we’re glad to hear it’s working properly now.

If you encounter any issues in the future, feel free to let us know anytime.

6

The issue was back.

I have a 3rd host, and it seems like only 1 host is affected. It can’t communicate with other hosts, they can communicate with each other. All of them are on the MLO connection. Also, I think this is the same host as before, so could be it is not the router’s problem exactly, but that host’s. Though restarting wifi on that host doesn’t change anything, but restarting the router did.

Both IPv4 and IPv6 is affected. But the affected host connect over the Internet just fine, so it doesn’t look like WiFi issue itself(?).

Anyway, I realize that this is probably some firmware issue, in the kernel or driver or something like this, and I bet it will get fixed eventually. I didn’t even know Wifi 7 exist, so I know how live goes with new tech adoption like that in Linux.

If I have anything useful to add I’ll post again, otherwise, if the issue happens every few days, I guess I can live with it for time being.

7

If only one device is experiencing issues, it may be due to the way some devices handle ARP after entering sleep mode (though this may not be the only cause).

We recommend that, when the issue occurs again, you check the device’s ARP table to see if entries for other devices on the same subnet that are actively pinging or communicating are present.

# On Windows CMD
arp -a

# On Linux 
ip neighbour

If it’s confirmed that the ARP entries are missing, you might try enabling Proxy ARP and Multicast-to-Unicast to see if this resolves the issue.

# Enable the Proxy ARP 
uci set wireless.wifi2g.proxy_arp='1'
uci set wireless.wifi5g.proxy_arp='1'
uci set wireless.wifi6g.proxy_arp='1'
uci set wireless.wlanmld2g.proxy_arp='1'
uci set wireless.wlanmld5g.proxy_arp='1'
uci set wireless.wlanmld6g.proxy_arp='1'

# Enable the Multicast to Unicast
uci set wireless.wifi2g.multicast_to_unicast_all='1'
uci set wireless.wifi5g.multicast_to_unicast_all='1'
uci set wireless.wifi6g.multicast_to_unicast_all='1'
uci set wireless.wlanmld2g.multicast_to_unicast_all='1'
uci set wireless.wlanmld5g.multicast_to_unicast_all='1'
uci set wireless.wlanmld6g.multicast_to_unicast_all='1'

uci commit 

reboot
BE9300 MLO - WiFi clients on different bands cannot communicate