Yosemite WiFi bug

I will take you up on a copy of the script; I've had the problem occur maybe 3-4 times now since the update. It will be nice not having to reboot every time.

OK, I'm gonna insert the script here in the reply. To the admins, if that's not permitted, please feel free to whack the script from this response, and let me know how best to post that up here for folks to use.

I've tried to comment to script pretty well. The only edit you have to make to the script is to properly reflect the en# of your airport card -- I couldn't figure out how to easily self-detect that.

You can change the sleep at the end of the script for your circumstances. I check the airport card every five minutes, and that seems to work, but I've had it checked as often as 15 seconds with no apparent ill effects.

The syslog logging will let you look in Console (search for "Wifiscript"), to see what your airport card is doing (or not) for each of the disable/enable steps in the script. It'll also give you an easy-to-find point in the logs to examine what was going on just before the airport card failure.

I invoke this script with the following command line in a Terminal session that I leave running on the machine:

sudo ./wifi.sh | tee wifi.out

Some of the commands for playing with the airport card require elevated privileges, hence the sudo. The tee lets you capture the output to a file for later use if that's important to you. If not, you can drop that from the command line.

YMMV. This works for me on my MacPro (2013), and the symptoms it's exhibiting. It may not work for you. There's nothing insidious or dangerous about this code as far as I know, but I *highly* encourage you to examine the script and make sure you're comfy with what it does. In other words, don't take my word for its functionality!!! :-) Feel free to use/modify this code however you'd like.

Here's the code:

#! /usr/bin/env bash

### setup some variables

wifiInterface="en2"

wifiIP=$(ipconfig getifaddr "$wifiInterface")

echo "Watching" $wifiInterface "on" $wifiIP

while true; do

### getting the IP address inside the loop protects against DHCP changes

wifiIP=$(ipconfig getifaddr "$wifiInterface")

### print the date to the terminal window

echo -n "$(date ) via $wifiIP : "

### write to the syslog that we're trying dig

syslog -s -k Facility com.apple.console Level Error Sender Wifiscript Message "dig attempt via "$wifiIP" "

dig @8.8.8.8 -b "$wifiIP" +tries=1 +time=3 google.com | \

grep 'Query time' | \

cut -d ' ' -f 4 -f 5

if [ ${PIPESTATUS[0]} -ne 0 ] ; then

echo " "

echo "*** WIFI ERROR #1 DETECTED -- Trying again ***"

syslog -s -k Facility com.apple.console Level Error Sender Wifiscript Message "*** WIFI ERROR #1 DETECTED -- Trying again ***"

### a second attempt is made in case there's some external issue that caused the first dig to fail

### print the date to the terminal window

echo -n "$(date ) via $wifiIP : "

### write to the syslog that we're trying dig

syslog -s -k Facility com.apple.console Level Error Sender Wifiscript Message "dig attempt via "$wifiIP" "

dig @8.8.8.8 -b "$wifiIP" +tries=1 +time=3 google.com | \

grep 'Query time' | \

cut -d ' ' -f 4 -f 5

if [ ${PIPESTATUS[0]} -ne 0 ] ; then

echo "*** WIFI ERROR #2 DETECTED ***"

syslog -s -k Facility com.apple.console Level Error Sender Wifiscript Message "*** WIFI ERROR #2 DETECTED ***"

echo " . Bringing "$wifiInterface" down and waiting five seconds..."

syslog -s -k Facility com.apple.console Level Error Sender Wifiscript Message "---> Bringing "$wifiInterface" down and waiting five seconds"

ifconfig "$wifiInterface" down

sleep 5

echo " . Turning off Airport and waiting five seconds..."

syslog -s -k Facility com.apple.console Level Error Sender Wifiscript Message "---> Turning off Airport and waiting five seconds"

networksetup -setairportpower "$wifiInterface" off

sleep 5

echo " . Turning on Airport and waiting five seconds..."

syslog -s -k Facility com.apple.console Level Error Sender Wifiscript Message "---> Turning on Airport and waiting five seconds"

