Wifi not working after waking

Question

Level 1

6 points

Wifi not working after waking

MacBook's pings to the router gets no response after waking from sleep. Requesting for a new DHCP lease fixes the connection but is annoying to have to do each time I open the laptop.

Packets are still being transferred (received and sent) between the router and laptop even though there's no response to pings. This happens with both my MacBook Air and MacBook Pro running MacOS 10.12 on both dynamically assigned or static IP. This does not happen with other laptops, iPhone 5s, iPhone 6s, iPhone 7, or the same MacBooks when running Windows 10 & Ubuntu.

Logs:

Sat May 20 05:58:23.018 <kernel> wl0: wl_update_tcpkeep_seq: Original Seq: 1032167819, Ack: 2788273341, Win size: 4096

Sat May 20 05:58:23.018 <kernel> wl0: wl_update_tcpkeep_seq: Updated seq/ack/win from UserClient Seq 1032167920, Ack 2788273410, Win size 1374

Sat May 20 05:58:23.018 <kernel> wl0: leaveModulePoweredForOffloads: Wi-Fi will stay on.

Sat May 20 05:58:23.018 <kernel> AirPort_Brcm43xx::platformWoWEnable: WWEN[enable], in_fatal_err[0]

Sat May 20 05:58:23.018 <kernel> AirPort_Brcm43xx::syncPowerState: WWEN[enabled]

Sat May 20 05:58:23.506 <kernel> IO80211Interface::updateReport _peerManager is missing

Sat May 20 05:58:23.633 <kernel> AirPort_Brcm43xx::platformWoWEnable: WWEN[disable], in_fatal_err[0]

Sat May 20 05:58:35.996 <kernel> Setting BTCoex Config: enable_2G:1, profile_2g:0, enable_5G:1, profile_5G:0

Sat May 20 05:58:36.084 <airportd[72]> ERROR: loginwindow (113) is not entitled for com.apple.wifi.events.private, will not register for event type 100

Sat May 20 05:58:36.084 <airportd[72]> ERROR: loginwindow (113) is not entitled for com.apple.wifi.events.private, will not register for event type 101

Sat May 20 05:58:36.085 <airportd[72]> ERROR: loginwindow (113) is not entitled for com.apple.wifi.events, but allowing anyways for event type 7

Sat May 20 05:58:36.085 <airportd[72]> ERROR: loginwindow (113) is not entitled for com.apple.wifi.events, but allowing anyways for event type 2

Sat May 20 05:58:36.085 <airportd[72]> ERROR: loginwindow (113) is not entitled for com.apple.wifi.events, but allowing anyways for event type 1

Sat May 20 05:58:36.086 <airportd[72]> ERROR: loginwindow (113) is not entitled for com.apple.wifi.events, but allowing anyways for event type 5

Sat May 20 05:58:36.103 <airportd[72]> ERROR: loginwindow (113) is not entitled for com.apple.wifi.events, but allowing anyways for event type 6

Sat May 20 05:58:36.525 <airportd[72]> ERROR: WiFiProxy (448) is not entitled for com.apple.wifi.events, but allowing anyways for event type 1

Sat May 20 05:58:36.528 <airportd[72]> ERROR: WiFiProxy (448) is not entitled for com.apple.wifi.events, but allowing anyways for event type 7

Sat May 20 05:58:36.528 <airportd[72]> ERROR: WiFiProxy (448) is not entitled for com.apple.wifi.events, but allowing anyways for event type 2

Sat May 20 05:58:36.528 <airportd[72]> ERROR: WiFiProxy (448) is not entitled for com.apple.wifi.events, but allowing anyways for event type 3

Sat May 20 05:58:36.528 <airportd[72]> ERROR: WiFiProxy (448) is not entitled for com.apple.wifi.events, but allowing anyways for event type 6

Sat May 20 05:58:36.531 <airportd[72]> ERROR: WiFiProxy (448) is not entitled for com.apple.wifi.events, but allowing anyways for event type 5

Sat May 20 05:58:36.547 <airportd[72]> ERROR: WiFiProxy (448) is not entitled for com.apple.wifi.events, but allowing anyways for event type 8

