Al Johnson wrote:
> On Thursday 25 June 2009, Fox Mulder wrote:
>> One big problem with wlan still exists. When i ping my server the time
>> fluctuates from ~15ms to ~4000ms and i got additional packet loss. I can
>> see this effect for example when i ssh into my freerunner or download
>> anything from it.
>>
>>  So something still must be wrong but i don't know what. My Wlan AP is
>> working right which i verified with a second pc connected through wlan.
>>
>> Anybody else experience such odd wlan behaviour?
> 
> There were reports that some APs don't play nicely with the power saving 
> enabled on the wifi chip. You could see if it's any more reliable with:
>       iwconfig eth0 power off
> or
>       wmiconfig -i eth0 --power maxperf

Wow you were right with the first guess.
After i did "wmiconfig -i eth0 --power maxperf" my average Ping goes
from 583.394ms with packet loss to 13.462ms with no packet loss. :)

Now i just have to find the right location where i could execute the
command. Do i have to execute it every time i enable wlan or just once
after booting?

Ciao,
    Rainer
PING 192.168.1.10 (192.168.1.10): 56 data bytes
64 bytes from 192.168.1.10: seq=0 ttl=64 time=1108.074 ms
64 bytes from 192.168.1.10: seq=1 ttl=64 time=104.011 ms
64 bytes from 192.168.1.10: seq=2 ttl=64 time=20.900 ms
64 bytes from 192.168.1.10: seq=3 ttl=64 time=1061.771 ms
64 bytes from 192.168.1.10: seq=4 ttl=64 time=58.661 ms
64 bytes from 192.168.1.10: seq=5 ttl=64 time=1305.747 ms
64 bytes from 192.168.1.10: seq=7 ttl=64 time=1036.534 ms
64 bytes from 192.168.1.10: seq=8 ttl=64 time=32.540 ms
64 bytes from 192.168.1.10: seq=9 ttl=64 time=1072.011 ms
64 bytes from 192.168.1.10: seq=10 ttl=64 time=67.932 ms
64 bytes from 192.168.1.10: seq=11 ttl=64 time=1116.922 ms
64 bytes from 192.168.1.10: seq=12 ttl=64 time=112.430 ms
64 bytes from 192.168.1.10: seq=13 ttl=64 time=1046.550 ms
64 bytes from 192.168.1.10: seq=14 ttl=64 time=42.630 ms
64 bytes from 192.168.1.10: seq=15 ttl=64 time=1089.967 ms
64 bytes from 192.168.1.10: seq=16 ttl=64 time=87.534 ms
64 bytes from 192.168.1.10: seq=17 ttl=64 time=1127.966 ms
64 bytes from 192.168.1.10: seq=18 ttl=64 time=123.950 ms
64 bytes from 192.168.1.10: seq=19 ttl=64 time=1061.496 ms
64 bytes from 192.168.1.10: seq=20 ttl=64 time=57.699 ms
64 bytes from 192.168.1.10: seq=21 ttl=64 time=1101.848 ms
64 bytes from 192.168.1.10: seq=22 ttl=64 time=97.355 ms
64 bytes from 192.168.1.10: seq=23 ttl=64 time=1034.018 ms
64 bytes from 192.168.1.10: seq=24 ttl=64 time=32.912 ms

--- 192.168.1.10 ping statistics ---
28 packets transmitted, 24 packets received, 14% packet loss
round-trip min/avg/max = 20.900/583.394/1305.747 ms
PING 192.168.1.10 (192.168.1.10): 56 data bytes
64 bytes from 192.168.1.10: seq=0 ttl=64 time=12.949 ms
64 bytes from 192.168.1.10: seq=1 ttl=64 time=17.966 ms
64 bytes from 192.168.1.10: seq=2 ttl=64 time=15.069 ms
64 bytes from 192.168.1.10: seq=3 ttl=64 time=16.872 ms
64 bytes from 192.168.1.10: seq=4 ttl=64 time=12.640 ms
64 bytes from 192.168.1.10: seq=5 ttl=64 time=13.490 ms
64 bytes from 192.168.1.10: seq=6 ttl=64 time=8.022 ms
64 bytes from 192.168.1.10: seq=7 ttl=64 time=16.331 ms
64 bytes from 192.168.1.10: seq=8 ttl=64 time=16.335 ms
64 bytes from 192.168.1.10: seq=9 ttl=64 time=10.998 ms
64 bytes from 192.168.1.10: seq=10 ttl=64 time=10.999 ms
64 bytes from 192.168.1.10: seq=11 ttl=64 time=6.791 ms
64 bytes from 192.168.1.10: seq=12 ttl=64 time=16.326 ms
64 bytes from 192.168.1.10: seq=13 ttl=64 time=17.917 ms
64 bytes from 192.168.1.10: seq=14 ttl=64 time=10.996 ms
64 bytes from 192.168.1.10: seq=15 ttl=64 time=11.256 ms
64 bytes from 192.168.1.10: seq=16 ttl=64 time=11.087 ms
64 bytes from 192.168.1.10: seq=17 ttl=64 time=16.288 ms

--- 192.168.1.10 ping statistics ---
18 packets transmitted, 18 packets received, 0% packet loss
round-trip min/avg/max = 6.791/13.462/17.966 ms
_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Reply via email to