networksetup -setairportpower "$wifiInterface" on

sleep 5

echo " . Bringing "$wifiInterface" up and waiting five seconds..."

syslog -s -k Facility com.apple.console Level Error Sender Wifiscript Message "---> Bringing "$wifiInterface" up and waiting five seconds"

ifconfig "$wifiInterface" up

sleep 5

echo "*** WIFI RECOVERY ATTEMPT COMPLETED ***"

syslog -s -k Facility com.apple.console Level Error Sender Wifiscript Message "*** WIFI RECOVERY ATTEMPT COMPLETED ***"

fi

fi

### pause for five minutes

sleep 300

done

Nice, thanks Colin! If I option-click my airport icon in the menu bar it tells me the interface name ("en1" for me). And I'm assuming I can either leave it running in the background to detect/correct the issue automatically, or I would imagine I can just open terminal and run the script when the issue occurs to hopefully correct without a reboot?

I'll keep you posted if it works for me the next time my card crashes.

You're very welcome! I hope it works for you, too. I generally just leave it running inside Terminal, and look at it every now and then to see if there's anything worth looking at.

It should be able to recover the card (assuming the same symptom as my Mac) whenever you notice the card is down. Leaving it running all the time avoids that, though! :-)

Interesting, it caused my computer to crash, in exactly the same way as when I go to Network Preferences and make wifi inactive after the issue occurs (complete freeze, then just powers down). I may have to mess with it a little. I have noticed that if I try and fail to turn wifi off and on before making the wifi inactive, the crash doesn't happen. I'll report back after I experiment some. The crash occurred when trying to bring Airport back up.

Ugh. I hate to hear that. I guess that confirms that what your and my Macs are doing is different. Hopefully some of the steps in the script will help nail down what's going on. If it would help, I can force a failure on my side (basically, turning off my card, and letting the script pick that up and "recover" it) and post the results from Console so you can compare against what my card is doing. Would that be helpful for you?

Possibly. I still think the errors are very similar. The problem is, with the freeze, my console doesn't really tell me anything? I have the "***WIFI ERROR #1" message in there, then everything is blank for two minutes (I think until I started back up). It doesn't even have the message from the second dig....

When mine goes down again, I'll see if I can prevent a freeze when the script runs; whatever I end up doing can then probably be worked into the script to be automatic.

I guess it does have the second dig attempt but that's it. But watching the Terminal while it was working, it reported ERROR #2, brought en1 down, brought Airport down, and was bringing Airport back up when it froze.

2/1/15 7:02:29.737 AM Wifiscript[1387]: dig attempt via 10.0.0.33

2/1/15 7:02:32.822 AM Wifiscript[1391]: *** WIFI ERROR #1 DETECTED -- Trying again ***

2/1/15 7:02:32.829 AM Wifiscript[1393]: dig attempt via 10.0.0.33

2/1/15 7:04:17.000 AM bootlog[0]: BOOT_TIME 1422803057 0

Man, that sure sounds like some kinda flakey problem. Normally, I'd think it was hardware related, but the intermittent nature of it doesn't support it being a hardware problem very well.

In my case, I think I'm gonna start tracking information from the command line airport utility via my script, to see if there's something else at play -- signal strength, etc. I am seeing a ton of ARPT AWDL Sync Enabled 0 and ARPT AWDL Sync Enabled 1 messages in the logs. They may have been there for a while, but they're Airport messages, and that's where I'm seeing this problem. Dunno if that's a factor or not, but I see some chatter that AWDL (which is a peer-to-peer connection across the wifi for AirDrop) may be a factor for why some are seeing weirdness with their wifi. You can turn it off (sudo ifconfig awdl0 down) at the cost of losing at least AirDrop, but I've done no testing to see if that improves my situation, and I don't know if there are further consequences than just to the AirDrop functionality.

Here's what happens in my logs when the script does a recover. This was from an actual failure this morning. I don't know if this'll tell you much, but it does give you something to compare against.

2/1/15 7:40:44.507 AM Wifiscript[13020]: dig attempt via 172.16.1.12

