Solved: the problem was having the STA Repeater mode turned on while using ethernet WAN. Turning off the repeater mode made the problem go away.
Long story:
I use GL.iNet Beryl AX during travels. Most of the time I use it in hotels, where I extend the wifi from the hall into the room (by using the STA repeater mode). The problem with packet losses started in a rented appartment when I decided to hook up the Beryl through a LAN cable to a router instead.
The logs (dmesg) showed that every 30-40 seconds my GL.iNet Beryl AX was trying to look for a previous hotel's wifi network to connect to. This resulted in me losing my wifi connectivity on the client side for a couple seconds every time.
Turning off STA Repeater mode when Beryl is connected via a lan cable made this problem go away.
Note to developers:
If ethernet is connected, maybe have STA Repeater mode turn off automatically?
I'd agree i wish this could be improved on, because we also have this failover system, ethernet should be prioritized as per default setting if it has link connection, somehow it doesn't seem to happen.
Some uers/customer probably require listening to the repeater SSID online, and use the repeater priority if the repeater connected, so they do not want to disable the automatically repeater.
But if you want to disable the repeater when the WAN interface connected, can try to custom a script, example for you:
create a script in the /etc/rc.d/S99wan_check.sh:
#!/bin/sh
/etc/init.d/repeater start
# Check whether the eth0 interface can ping 8.8.8.8
if ping -I eth0 -c 30 8.8.8.8 &> /dev/null; then
echo "eth0 interface ping 8.8.8.8 ok, Repeater will be disabled"
# disable Repeater mode/script
/etc/init.d/repeater stop
else
echo "eth0 interface cannot ping 8.8.8.8, Repeater keep working"
fi
Note: only when the device boot-up affective one time.
I hit this too. With WAN only on Ethernet and no WAN Wifi configured there is terrible packet loss on the router. Interactive sessions like VNC are unusable and video streaming is unreliable. Stopping the repeater solves the problem.
This ought to be considered a bug and not something we have discover here and fix with a boot script on every release.
Also, make sure you turn the repeater off before you power it down. For some reason, when I go to a new place, my Slate has trouble transmitting the wifi SSID if repeater was left on from previous connection. Best to leave it off, and turn on repeater when you get to new location.
uci set network.wan.metric='10'
uci set network.wwan.metric='20'
uci commit
/etc/init.d/network restart
With this, default(0.0.0.0/0) will be routed to the WWAN only when the WAN link is down.
In simple terms, the WAN has priority over the WWAN.
You can adjust the numbers, or set some for other interfaces as well.
