Opened 6 years ago

Closed 6 years ago

Last modified 4 years ago

#11122 closed defect (no_response)

sharp decline in performance with macbook client and wzr-hp-g300nh

Reported by: bh Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: wzr-hp-g300nh macbook wireless Cc:


My previous flash was a Feb 25th build of trunk to a Buffalo WZR-HP-G300NH and I just yesterday flashed to the latest trunk on Mar 11th. Since that flash I have been experiencing extremely poor performance with only one client on my network, my macbook. No matter where I operate the macbook in relation to the router in my house, no matter which channel I select I cannot get a stable connection. Pings from the router to the macbook vary wildly:

root@OpenWrt:~# ping
PING ( 56 data bytes
64 bytes from seq=0 ttl=64 time=13.971 ms
64 bytes from seq=1 ttl=64 time=185.046 ms
64 bytes from seq=2 ttl=64 time=204.523 ms
64 bytes from seq=3 ttl=64 time=18.244 ms
64 bytes from seq=4 ttl=64 time=165.617 ms
64 bytes from seq=5 ttl=64 time=35.852 ms
64 bytes from seq=6 ttl=64 time=115.446 ms
64 bytes from seq=13 ttl=64 time=153.626 ms
64 bytes from seq=15 ttl=64 time=108.933 ms
64 bytes from seq=17 ttl=64 time=275.907 ms
64 bytes from seq=19 ttl=64 time=214.280 ms
64 bytes from seq=20 ttl=64 time=165.035 ms
64 bytes from seq=21 ttl=64 time=48.639 ms
64 bytes from seq=22 ttl=64 time=306.898 ms

In addition to wildly fluctuating pings I am experiencing "timeouts" where the wireless connection becomes unresponsive until I cycle wireless on the macbook client. I must stress that there have been no changes in my network configuration aside from the flash to the latest trunk and that every other client on the network is experiencing no technical issue. I must also stress that the macbook client interacted flawlessly with the WZR-HP-G300NH router before the flash to the latest trunk.

I see nothing in the OpenWRT logs that would indicate a problem with the router. If there is any additional information that might help troubleshoot this issue please respond.

Attachments (0)

Change History (8)

comment:1 Changed 6 years ago by bh

I flashed to a new compile of backfire and the problem has gone away. I think there must be something in the latest ath9k/mac80211 trunk fixes that my macbook doesn't like.

comment:2 Changed 6 years ago by nbd

Please try removing package/mac80211/patches/56* in trunk, rebuild and see if that fixes the issue.

comment:3 Changed 6 years ago by bh

Rebuilt after deleting the patches you specified and flashed... macbook client performance looks like it's back to normal. I'll keep an eye on this ticket if you'd like to test a different set of patches.

comment:4 Changed 6 years ago by nbd

Please try latest svn (without removing any patches).

comment:5 Changed 6 years ago by bh

PING ( 56 data bytes
64 bytes from icmp_seq=0 ttl=64 time=12.611 ms
64 bytes from icmp_seq=1 ttl=64 time=21.529 ms
64 bytes from icmp_seq=2 ttl=64 time=1.404 ms
64 bytes from icmp_seq=3 ttl=64 time=1.331 ms
64 bytes from icmp_seq=4 ttl=64 time=18.749 ms
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
64 bytes from icmp_seq=7 ttl=64 time=113.541 ms
64 bytes from icmp_seq=8 ttl=64 time=213.323 ms
64 bytes from icmp_seq=9 ttl=64 time=6.590 ms
Request timeout for icmp_seq 10
64 bytes from icmp_seq=11 ttl=64 time=10.295 ms
Request timeout for icmp_seq 12
64 bytes from icmp_seq=13 ttl=64 time=62.811 ms
64 bytes from icmp_seq=14 ttl=64 time=67.002 ms
64 bytes from icmp_seq=15 ttl=64 time=1.413 ms
64 bytes from icmp_seq=16 ttl=64 time=1.372 ms
Request timeout for icmp_seq 17
64 bytes from icmp_seq=18 ttl=64 time=34.019 ms
Request timeout for icmp_seq 19
64 bytes from icmp_seq=20 ttl=64 time=100.463 ms
64 bytes from icmp_seq=21 ttl=64 time=35.118 ms
--- ping statistics ---
22 packets transmitted, 16 packets received, 27.3% packet loss
round-trip min/avg/max/stddev = 1.331/43.848/213.323/55.725 ms

I'm not getting the timeouts any longer but much more packet loss/ping fluctuation than backfire with an identical configuration.

comment:6 Changed 6 years ago by nbd

please try latest svn again, some more fixes went in.

comment:7 Changed 6 years ago by nbd

  • Resolution set to no_response
  • Status changed from new to closed

comment:8 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

as closed .
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.