2/1/15 7:40:47.522 AM Wifiscript[13024]: *** WIFI ERROR #1 DETECTED -- Trying again ***

2/1/15 7:40:47.526 AM Wifiscript[13026]: dig attempt via 172.16.1.12

2/1/15 7:40:50.536 AM Wifiscript[13030]: *** WIFI ERROR #2 DETECTED ***

2/1/15 7:40:50.538 AM Wifiscript[13031]: ---> Bringing en2 down and waiting five seconds

2/1/15 7:40:50.000 AM kernel[0]: AirPort: Link Down on en2. Reason 8 (Disassociated because station leaving).

2/1/15 7:40:50.000 AM kernel[0]: en2::IO80211Interface::postMessage bssid changed

2/1/15 7:40:50.000 AM kernel[0]: ARPT: 390649.621324: AWDL Sync Enabled 1

2/1/15 7:40:50.000 AM kernel[0]: ARPT: 390649.621333: Failed to set AWDL Sync Enabled state (1), error code -4

2/1/15 7:40:50.000 AM kernel[0]: IO80211AWDLPeerManager::failToEnable

2/1/15 7:40:50.000 AM kernel[0]: IO80211AWDLPeerManager::interfaceStateChange can t enable awdl!

2/1/15 7:40:50.000 AM kernel[0]: en2: 802.11d country code set to 'X0'.

2/1/15 7:40:50.000 AM kernel[0]: en2: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165

2/1/15 7:40:50.000 AM kernel[0]: IO80211AWDLPeerManager::doDisable source [handleSIOCSIFFLAGS]

2/1/15 7:40:50.000 AM kernel[0]: AirPort: Link Down on awdl0. Reason 1 (Unspecified).

2/1/15 7:40:50.000 AM kernel[0]: IO80211AWDLPeerManager::doDisable source [setLinkState]

2/1/15 7:40:50.560 AM airportd[33]: _handleLinkEvent: WiFi is not powered. Resetting state variables.

2/1/15 7:40:50.813 AM UserEventAgent[19]: Captive: CNPluginHandler en2: Inactive

2/1/15 7:40:50.814 AM configd[28]: network changed: v4(en0:172.16.1.10, en2-:172.16.1.12) DNS* Proxy SMB

2/1/15 7:40:50.815 AM discoveryd[52]: Basic Bonjour stop listening on awdl0

2/1/15 7:40:50.815 AM discoveryd[52]: Basic Bonjour stop listening on en2

2/1/15 7:40:55.570 AM Wifiscript[13035]: ---> Turning off Airport and waiting five seconds

2/1/15 7:41:00.659 AM Wifiscript[13040]: ---> Turning on Airport and waiting five seconds

2/1/15 7:41:01.000 AM kernel[0]: en2: channel changed to 1

2/1/15 7:41:01.000 AM kernel[0]: AirPort: Link Up on awdl0

2/1/15 7:41:01.000 AM kernel[0]: IO80211AWDLPeerManager::configure Dynamic country code not supported on this device

2/1/15 7:41:01.000 AM kernel[0]: ARPT: 390660.297020: AWDL Sync Enabled 1

2/1/15 7:41:01.000 AM kernel[0]: en2: channel changed to 1

2/1/15 7:41:01.000 AM kernel[0]: IO80211AWDLPeerManager::setAwdlOperatingMode Setting the AWDL operation mode from AUTO to SUSPENDED

2/1/15 7:41:01.000 AM kernel[0]: IO80211AWDLPeerManager::setAwdlSuspendedMode() Suspending AWDL, enterQuietMode(true)

2/1/15 7:41:01.000 AM kernel[0]: ARPT: 390660.410860: AWDL Sync Enabled 0

2/1/15 7:41:01.000 AM kernel[0]: en2: 802.11d country code set to 'US'.

2/1/15 7:41:01.000 AM kernel[0]: en2: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165

2/1/15 7:41:01.000 AM kernel[0]: ARPT: 390660.539133: MacAuthEvent en2 Auth result for: 00:26:bb:75:fd:fe MAC AUTH succeeded

