Skip to main content
Question

802.1X wifi will not connect after JAMF install and after JAMF removal.

  • April 1, 2016
  • 2 replies
  • 19 views
A
Forum|alt.badge.img+2

We have one Mac that fails to connect to a 802.1X network in a particular facility. This network is managed (via profile) via JAMF. We've re-installed profiles, stripped underlying configs, literally everything -- and yet this machine will not connect to the network in question. We went so far as to remove JAMF completely from the machine and manually configure the network -- but the network still refuses to connect. By not connect, I mean does not even peer with the network (from /var/log/wifi.log):

AutoJoin: <airportd[65]> __matchProfile: [wifi.ssid.foo] SSID 'FOO' (<foo>{length = 27, capacity = 27, bytes = 0xfoo}) does not match network SSID 'FOO' (<foo>{length = 27, capacity = 27, bytes = 0xfoo})

(I've stripped out all potential identifying information)

The device will peer with other networks, even 802.1X networks. The user certificate is valid and will peer on another Mac if tested. It will peer to the same AP in the building as well (and we have tried peering to other APs)

The Mac connected correctly before the JAMF framework as applied, and now we see this error. Either a) this Mac has something very wrong with it or b) there is something that got hosed when we installed the framework and now it has left traces behind.

Thoughts?

    2 replies

    bentoms
    Forum|alt.badge.img+35
    • bentoms
    • Hall of Fame
    • April 3, 2016

    @astanley in the system.log, any messages from eapoclient?

    A
    Forum|alt.badge.img+2
    • astanley
    • Author
    • New Contributor
    • April 5, 2016

    @bentoms Yup, here they are. FWIW, I stripped out a bunch of corecaptured entires to make this readable, but I left the kernel messages in.

    Mar 29 03:08:49 Client-Foo kernel[0]: en0: channel changed to 1
Mar 29 03:08:49 Client-Foo eapolclient[17140]: en0 START uid 501 gid 20
Mar 29 03:08:49 Client-Foo kernel[0]: en0: channel changed to 1
Mar 29 03:08:49 Client-Foo eapolclient[17140]: en0: 802.1X User Mode
Mar 29 03:08:49 Client-Foo kernel[0]: ARPT: 11190.904123: wlc_dump_aggfifo:
Mar 29 03:08:49 Client-Foo kernel[0]: ARPT: 11190.904148: framerdy 0x0 bmccmd 3 framecnt 1024 
Mar 29 03:08:49 Client-Foo kernel[0]: ARPT: 11190.904202: AQM agg params 0xfc0 maxlen hi/lo 0x0 0xffff minlen 0x0 adjlen 0x0
Mar 29 03:08:49 Client-Foo kernel[0]: ARPT: 11190.904248: AQM agg results 0x8001 len hi/lo: 0x0 0x26 BAbitmap(0-3) 0 0 0 0
Mar 29 03:08:49 Client-Foo kernel[0]: en0: channel changed to 1
Mar 29 03:08:49 Client-Foo kernel[0]: ARPT: 11190.975598: wlc_dump_aggfifo:
Mar 29 03:08:49 Client-Foo kernel[0]: ARPT: 11190.975631: framerdy 0x0 bmccmd 3 framecnt 1024 
Mar 29 03:08:49 Client-Foo kernel[0]: ARPT: 11190.975683: AQM agg params 0xfc0 maxlen hi/lo 0x0 0xffff minlen 0x0 adjlen 0x0
Mar 29 03:08:49 Client-Foo kernel[0]: ARPT: 11190.975726: AQM agg results 0x8001 len hi/lo: 0x0 0x26 BAbitmap(0-3) 0 0 0 0
Mar 29 03:08:52 Client-Foo kernel[0]: Unexpected payload found for message 9, dataLen 0
Mar 29 03:08:52 Client-Foo eapolclient[17140]: en0 STOP
    Terms & ConditionsCookie settingsAccessibility statement