maemo.org - Talk - View Single Post - Poor wifi performance?

Milhouse	2007-12-09 , 06:58
Posts: 3,401 \| Thanked: 1,255 times \| Joined on Nov 2005 @ London, UK	#6

Ubuntu Gutsy Gibbon w/Intel 10/100 PRO NIC pinging N800:

Code:

neil@nm-tyan:~$ ping n8dev
PING n8dev (192.168.0.19) 56(84) bytes of data.
64 bytes from n8dev (192.168.0.19): icmp_seq=1 ttl=64 time=72.8 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=2 ttl=64 time=96.1 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=3 ttl=64 time=17.2 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=4 ttl=64 time=40.8 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=5 ttl=64 time=65.3 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=6 ttl=64 time=89.4 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=7 ttl=64 time=112 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=8 ttl=64 time=35.0 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=9 ttl=64 time=56.0 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=10 ttl=64 time=81.2 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=11 ttl=64 time=105 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=12 ttl=64 time=27.1 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=13 ttl=64 time=50.7 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=14 ttl=64 time=74.5 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=15 ttl=64 time=98.5 ms
64 bytes from n8dev (192.168.0.19): icmp_seq=16 ttl=64 time=20.3 ms

--- n8dev ping statistics ---
16 packets transmitted, 16 received, 0% packet loss, time 15000ms
rtt min/avg/max/mdev = 17.254/65.246/112.847/30.098 ms


Ubuntu PC ----- [Gig Switch] ----- [WRT54GS AP] ~~~Wi-Fi~~~ N800

Average: 65ms

N800 pinging Ubuntu Gutsy Gibbon PC:

Code:

/home/user # ping 192.168.0.12
PING 192.168.0.12 (192.168.0.12): 56 data bytes
64 bytes from 192.168.0.12: seq=0 ttl=64 time=27.6 ms
64 bytes from 192.168.0.12: seq=1 ttl=64 time=20.5 ms
64 bytes from 192.168.0.12: seq=2 ttl=64 time=19.5 ms
64 bytes from 192.168.0.12: seq=3 ttl=64 time=20.6 ms
64 bytes from 192.168.0.12: seq=4 ttl=64 time=19.6 ms
64 bytes from 192.168.0.12: seq=5 ttl=64 time=19.8 ms
64 bytes from 192.168.0.12: seq=6 ttl=64 time=19.7 ms
64 bytes from 192.168.0.12: seq=7 ttl=64 time=20.7 ms
64 bytes from 192.168.0.12: seq=8 ttl=64 time=19.6 ms
64 bytes from 192.168.0.12: seq=9 ttl=64 time=20.5 ms
64 bytes from 192.168.0.12: seq=10 ttl=64 time=19.6 ms
64 bytes from 192.168.0.12: seq=11 ttl=64 time=20.5 ms
64 bytes from 192.168.0.12: seq=12 ttl=64 time=19.5 ms
64 bytes from 192.168.0.12: seq=13 ttl=64 time=20.6 ms
64 bytes from 192.168.0.12: seq=14 ttl=64 time=19.6 ms
64 bytes from 192.168.0.12: seq=15 ttl=64 time=20.5 ms
64 bytes from 192.168.0.12: seq=16 ttl=64 time=19.6 ms
64 bytes from 192.168.0.12: seq=17 ttl=64 time=20.9 ms

--- 192.168.0.12 ping statistics ---
18 packets transmitted, 18 packets received, 0% packet loss
round-trip min/avg/max = 19.5/20.4/27.6 ms


N800 ~~~Wi-Fi~~~ [WRT54GS AP] ----- [Gig Switch] ----- Ubuntu PC

Average: 20.4ms

Ubuntu Gutsy Gibbon pinging a TiVo Series 1 over a bridged wireless connection:

Code:

neil@nm-tyan:~$ ping tivo
PING tivo (192.168.0.7) 56(84) bytes of data.
64 bytes from tivo (192.168.0.7): icmp_seq=1 ttl=255 time=3.25 ms
64 bytes from tivo (192.168.0.7): icmp_seq=2 ttl=255 time=3.28 ms
64 bytes from tivo (192.168.0.7): icmp_seq=3 ttl=255 time=3.23 ms
64 bytes from tivo (192.168.0.7): icmp_seq=4 ttl=255 time=3.24 ms
64 bytes from tivo (192.168.0.7): icmp_seq=5 ttl=255 time=3.22 ms
64 bytes from tivo (192.168.0.7): icmp_seq=6 ttl=255 time=4.19 ms
64 bytes from tivo (192.168.0.7): icmp_seq=7 ttl=255 time=4.15 ms
64 bytes from tivo (192.168.0.7): icmp_seq=8 ttl=255 time=3.13 ms
64 bytes from tivo (192.168.0.7): icmp_seq=9 ttl=255 time=3.12 ms
64 bytes from tivo (192.168.0.7): icmp_seq=10 ttl=255 time=3.25 ms
64 bytes from tivo (192.168.0.7): icmp_seq=11 ttl=255 time=3.14 ms
64 bytes from tivo (192.168.0.7): icmp_seq=12 ttl=255 time=3.36 ms
64 bytes from tivo (192.168.0.7): icmp_seq=13 ttl=255 time=3.35 ms
64 bytes from tivo (192.168.0.7): icmp_seq=14 ttl=255 time=3.37 ms
64 bytes from tivo (192.168.0.7): icmp_seq=15 ttl=255 time=3.65 ms
64 bytes from tivo (192.168.0.7): icmp_seq=16 ttl=255 time=3.39 ms

--- tivo ping statistics ---
16 packets transmitted, 16 received, 0% packet loss, time 15005ms
rtt min/avg/max/mdev = 3.129/3.400/4.192/0.317 ms


Ubuntu PC ----- [Gig Switch] ----- [WRT54GS AP] ~~~Wi-Fi~~~ [WRT54GS Bridge] ----- TiVo

Average: 3.4ms

The TiVo Series 1 is using a 50mhz PowerPC processor, connected by wired ethernet to a Linksys WRT54GS (200mhz Broadcom CPU) which is bridged (11g, WPA PSK/TKIP) to another WRT54GS Access Point, to which the Ubuntu PC is connected via a Gig ethernet switch.

The TiVo connection is a far more convoluted route than that taken by the N800, yet the TiVo - a far less poweful device than the N800 - responds in a fraction of the time taken by the N800.

The N800 has a more powerful CPU than either of the Linksys wireless routers and the TiVo, so I can't believe the poor ping time is due to CPU issues on the N800.

Pinging *FROM* the N800 to the Ubuntu PC results in a better ping time - less than a third of that when going the other way - which suggests something odd is going on (power saving?)

I've suspected for some time that the WiFi speed on N800s (also 770s) is poor, but doubt we'll see any improvement due to the open/closed nature of the WiFi stack and the lack of apparent care/importance Nokia give to the wireless side of things. I don't think the problem is with the CPU, more likely a poor or duff implementation.

Last edited by Milhouse; 2007-12-09 at 07:03.

Quote & Reply |