WiFi stop from time to time

[gev]

Hello

 

I have an issue with my wifi, it's not reliable. There is no problem with my laptop, or any other devices on my network, but my NanoPi Neo is disconneted after a few hours. It can stay alive for an half a day, and after it become unreachable.

 

As I have no other connection to my NanoPi it's a bit hard to establish what appens. But if I unplug the USB Wifi dungle, and replugged it the link come back.

 

Doing a ping to the NanoPi, I see regular "Request timeout for icmp_seq" - every 20, 50 or 100 request, it depends - and sometime the request time is abnormally huge: serveral seconds.

 

The config has bee done with nmtui, the name has been left as proposed (wlx00b819aa5f7). It's a static IP, Gateway is y router, and the DNS server has been input manually based on my router data.

 

iwconfig output:

wlx000b819aa5f7  IEEE 802.11bgn  ESSID:"MyESSID"  Nickname:"<WIFI@REALTEK>"
          Mode:Managed  Frequency:2.437 GHz  Access Point: 14:CC:20:97:FE:64
          Bit Rate:150 Mb/s   Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:****-****-****-****-****-****-****-****   Security mode:open
          Power Management:off
          Link Quality=80/100  Signal level=49/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

 

ifconfig:

wlx000b819aa5f7 Link encap:Ethernet  HWaddr 00:0b:81:9a:a5:f7
          inet addr:192.168.1.202  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::d443:6a18:32da:e5d7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:51728 errors:0 dropped:8476 overruns:0 frame:0
          TX packets:35786 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7144585 (7.1 MB)  TX bytes:4917495 (4.9 MB)

ping output:

64 bytes from 192.168.1.202: icmp_seq=22055 ttl=64 time=56.726 ms
64 bytes from 192.168.1.202: icmp_seq=22056 ttl=64 time=3.295 ms
64 bytes from 192.168.1.202: icmp_seq=22058 ttl=64 time=6.217 ms
64 bytes from 192.168.1.202: icmp_seq=22059 ttl=64 time=6.551 ms
64 bytes from 192.168.1.202: icmp_seq=22060 ttl=64 time=6.095 ms
64 bytes from 192.168.1.202: icmp_seq=22061 ttl=64 time=8.796 ms
Request timeout for icmp_seq 22062
64 bytes from 192.168.1.202: icmp_seq=22063 ttl=64 time=5.058 ms
64 bytes from 192.168.1.202: icmp_seq=22064 ttl=64 time=6.975 ms
64 bytes from 192.168.1.202: icmp_seq=22065 ttl=64 time=6.486 ms
64 bytes from 192.168.1.202: icmp_seq=22066 ttl=64 time=3.707 ms
64 bytes from 192.168.1.202: icmp_seq=22067 ttl=64 time=9.997 ms
64 bytes from 192.168.1.202: icmp_seq=22068 ttl=64 time=6.415 ms
64 bytes from 192.168.1.202: icmp_seq=22069 ttl=64 time=6.248 ms
64 bytes from 192.168.1.202: icmp_seq=22070 ttl=64 time=5.540 ms
64 bytes from 192.168.1.202: icmp_seq=22071 ttl=64 time=5.915 ms
64 bytes from 192.168.1.202: icmp_seq=22072 ttl=64 time=12.543 ms

Spoiler

 

I would really appreciate if someone can tell me waht to monitor to prevent that issue

Regards