Modify

Opened 3 years ago

Closed 3 years ago

Last modified 7 months ago

#13966 closed defect (worksforme)

Consistently dropped wifi connections with OSX client

Reported by: Pedro Côrte-Real <pedro@…> Owned by: developers
Priority: normal Milestone: Attitude Adjustment 12.09.1
Component: base system Version: Trunk
Keywords: Cc:

Description

I have a TP-Link TL-WR1043ND running 12.09 final. It has consistently been dropping connections to a Macbook air running OSX 10.7.5. OSX reports that the wifi card is a Broadcom BCM43xx. On the router side the logs show this:

Jul 28 17:30:20 router daemon.notice hostapd: wlan0: STA 28:37:37:19:d2:e6 IEEE 802.11: did not acknowledge authentication response
Jul 28 17:30:23 router daemon.notice hostapd: wlan0: STA 28:37:37:19:d2:e6 IEEE 802.11: did not acknowledge authentication response
Jul 28 17:30:34 router daemon.notice hostapd: wlan0: STA 28:37:37:19:d2:e6 IEEE 802.11: did not acknowledge authentication response
Jul 28 17:30:38 router daemon.notice hostapd: wlan0: STA 28:37:37:19:d2:e6 IEEE 802.11: did not acknowledge authentication response
Jul 28 17:30:41 router daemon.notice hostapd: wlan0: STA 28:37:37:19:d2:e6 IEEE 802.11: did not acknowledge authentication response
Jul 28 17:30:44 router daemon.notice hostapd: wlan0: STA 28:37:37:19:d2:e6 IEEE 802.11: did not acknowledge authentication response
Jul 28 17:30:47 router daemon.notice hostapd: wlan0: STA 28:37:37:19:d2:e6 IEEE 802.11: did not acknowledge authentication response
Jul 28 17:30:50 router daemon.notice hostapd: wlan0: STA 28:37:37:19:d2:e6 IEEE 802.11: did not acknowledge authentication response
Jul 28 17:30:54 router daemon.notice hostapd: wlan0: STA 28:37:37:19:d2:e6 IEEE 802.11: did not acknowledge authentication response
Jul 28 17:30:57 router daemon.notice hostapd: wlan0: STA 28:37:37:19:d2:e6 IEEE 802.11: did not acknowledge authentication response
Jul 28 17:31:01 router daemon.info hostapd: wlan0: STA 28:37:37:19:d2:e6 IEEE 802.11: authenticated
Jul 28 17:31:01 router daemon.info hostapd: wlan0: STA 28:37:37:19:d2:e6 IEEE 802.11: associated (aid 2)
Jul 28 17:31:01 router daemon.info hostapd: wlan0: STA 28:37:37:19:d2:e6 WPA: pairwise key handshake completed (RSN)

while on the client side the logs show this:

7/28/13 6:30:55.000 PM kernel: MacAuthEvent en0   Auth result for: b0:48:7a:bb:46:9a  MAC AUTH succeeded
7/28/13 6:30:55.000 PM kernel: wlEvent: en0 en0 Link UP virtIf = 0
7/28/13 6:30:55.000 PM kernel: wl0: Roamed or switched channel, reason #3, bssid b0:48:7a:bb:46:9a
7/28/13 6:30:55.000 PM kernel: en0: BSSID changed to b0:48:7a:bb:46:9a
7/28/13 6:30:56.000 PM kernel: wlEvent: en0 en0 Link DOWN virtIf = 0
7/28/13 6:30:56.000 PM kernel: AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).
7/28/13 6:30:57.000 PM kernel: MacAuthEvent en0   Auth result for: b0:48:7a:bb:46:9a  MAC AUTH succeeded
7/28/13 6:30:57.000 PM kernel: wlEvent: en0 en0 Link UP virtIf = 0
7/28/13 6:30:57.000 PM kernel: AirPort: Link Up on en0
7/28/13 6:30:57.000 PM kernel: en0: BSSID changed to b0:48:7a:bb:46:9a
7/28/13 6:31:00.000 PM kernel: MacAuthEvent en0   Auth result for: b0:48:7a:bb:46:9a  MAC AUTH succeeded
7/28/13 6:31:00.000 PM kernel: wlEvent: en0 en0 Link UP virtIf = 0
7/28/13 6:31:00.000 PM kernel: wl0: Roamed or switched channel, reason #3, bssid b0:48:7a:bb:46:9a
7/28/13 6:31:00.000 PM kernel: en0: BSSID changed to b0:48:7a:bb:46:9a
7/28/13 6:31:04.000 PM kernel: MacAuthEvent en0   Auth result for: b0:48:7a:bb:46:9a  MAC AUTH succeeded
7/28/13 6:31:04.000 PM kernel: wlEvent: en0 en0 Link UP virtIf = 0
7/28/13 6:31:04.000 PM kernel: wl0: Roamed or switched channel, reason #3, bssid b0:48:7a:bb:46:9a
7/28/13 6:31:04.000 PM kernel: en0: BSSID changed to b0:48:7a:bb:46:9a
7/28/13 6:31:06.000 PM kernel: wlEvent: en0 en0 Link DOWN virtIf = 0
7/28/13 6:31:06.000 PM kernel: AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).
7/28/13 6:31:07.000 PM kernel: MacAuthEvent en0   Auth result for: b0:48:7a:bb:46:9a  MAC AUTH succeeded
7/28/13 6:31:07.000 PM kernel: wlEvent: en0 en0 Link UP virtIf = 0
7/28/13 6:31:07.000 PM kernel: AirPort: Link Up on en0
7/28/13 6:31:07.000 PM kernel: en0: BSSID changed to b0:48:7a:bb:46:9a
7/28/13 6:31:11.000 PM kernel: MacAuthEvent en0   Auth result for: b0:48:7a:bb:46:9a  MAC AUTH succeeded
7/28/13 6:31:11.000 PM kernel: wlEvent: en0 en0 Link UP virtIf = 0
7/28/13 6:31:11.000 PM kernel: wl0: Roamed or switched channel, reason #3, bssid b0:48:7a:bb:46:9a
7/28/13 6:31:11.000 PM kernel: en0: BSSID changed to b0:48:7a:bb:46:9a

I use the same client in another place, where I've installed the same routers running the same version of openwrt and this doesn't happen. The main difference I've been able to establish is that on the other location I control all the access points and have put them on different channels while in this location there are several neighbor controlled ones that are sometimes on the same channel.

I use a Lenovo X220 tablet on the same networks and it works fine in both, so there's something to the osx+openwrt combination.

The router configuration is pretty standard with g+n mode on channel 5 with 20Mhz HT mode. Let me know if you need any additional debugging information.

Attachments (0)

Change History (3)

comment:1 follow-up: Changed 3 years ago by nbd

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

Known issue, this has been fixed after the 12.09 release. The fixes are in the 12.09 git tree, so I'd suggets you build your own image.

comment:2 Changed 2 years ago by pedro@…

Got the same issue on a WDR4300. I'll try building from git to see if this is fixed.

comment:3 in reply to: ↑ 1 Changed 7 months ago by anonymous

Replying to nbd:

Known issue, this has been fixed after the 12.09 release. The fixes are in the 12.09 git tree, so I'd suggets you build your own image.

I have met the similar problem , could you tell me the reason and how to resolve it? thanks.

Add Comment

Modify Ticket

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


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

 
Note: See TracTickets for help on using tickets.