Menu
▾
▴
Re: [Acx100-users] Packet loss/performance problems
|
From: Oliver W. <oli...@ol...> - 2011-12-14 22:07:56
|
Hi Jaime, Just tried on an DG834G v2 with the current driver version (commit 09bebfd), which is also the uptodate version in the OpenWrt trunk, but I don't observe these delays, neither from pings AP->STA nor STA->AP, see below. The kernel etc. however of my installation is still an older trunk version ... I would still need to update this and make another test. If I understand correctly, other clients respond normally to pings from the router, just the phone shows longer delays. Did you already try the phone with other APs, if these delays can be observed there as well ? How is it with other traffic patterns, like e.g. an ssh or scp from the router to the phone ? Difficult to say if it's something with the driver - maybe, but I never observed this with clients here. I'm just wondering, if the wifi of phone could maybe snooze down on low activity, and therefore react with an higher initial latency. That could go inline with the fact, that activity initiated from the phone decreases the delays. But it's just a guess. You could also try to monitor the wifi 802.11 frames with a third station and e.g. wireshark, to see if the router and phone indeed send their respective data/ack frames. I tried that below on a WPA2 link. Best Regards, Oliver --- gamix:~# ping 192.168.2.12 PING 192.168.2.12 (192.168.2.12) 56(84) bytes of data. 64 bytes from 192.168.2.12: icmp_req=1 ttl=64 time=6.78 ms 64 bytes from 192.168.2.12: icmp_req=2 ttl=64 time=3.95 ms 64 bytes from 192.168.2.12: icmp_req=3 ttl=64 time=4.06 ms 64 bytes from 192.168.2.12: icmp_req=4 ttl=64 time=6.69 ms 64 bytes from 192.168.2.12: icmp_req=5 ttl=64 time=4.55 ms 64 bytes from 192.168.2.12: icmp_req=6 ttl=64 time=4.70 ms 64 bytes from 192.168.2.12: icmp_req=7 ttl=64 time=4.02 ms 64 bytes from 192.168.2.12: icmp_req=8 ttl=64 time=4.50 ms 64 bytes from 192.168.2.12: icmp_req=9 ttl=64 time=5.99 ms 64 bytes from 192.168.2.12: icmp_req=10 ttl=64 time=5.32 ms 64 bytes from 192.168.2.12: icmp_req=11 ttl=64 time=2.13 ms 64 bytes from 192.168.2.12: icmp_req=12 ttl=64 time=4.73 ms 64 bytes from 192.168.2.12: icmp_req=13 ttl=64 time=4.54 ms 64 bytes from 192.168.2.12: icmp_req=14 ttl=64 time=4.85 ms 64 bytes from 192.168.2.12: icmp_req=15 ttl=64 time=4.96 ms --- root@dg834gv2:~/Test# ping 192.168.2.4 PING 192.168.2.4 (192.168.2.4): 56 data bytes 64 bytes from 192.168.2.4: seq=0 ttl=64 time=7.120 ms 64 bytes from 192.168.2.4: seq=1 ttl=64 time=5.527 ms 64 bytes from 192.168.2.4: seq=2 ttl=64 time=5.493 ms 64 bytes from 192.168.2.4: seq=3 ttl=64 time=2.656 ms 64 bytes from 192.168.2.4: seq=4 ttl=64 time=4.494 ms 64 bytes from 192.168.2.4: seq=5 ttl=64 time=5.628 ms 64 bytes from 192.168.2.4: seq=6 ttl=64 time=6.899 ms 64 bytes from 192.168.2.4: seq=7 ttl=64 time=2.904 ms 64 bytes from 192.168.2.4: seq=8 ttl=64 time=6.118 ms 64 bytes from 192.168.2.4: seq=9 ttl=64 time=3.576 ms 64 bytes from 192.168.2.4: seq=10 ttl=64 time=6.710 ms 64 bytes from 192.168.2.4: seq=11 ttl=64 time=5.485 ms 64 bytes from 192.168.2.4: seq=12 ttl=64 time=5.959 ms 64 bytes from 192.168.2.4: seq=13 ttl=64 time=4.807 ms 64 bytes from 192.168.2.4: seq=14 ttl=64 time=5.386 ms 64 bytes from 192.168.2.4: seq=15 ttl=64 time=6.790 ms 64 bytes from 192.168.2.4: seq=16 ttl=64 time=6.082 ms 64 bytes from 192.168.2.4: seq=17 ttl=64 time=4.789 ms 64 bytes from 192.168.2.4: seq=18 ttl=64 time=5.362 ms --- 1180 39.752261 Trend_cd:f5:c8 Intel_98:86:d8 LLC -20 I, N(R)=16, N(S)=0; DSAP 0x8a Individual, SSAP LLC 1181 39.752470 Trend_cd:f5:c8 (RA) 802.11 -42 Acknowledgement, Flags=........C 1182 39.753103 Intel_98:86:d8 Trend_cd:f5:c8 LLC -44 I, N(R)=16, N(S)=0; DSAP 0x8c Individual, SSAP LLC 1183 39.753355 Intel_98:86:d8 (RA) 802.11 -17 Acknowledgement, Flags=........C 1203 40.753452 Trend_cd:f5:c8 Intel_98:86:d8 LLC -20 I, N(R)=16, N(S)=0; DSAP 0x8a Group, SSAP LLC 1204 40.753652 Trend_cd:f5:c8 (RA) 802.11 -44 Acknowledgement, Flags=........C 1206 40.755904 Intel_98:86:d8 Trend_cd:f5:c8 LLC -43 I, N(R)=16, N(S)=0; DSAP 0x8c Group, SSAP LLC 1207 40.756155 Intel_98:86:d8 (RA) 802.11 -18 Acknowledgement, Flags=........C 1239 41.754649 Trend_cd:f5:c8 Intel_98:86:d8 LLC -19 I, N(R)=16, N(S)=0; DSAP 0x8c Individual, SSAP 1240 41.754857 Trend_cd:f5:c8 (RA) 802.11 -44 Acknowledgement, Flags=........C --- On 12/14/2011 10:31 AM, Jaime T wrote: > Hi. > > Thank you to all the developers that have worked on the drivers for > the wireless chip in my Netgear DG834G (v2) ADSL wireless router. I'm > using Openwrt's trunk on the box and wireless works well. > > I get packet-loss problems, however, with one of the wireless clients. > If I ping from the router to my android phone, I get the following > kind of result (the packets between seq# 16 and seq# 260 disappear): > > root@OpenWrt:~# ping 192.168.0.134 > PING 192.168.0.134 (192.168.0.134): 56 data bytes > 64 bytes from 192.168.0.134: seq=0 ttl=64 time=5981.923 ms > 64 bytes from 192.168.0.134: seq=1 ttl=64 time=4980.768 ms > 64 bytes from 192.168.0.134: seq=2 ttl=64 time=3984.334 ms > 64 bytes from 192.168.0.134: seq=3 ttl=64 time=2983.757 ms > 64 bytes from 192.168.0.134: seq=4 ttl=64 time=1983.329 ms > 64 bytes from 192.168.0.134: seq=5 ttl=64 time=982.866 ms > 64 bytes from 192.168.0.134: seq=6 ttl=64 time=2.305 ms > 64 bytes from 192.168.0.134: seq=7 ttl=64 time=3987.770 ms > 64 bytes from 192.168.0.134: seq=8 ttl=64 time=2987.478 ms > 64 bytes from 192.168.0.134: seq=9 ttl=64 time=1989.163 ms > 64 bytes from 192.168.0.134: seq=10 ttl=64 time=988.934 ms > 64 bytes from 192.168.0.134: seq=11 ttl=64 time=2.360 ms > 64 bytes from 192.168.0.134: seq=12 ttl=64 time=3999.889 ms > 64 bytes from 192.168.0.134: seq=13 ttl=64 time=3000.279 ms > 64 bytes from 192.168.0.134: seq=14 ttl=64 time=2006.232 ms > 64 bytes from 192.168.0.134: seq=15 ttl=64 time=1006.624 ms > 64 bytes from 192.168.0.134: seq=16 ttl=64 time=5.243 ms > 64 bytes from 192.168.0.134: seq=260 ttl=64 time=2022.973 ms > 64 bytes from 192.168.0.134: seq=261 ttl=64 time=1024.080 ms > 64 bytes from 192.168.0.134: seq=262 ttl=64 time=24.571 ms > > Does the regular pattern of time delay mean anything to anyone? > Interestingly, if I ping the router from the phone at the same time, > these problems disappear: > > root@OpenWrt:~# ping 192.168.0.7 > PING 192.168.0.7 (192.168.0.7): 56 data bytes > 64 bytes from 192.168.0.7: seq=18 ttl=64 time=15.138 ms > 64 bytes from 192.168.0.7: seq=19 ttl=64 time=4.984 ms > 64 bytes from 192.168.0.7: seq=20 ttl=64 time=4.986 ms > 64 bytes from 192.168.0.7: seq=21 ttl=64 time=3.300 ms > 64 bytes from 192.168.0.7: seq=22 ttl=64 time=912.268 ms > 64 bytes from 192.168.0.7: seq=23 ttl=64 time=4.089 ms > 64 bytes from 192.168.0.7: seq=24 ttl=64 time=2921.293 ms > 64 bytes from 192.168.0.7: seq=25 ttl=64 time=1925.985 ms > 64 bytes from 192.168.0.7: seq=26 ttl=64 time=925.776 ms > 64 bytes from 192.168.0.7: seq=27 ttl=64 time=3.917 ms > 64 bytes from 192.168.0.7: seq=209 ttl=64 time=174.194 ms > 64 bytes from 192.168.0.7: seq=210 ttl=64 time=174.782 ms > 64 bytes from 192.168.0.7: seq=211 ttl=64 time=175.447 ms > 64 bytes from 192.168.0.7: seq=212 ttl=64 time=176.279 ms > 64 bytes from 192.168.0.7: seq=213 ttl=64 time=177.976 ms > 64 bytes from 192.168.0.7: seq=214 ttl=64 time=178.428 ms > 64 bytes from 192.168.0.7: seq=215 ttl=64 time=177.975 ms > 64 bytes from 192.168.0.7: seq=216 ttl=64 time=179.094 ms > > (I started pinging the router from the phone at about seq# 209). > > Is there anything that I could do to improve the wireless > connectivity? I appreciate that I haven't given lots of info to work > with - if a tcpdump capture from a third host would help, please let > me know. > > With kind regards, > > Jaime > > ------------------------------------------------------------------------------ > Cloud Computing - Latest Buzzword or a Glimpse of the Future? > This paper surveys cloud computing today: What are the benefits? > Why are businesses embracing it? What are its payoffs and pitfalls? > http://www.accelacomm.com/jaw/sdnl/114/51425149/ > _______________________________________________ > Acx100-users mailing list > Acx...@li... > https://lists.sourceforge.net/lists/listinfo/acx100-users > |