2/1/15 7:41:01.000 AM kernel[0]: AirPort: Link Up on en2

2/1/15 7:41:01.000 AM kernel[0]: en2: BSSID changed to 00:26:bb:75:fd:fe

2/1/15 7:41:01.000 AM kernel[0]: en2: channel changed to 161,-1

2/1/15 7:41:01.000 AM kernel[0]: en2::IO80211Interface::postMessage bssid changed

2/1/15 7:41:01.487 AM configd[28]: arp_client_transmit(en2) failed, Network is down (50)

2/1/15 7:41:01.487 AM configd[28]: [bootp_transmit.c:213] bootp_transmit(): bpf_write(en2) failed: Network is down (50)

2/1/15 7:41:01.487 AM configd[28]: DHCP en2: INIT-REBOOT transmit failed

2/1/15 7:41:01.487 AM configd[28]: DHCP en2: ARP detect ROUTER failed, arp_client_transmit(en2) failed, Network is down (50)

2/1/15 7:41:01.878 AM discoveryd[52]: Basic DNSResolver Error 9 on socket - this might be a closed socket

2/1/15 7:41:03.559 AM configd[28]: arp_client_transmit(en2) failed, Network is down (50)

2/1/15 7:41:03.560 AM configd[28]: [bootp_transmit.c:213] bootp_transmit(): bpf_write(en2) failed: Network is down (50)

2/1/15 7:41:03.560 AM configd[28]: DHCP en2: INIT-REBOOT transmit failed

2/1/15 7:41:03.560 AM configd[28]: DHCP en2: ARP detect ROUTER failed, arp_client_transmit(en2) failed, Network is down (50)

2/1/15 7:41:03.640 AM discoveryd[52]: AwdlD2d AwdlD2dStartAdvertisingPair: 'bagel-warmer' Advertising service started

2/1/15 7:41:03.641 AM discoveryd[52]: AwdlD2d AwdlD2dStartAdvertisingPair: 'bagel-warmer' Advertising service started

2/1/15 7:41:03.643 AM discoveryd[52]: AwdlD2d AwdlD2dStartAdvertisingPair: '2aafbaefff98728200000000000008efip6arpa' Advertising service started

2/1/15 7:41:04.439 AM locationd[58]: NETWORK: requery, 0, 0, 0, 0, 1, items, fQueryRetries, 0, fLastRetryTimestamp, 444450276.8

2/1/15 7:41:05.000 AM kernel[0]: AirPort: Link Down on en2. Reason 8 (Disassociated because station leaving).

2/1/15 7:41:05.000 AM kernel[0]: en2: channel changed to 1

2/1/15 7:41:05.000 AM kernel[0]: en2::IO80211Interface::postMessage bssid changed

2/1/15 7:41:05.000 AM kernel[0]: en2: 802.11d country code set to 'X0'.

2/1/15 7:41:05.000 AM kernel[0]: en2: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165

2/1/15 7:41:06.000 AM kernel[0]: ARPT: 390665.114201: MacAuthEvent en2 Auth result for: 00:26:bb:75:fd:fe MAC AUTH succeeded

2/1/15 7:41:06.000 AM kernel[0]: AirPort: Link Up on en2

2/1/15 7:41:06.000 AM kernel[0]: en2: BSSID changed to 00:26:bb:75:fd:fe

2/1/15 7:41:06.000 AM kernel[0]: en2: channel changed to 161,-1

2/1/15 7:41:06.000 AM kernel[0]: en2::IO80211Interface::postMessage bssid changed

2/1/15 7:41:06.061 AM configd[28]: arp_client_transmit(en2) failed, Network is down (50)

2/1/15 7:41:06.061 AM configd[28]: [bootp_transmit.c:213] bootp_transmit(): bpf_write(en2) failed: Network is down (50)

2/1/15 7:41:06.061 AM configd[28]: DHCP en2: INIT-REBOOT transmit failed

