GL-MT300N-V2 wifi packet loss


I’m experiencing frequent packet loss over wifi with GL-MT300N-V2.
The device is configured in router mode, WAN connected with physical cable.

Packet loss happens every 30-40 seconds, 1-2 packets are lost.

When packet loss happens I see the following messages in dmesg:
root@GL-MT300N-V2:~# dmesg
[30416.612989] 5f0, flush one!
[30426.195099] ea8, flush one!
[30427.177421] Rcv Wcid(1) AddBAReq
[30427.180943] Start Seq = 00000eaa

Any hints highly appreciated.

Thank you.

Where did you ping from? from PC connected to MT300N via wifi? Did you setup repeater? which can refer to MT1300 WiFi issues.

Ping is running from the PC connected via wifi. Repeater is not configured, no saved networks.
MT300N is configured in router mode, WAN is connected via cable to the uplink device.

MT300N is running with 3.216 release.

The drops I see corresponds with the RX errors incrementing on ra0 interface.

root@GL-MT300N-V2:~# ifconfig ra0
ra0 Link encap:Ethernet HWaddr 94:83:C4:15:51:54
RX packets:100041 errors:62 dropped:0 overruns:0 frame:0
TX packets:113123 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15877059 (15.1 MiB) TX bytes:78984458 (75.3 MiB)


If you are trying to ping any outside server you need to use Google dns addresses as they are the quickest out there. The IP addresses to ping are and is cloudflare dns server and not exactly the fastest.

Packet loss over cable usually means there’s a fault on the wire, faulty NIC or fault outside your house. Use trace to find where the loss is.

Hi Shivadow,

When I ping the next hop device from MT1300 there is no packet loss, so the cable between them is fine.
If I ping from the PC (connected via wifi) to the next hop device I get the same packet loss.

It doesn’t matter if I ping Cloudflare’s IP or Google’s IP, the drops are there each 30-40 seconds.

When drops happens I see RX errors incrementing on ra0 interface, so something is wrong on the wifi segment.

I’ve upgraded MT1300 to release 4.3.7, it improved a lot.

Thanks everyone for the inputs.


Few updates after ~24h using release 4.3.7.

Clients are connected to wifi but connection is not working i.e. ping to the default gateway is not working. Disabling and enabling Wifi on MacOS/iOS sometimes fixes the issue sometimes not. These are pretty random.

If you want to troubleshoot it, you go into GUI and change same wifi settings or other settings the CPU usage goes to the sky and eventually the device reboots.

Poor experience with 4.3.7, I’ve reverted back to 3.216.

After downgrading to 3.216 and resetting the device it is working properly. No more wifi drops.