Skip to main content

Hi All,

We have a bunch of unmanaged Macs on one of our sites that we are looking to manage soon, but at the moment we are having constant issues with connectivity dropping off and being very inconsistent.

We have narrowed it down to the following packet issue:
The issue is related to this message:

Line 5844: Dot1x_NW_MsgTask_6: Aug 04 09:39:32.306: b8:e8:56:43:af:9e Received EAPOL LOGOFF from mobile b8:e8:56:43:af:9e - processing Line 17012: Dot1x_NW_MsgTask_6: Aug 04 11:01:42.212: b8:e8:56:43:af:9e Received EAPOL LOGOFF from mobile b8:e8:56:43:af:9e - processing Line 19776: *Dot1x_NW_MsgTask_6: Aug 04 11:18:58.610: b8:e8:56:43:af:9e Received EAPOL LOGOFF from mobile b8:e8:56:43:af:9e – processing

Once the WLC receive this message it’s directly de-authenticate the client as per the client request.

Dot1x_NW_MsgTask_6: Aug 04 09:39:32.306: b8:e8:56:43:af:9e apfMsDeleteByMscb Scheduling mobile for deletion with deleteReason 1, reasonCode 1
Dot1x_NW_MsgTask_6: Aug 04 09:39:32.306: b8:e8:56:43:af:9e Scheduling deletion of Mobile Station: (callerId: 30) in 1 seconds

We have client load balancing disabled by default, this supposedly fixes it as per other sources but we are having these issues still.

Does anyone have experience with EAPOL-LOGOFF issues or can offer any help?

Do the clients have Junos Pulse installed per chance?
Also, does deleting these files (then rebooting) temporarily improve things? :

cd /Library/Preferences/SystemConfiguration
rm -rf com.apple.airport.preferences.plist
rm -rf com.apple.network.identification.plist
rm -rf com.apple.wifi.message-tracer.plist

rm -rf NetworkInterfaces.plist

rm -rf preferences.plist

By chance are any of those machines running Yosemite pre-10.10.4? If so I wonder if it is the discoveryd process having issues.

hey benshawk, i'm curious why you asked about Pulse. We use that, and have had some wifi issues with 10.10, but nothing ever was traced back to Pulse . . . .

Thanks benshawk i'll get those guys to run those commands and see what the outcome is, they definitely won't be on Junos Pulse either.

They're most likely running the latest since they're standalone users managing their own Mac but i'll check that..thanks

Still having these issues and none of the above have worked.

Noticing these logs from Wireless Diagnostics tool:

08/10/15 14:16:30.0040 NETWORK / ch64 [RSSI=-45 dBm, Noise=-89 dBm, SNR=44, Tx=878 Mbps]
08/10/15 14:16:30.0040 AWDL: Disabled [6 6 ]
08/10/15 14:16:30.0040 UNEXPECTED DROP DETECTED!!!

--- Monitor Test Cases

08/10/15 14:16:32.1830 Wi-Fi On . . . YES
08/10/15 14:16:32.1830 Wi-Fi Associated . . . YES
08/10/15 14:16:32.2530 QOS (BK_SYS) ping address xxx . . . pass —— [1/1 (0% loss) min=7.5 max=7.5 avg=7.5]
08/10/15 14:16:32.3230 QOS (BK) ping address xxx . . . pass —— [1/1 (0% loss) min=8.1 max=8.1 avg=8.1]
08/10/15 14:16:32.3930 QOS (BE) ping address xxx . . . pass —— [1/1 (0% loss) min=11.3 max=11.3 avg=11.3]
08/10/15 14:16:32.4620 QOS (RD) ping address xxx. . . pass —— [1/1 (0% loss) min=7.4 max=7.4 avg=7.4]
08/10/15 14:16:32.5320 QOS (OAM) ping address xxx . . . pass —— [1/1 (0% loss) min=7.6 max=7.6 avg=7.6]
08/10/15 14:16:32.6020 QOS (AV) ping address xxx . . . pass —— [1/1 (0% loss) min=11.8 max=11.8 avg=11.8]
08/10/15 14:16:32.6710 QOS (RV) ping address xxx . . . pass —— [1/1 (0% loss) min=7.9 max=7.9 avg=7.9]
08/10/15 14:16:32.7400 QOS (VI) ping address xxx . . . pass —— [1/1 (0% loss) min=7.3 max=7.3 avg=7.3]
08/10/15 14:16:32.8090 QOS (VO) ping address xxx . . . pass —— [1/1 (0% loss) min=9.4 max=9.4 avg=9.4]
08/10/15 14:16:32.8790 QOS (CTL) ping address xxx . . . pass —— [1/1 (0% loss) min=7.5 max=7.5 avg=7.5]
08/10/15 14:16:35.9230 LAN: WiFi interface can ping IPv4 router xxx . . . YES —— [4/4 (0% loss) min=7.5 max=8.7 avg=8.1]
08/10/15 14:16:41.0060 WAN: WiFi interface can ping DNS server xxx . . . YES -- [2/4 (0% loss) min=157.9 max=160.8 avg=159.4]
08/10/15 14:16:43.7230 Crowded Wi-Fi channel detected with on channel 64

--- Monitor Summary

08/10/15 14:16:43.7240 Crowded Wi-Fi Channel
08/10/15 14:16:43.7240 LAN Connectivity Failure

Terms & ConditionsCookie settingsAccessibility statement