Hi Chistian, I think I found the reason. a long time ago I change the setting "Beacon Interval" of my wireless router to 5sec. Its working fine with all other clients. However changing it back to 100ms resulted in muuuuuch lesser ping timings, like yours. I will observe the behavior further (I got to go now). If I do not write anything any more, the problem is solved.
If you have a linksys (cisco) router (mine is a WRT54G) and have long ping timings, check the beacon interval in the settings "Wireless" -> "Advance Wireless Settings". From the help: "The Beacon Interval value indicates the frequency interval of the beacon. A beacon is a packet broadcast by the Router to synchronize the wireless network." Cheers, Alex Christian Rüb wrote: > Hi Alex, > > wifi is still not really stable in general (still some open issues) but > currently I get this: > r...@om-gta02 ~ $ ping www.heise.de > PING www.heise.de (193.99.144.85): 56 data bytes > 64 bytes from 193.99.144.85: seq=0 ttl=249 time=69.545 ms > 64 bytes from 193.99.144.85: seq=1 ttl=249 time=113.702 ms > 64 bytes from 193.99.144.85: seq=2 ttl=248 time=120.918 ms > 64 bytes from 193.99.144.85: seq=3 ttl=249 time=140.916 ms > 64 bytes from 193.99.144.85: seq=4 ttl=248 time=160.834 ms > 64 bytes from 193.99.144.85: seq=5 ttl=249 time=76.075 ms > 64 bytes from 193.99.144.85: seq=6 ttl=249 time=96.110 ms > ^C > --- www.heise.de ping statistics --- > 7 packets transmitted, 7 packets received, 0% packet loss > round-trip min/avg/max = 69.545/111.157/160.834 ms > > So this is far below 2secs... > So I doubt it is somehow wpa_supplicant related. > > Cheers, > Christian > > > >> Hi Christian >> >> Thanks for the scripts. I copied them and adapted the configuration >> files as mentioned in the readme. However, I have (maybe a stupid) >> question: How well does Wifi work for you after assigning to an AP? >> Whenever I have a stable connection, pinging the AP takes enormous >> times. In _average_ I have ping timings around 3 seconds and the AP is >> not even 2 meters away. That is way too much for most chat clients and >> web browsers, which return with an Handshake-failed or website-not-found >> error. Is there something I can do? (Sorry, if it had already been >> discussed here. Either I missed it or I forgot.) >> >> Thanks, >> Alex >> >> Christian Rüb wrote: >> >>> >>> +1 >>> >>> I have been using a wireless roaming setup Debian-like. This means I had to >>> edit interfaces and wpa_supplicant.conf manually but it then works without >>> any user interaction necessary. >>> I have the scripts (little changes + additions to basic moko setup) tared >>> here and also a little README for those interested. >>> I will continue using it until there is something usable for the GUI (that >>> also supports static IPs). >>> >>> http://openmoko.senfdax.de/shr-unstable/wpa-roaming.README >>> http://openmoko.senfdax.de/shr-unstable/wpa-roaming.tar >>> >>> Cheers, >>> Christian >>> >>> _______________________________________________ >>> Shr-User mailing list >>> [email protected] >>> http://lists.shr-project.org/mailman/listinfo/shr-user >>> >>> >>> >> _______________________________________________ >> Shr-User mailing list >> [email protected] >> http://lists.shr-project.org/mailman/listinfo/shr-user >> >> > > _______________________________________________ > Shr-User mailing list > [email protected] > http://lists.shr-project.org/mailman/listinfo/shr-user > > _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