2/1/15 7:41:06.061 AM configd[28]: DHCP en2: ARP detect ROUTER failed, arp_client_transmit(en2) failed, Network is down (50)

2/1/15 7:41:06.000 AM kernel[0]: en2: 802.11d country code set to 'US'.

2/1/15 7:41:06.000 AM kernel[0]: en2: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165

2/1/15 7:41:06.207 AM Wifiscript[13044]: ---> Bringing en2 up and waiting five seconds

2/1/15 7:41:06.000 AM kernel[0]: en2: BSSID changed to 00:26:bb:75:fd:fe

2/1/15 7:41:06.000 AM kernel[0]: en2: channel changed to 161,-1

2/1/15 7:41:06.000 AM kernel[0]: en2: BSSID changed to 00:26:bb:75:fd:fe

2/1/15 7:41:06.000 AM kernel[0]: en2: channel changed to 161,-1

2/1/15 7:41:07.000 AM kernel[0]: AirPort: RSN handshake complete on en2

2/1/15 7:41:07.000 AM kernel[0]: IO80211AWDLPeerManager::setAwdlOperatingMode Setting the AWDL operation mode from SUSPENDED to AUTO

2/1/15 7:41:07.000 AM kernel[0]: IO80211AWDLPeerManager::setAwdlAutoMode Resuming AWDL

2/1/15 7:41:07.000 AM kernel[0]: ARPT: 390666.480957: AWDL Sync Enabled 1

2/1/15 7:41:07.420 AM configd[28]: network changed: v4(en0:172.16.1.10) DNS* Proxy SMB

2/1/15 7:41:07.421 AM UserEventAgent[19]: Captive: [CNInfoNetworkActive:1709] en2: SSID 'MY_WIFI_NETWORK_NAME' making interface primary (cache indicates network not captive)

2/1/15 7:41:07.421 AM UserEventAgent[19]: Captive: CNPluginHandler en2: Evaluating

2/1/15 7:41:07.423 AM UserEventAgent[19]: Captive: en2: Not probing 'MY_WIFI_NETWORK_NAME' (cache indicates not captive)

2/1/15 7:41:07.423 AM UserEventAgent[19]: Captive: CNPluginHandler en2: Authenticated

2/1/15 7:41:07.426 AM configd[28]: network changed: v4(en0:172.16.1.10, en2!:172.16.1.12) DNS Proxy SMB

2/1/15 7:41:07.000 AM kernel[0]: en2: BSSID changed to 00:26:bb:75:fd:fe

2/1/15 7:41:07.000 AM kernel[0]: en2: channel changed to 161,-1

2/1/15 7:41:11.218 AM Wifiscript[13048]: *** WIFI RECOVERY ATTEMPT COMPLETED ***

2/1/15 7:41:34.000 AM kernel[0]: ARPT: 390693.679416: AWDL Sync Enabled 0

2/1/15 7:46:11.214 AM Wifiscript[13056]: dig attempt via 172.16.1.12

Just an update... I've had AWDL disabled for 48 hours (almost), and things have been very quiet. Maybe that's a clue, or maybe that's wishful thinking. :-)

It's now been five days since I've had a wifi event. I'm not saying that turning off AWDL is why, but my good fortune does seem to started when I turned it off.

I'm really hoping this is a workaround for my wifi card flakiness!

Can someone help me? At home the Wifi work fine, but at work i dont have internet...

Thu Feb 5 17:17:51.888 ***Starting Up***

Thu Feb 5 17:17:57.521 <airportd[33]> airportdProcessDLILEvent: en0 attached (down)

Thu Feb 5 20:47:11.870 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Thu Feb 5 20:50:25.234 <airportd[33]> _handleLinkEvent: Got an error trying to query WiFi for power. Resetting state variables.

Thu Feb 5 20:51:15.875 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Thu Feb 5 21:01:52.740 <kernel> AWDL Sync Enabled 1

Thu Feb 5 21:02:27.633 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Thu Feb 5 21:02:32.820 <kernel> AWDL Sync Enabled 0

