search

wolfallein / clockworkpi-debian

A minimal Debian OS for clockworkpi device based on Allwinner R16 SOC
37 stars 7 forks source link

Slow ssh connexion over wifi, works fine over USB #4

Open arthurlutz opened 3 years ago

arthurlutz commented 3 years ago

After setting up version 0.3 I get wifi working, but the SSH over wifi is laggy, almost unusable. For now am switching to ssh over the USB network but I'd be happy to debug this to help solve the problem.

wolfallein commented 3 years ago

I don't remember to have this issue with my GS on v0.3. Will look for it.

Could you try a different network and see if the connection is good?

arthurlutz commented 3 years ago

I'm getting very variable ping responses which is probably the reason ssh is being like this. 

❯ ping 192.168.1.157
PING 192.168.1.157 (192.168.1.157) 56(84) bytes of data.
64 bytes from 192.168.1.157: icmp_seq=1 ttl=64 time=4.20 ms
64 bytes from 192.168.1.157: icmp_seq=2 ttl=64 time=440 ms
64 bytes from 192.168.1.157: icmp_seq=3 ttl=64 time=884 ms
64 bytes from 192.168.1.157: icmp_seq=4 ttl=64 time=2.15 ms
64 bytes from 192.168.1.157: icmp_seq=5 ttl=64 time=521 ms
64 bytes from 192.168.1.157: icmp_seq=6 ttl=64 time=831 ms
64 bytes from 192.168.1.157: icmp_seq=7 ttl=64 time=2.56 ms
64 bytes from 192.168.1.157: icmp_seq=8 ttl=64 time=611 ms
64 bytes from 192.168.1.157: icmp_seq=9 ttl=64 time=901 ms
64 bytes from 192.168.1.157: icmp_seq=10 ttl=64 time=1.97 ms
64 bytes from 192.168.1.157: icmp_seq=11 ttl=64 time=687 ms
64 bytes from 192.168.1.157: icmp_seq=12 ttl=64 time=1231 ms
64 bytes from 192.168.1.157: icmp_seq=13 ttl=64 time=229 ms
64 bytes from 192.168.1.157: icmp_seq=14 ttl=64 time=782 ms
64 bytes from 192.168.1.157: icmp_seq=15 ttl=64 time=907 ms
64 bytes from 192.168.1.157: icmp_seq=16 ttl=64 time=2.09 ms
64 bytes from 192.168.1.157: icmp_seq=17 ttl=64 time=1.87 ms
64 bytes from 192.168.1.157: icmp_seq=18 ttl=64 time=1.72 ms

On the same wifi / network a pizero-w gets : 

❯ ping pizerow.local
PING pizerow.local (192.168.1.3) 56(84) bytes of data.
64 bytes from 192.168.1.3 (192.168.1.3): icmp_seq=1 ttl=64 time=246 ms
64 bytes from 192.168.1.3 (192.168.1.3): icmp_seq=2 ttl=64 time=5.33 ms
64 bytes from 192.168.1.3 (192.168.1.3): icmp_seq=3 ttl=64 time=7.17 ms
64 bytes from 192.168.1.3 (192.168.1.3): icmp_seq=4 ttl=64 time=6.46 ms
64 bytes from 192.168.1.3 (192.168.1.3): icmp_seq=5 ttl=64 time=3.19 ms
64 bytes from 192.168.1.3 (192.168.1.3): icmp_seq=6 ttl=64 time=5.50 ms
64 bytes from 192.168.1.3 (192.168.1.3): icmp_seq=7 ttl=64 time=5.93 ms
arthurlutz commented 3 years ago

Running wavemon to see if the signal strength has an impact. Suprise : when running wavemon via the USB connexion, ping is still bad, when running through the wifi (over a laggy SSH) I suddenly get low pings and opening another shell is working fine ! So is there some of power management in the wifi that says "go to sleep when inactive" which would explain this ?