Sat May 20 06:00:52.507 <kernel> IO80211Interface::updateReport _peerManager is missing

MacBook Pro with Retina display, null

Posted on May 20, 2017 3:14 AM

Reply

Answer 1

CarlAVII

Community Specialist

May 21, 2017 1:08 PM in response to Kokowang

Greetings Kokowang,

Thank you for using Apple Support Communities. It seems like when you wake the computer from sleep it will not reconnect to the Wi-Fi. This seems to be isolated to the one computer. You can check to see if the diagnostic can identify what the cause is. If it stays isolated to the one computer it could be the network interface, you can remove Wi-Fi and readd it and see if you are able to maintain the connection.

How to troubleshoot Wi-Fi connectivity

Remove a network location

Choose Apple menu > System Preferences, then click Network.

Click the Location pop-up menu, choose Edit Locations, then select the location you want to remove.

Click the Remove button , click Done, then click Apply.

Create a network location

Choose Apple menu > System Preferences, then click Network.

Click the Location pop-up menu, choose Edit Locations, then click the Add button .

Enter a name for the location, then click Done.

Enter settings for each network port you want to use in that location.

Click Apply.

macOS Sierra: Create and manage network locations
Take care.

Reply

Answer 2

Leanne_68

Community Specialist

May 23, 2017 1:28 PM in response to Kokowang

Hey Kokowang,

Thanks for the update. Since the Wi-Fi connection works in Windows, you have already verified the recommended settings for the router, and this is the only device affected, we would need to isolate what is causing this to happen. One thing you may want to do is create a test user and see if is able to establish a connection or if the issue is system wide.

Use another account for testing

If another user account is already set up on your Mac, you can simply log out of your account (Apple menu > Log Out) and log in with the other account. But the best way to test is with a newly created account:

Choose Apple menu () > System Preferences, then click Users & Groups.

Click , then enter an administrator name and password.

Click the Add button (+) below the list of users.

Complete the fields shown for a Standard or Administrator account, then click Create Account (or OK).

If you plan to test with any of the documents in your own account, make those documents available to the new account. Drag them to the Shared folder of the Users folder on your hard drive (~/Users/Shared). You can then move them to other folders after you log in as the new user.

Then log out of your account and log in with the new account:

Choose Apple menu > Log out.

At the login window, log in with the name and password of the new account. If you're also asked to sign in with an iCloud account or Apple ID, skip that step.

Now try to reproduce the issue in the new account. If you need to set up an email account or other account in order to test, you can do so.

If the issue doesn't happen in the other account

If the issue doesn't happen in the new user account, the issue is related to the settings or files in your own account.

How to test an issue in another user account on your Mac
Cheers.

Reply

Answer 3

mnaile

Level 1

13 points

May 21, 2017 9:33 PM in response to Kokowang

I have this problem also. I tried removing network location and creating new but that didn't help. I have resolved to turning wifi off before putting MBP to sleep and then reenabling wifi when using the next time. Would be nice if someone could offer a solution other than the canned response.

Reply

Answer 4

Kokowang Author

Level 1

6 points

May 23, 2017 1:19 PM in response to Kokowang

Thanks for the responses. I've already tried resetting WiFi and network diagnostics finds no issues. The issue is that the MacBook thinks it's maintaining a connection to the router, but all communications are unresponsive. The MacBook acts as if it's connected and everything is fine, although the router never received any connection requests and never sent back an acknowledgement confirmation signal. (Why is the mac showing that it's connected without ever receiving an ACK signal?).

Even when isolated from interference (only device on network, out of range of all other networks, very low noise floor -92db), the MacBook acts the same way. The Mac also functions perfectly normally when waking from sleep on Windows10 and Ubuntu 16.04, suggesting that's it's a software issue with MacOS. Oddly, this only happens on my home WiFi network. The router is a mid-high end Archer-C3200 configured accordingly to Apple's suggested router settings, and other devices on my network don't experience any issues. I've also tried with static IP to eliminate the possibility that there's an IP lease disagreement between the Mac and the router.

Reply