Thu Feb 5 21:18:53.235 <airportd[33]> _handleLinkEvent: Got an error trying to query WiFi for power. Resetting state variables.

Thu Feb 5 21:21:11.627 <kernel> AWDL Sync Enabled 1

Thu Feb 5 21:21:42.678 <kernel> AWDL Sync Enabled 0

Thu Feb 5 22:15:44.996 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Thu Feb 5 22:48:23.228 <airportd[33]> _handleLinkEvent: Got an error trying to query WiFi for power. Resetting state variables.

Thu Feb 5 22:51:30.086 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Thu Feb 5 23:10:48.711 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Fri Feb 6 00:26:02.229 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Fri Feb 6 02:14:47.320 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Fri Feb 6 02:52:00.625 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Fri Feb 6 08:16:57.371 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Fri Feb 6 08:34:32.516 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Fri Feb 6 08:34:52.745 <airportd[33]> _handleLinkEvent: WiFi is not powered. Resetting state variables.

Fri Feb 6 09:44:56.572 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Fri Feb 6 10:47:35.400 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Fri Feb 6 10:47:37.596 <airportd[33]> _handleLinkEvent: WiFi is not powered. Resetting state variables.

Fri Feb 6 11:04:31.878 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Fri Feb 6 11:04:34.082 <airportd[33]> _handleLinkEvent: WiFi is not powered. Resetting state variables.

Fri Feb 6 11:20:33.247 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Fri Feb 6 11:20:35.888 <airportd[33]> _handleLinkEvent: WiFi is not powered. Resetting state variables.

Fri Feb 6 11:34:15.691 <airportd[33]> -[CWXPCConnection performScanWithChannels:ssidList:legacyScanSSID:includeHiddenNetworks:mergeScan Results:maxAge:maxMissCount:maxWakeCount:maxAutoJoinCount:interfaceName:waitForW iFi:waitForBluetooth:token:priority:reply:]: !!! SCAN request received 0.0476 seconds after previous scan request from 4092 (Wireless Diagnostics)

Fri Feb 6 11:34:15.704 <airportd[33]> -[CWXPCConnection performScanWithChannels:ssidList:legacyScanSSID:includeHiddenNetworks:mergeScan Results:maxAge:maxMissCount:maxWakeCount:maxAutoJoinCount:interfaceName:waitForW iFi:waitForBluetooth:token:priority:reply:]: !!! SCAN request received 0.0125 seconds after previous scan request from 4092 (Wireless Diagnostics)

Fri Feb 6 11:35:05.169 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Fri Feb 6 11:35:07.587 <airportd[33]> _handleLinkEvent: WiFi is not powered. Resetting state variables.

Fri Feb 6 11:44:45.680 <airportd[33]> _handleLinkEvent: Got an error trying to query WiFi for power. Resetting state variables.

Fri Feb 6 12:06:26.939 <airportd[33]> _handleLinkEvent: Got an error trying to query WiFi for power. Resetting state variables.

Fri Feb 6 12:07:55.624 <airportd[33]> -[CWXPCConnection performScanWithChannels:ssidList:legacyScanSSID:includeHiddenNetworks:mergeScan Results:maxAge:maxMissCount:maxWakeCount:maxAutoJoinCount:interfaceName:waitForW iFi:waitForBluetooth:token:priority:reply:]: !!! SCAN request received 0.0102 seconds after previous scan request from 4304 (Wireless Diagnostics)

Fri Feb 6 12:12:33.165 <kernel> wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.

Fri Feb 6 12:12:35.678 <airportd[33]> _handleLinkEvent: WiFi is not powered. Resetting state variables.

I think that's a very different topic than what we've been talking about here. I'm no wifi expert, but if it's working in one place and not another, I'd be inclined to try to understand what's different about the two wifi networks.

It might make more sense to open a new discussion topic, for broader visibility.

Good luck!

OK, color me as "cautiously optimistic"... with AWDL disabled since February 1st, I've had no wi-fi issues with my Mac Pro. I hope that's the start of good news.