VPN3k Radius authentication Error

I dont know what i am doing wrong, but everytime i try to setup a VPN3k for radius authentication get the following error:
An error has occurred while attempting to perform the operation.
Authentication Error: No active server found
The server is correctly configured on the vpn3k and also i setup the vpn3k as a client to ACS. The radius server works fine with any other routers.
Can anybody please share some tips.
Thanks

I can suggest several things to check about this issue. Are you sure that you have correct IP connectivity between the devices? (check this by pinging from the vpn3k to the server and ping from the server to the vpn3k) Are you sure that you have configured the correct key for cummunication from the vpn3k to the server? Does the server see any connection attempt from the vpn3k? (check logs and failed attempt reports on the server) Is there any access list on any router along the path from the vpn3k to the server which might be denying the request or the response?
HTH
Rick

Similar Messages

  • RADIUS Authentication Error Across the Subnet

    Hi Guyz
    I have configured Microsoft Server 2012 R2 as a RADIUS for Cisco IOS Devices
    Server IP Address :  10.95.6.12
    Router IP Address Fa 0/0.192                    ---->>>    192.193.194.195
    Router IP Address Fa 0/0.6                          --->>>    10.95.6.1
    Switch IP Address VLAN 192                     ---->>>    192.193.194.2010.95.6.11
    Switch IP Address VLAN 6                          ---->>>    10.95.6.11
    When i access the Cisco Devices RADIUS CLIENT with 10.95.6.x Subnet, It works fine 
    When i access the Cisco Devices through RADIUS CLIENT 192.193.194.x Subnet, It does not pass through the RADIUS Authentication.
    Attached in the Picture i can not access the 192.193.194.20 Device but I can access 10.95.6.1 Device.  As soon as I change the IP Address 10.95.6.11 I can access the Device.
    Ping is successful across the  Routers / Switches and Server as well.  Below is unsuccessful debug details as well:
    ===
    Home_Switch#
    01:52:30: RADIUS/ENCODE(00000008): ask "Password: "
    Home_Switch#
    01:52:41: RADIUS/ENCODE(00000008):Orig. component type = EXEC
    01:52:41: RADIUS:  AAA Unsupported Attr: interface         [171] 4   
    01:52:41: RADIUS:   74 74                [ tt]
    01:52:41: RADIUS/ENCODE(00000008): dropping service type, "radius-server attribute 6 on-for-login-auth" is off
    01:52:41: RADIUS(00000008): Config NAS IP: 0.0.0.0
    01:52:41: RADIUS/ENCODE(00000008): acct_session_id: 8
    01:52:41: RADIUS(00000008): sending
    01:52:41: RADIUS/ENCODE: Best Local IP-Address 10.95.6.11 for Radius-Server 10.95.6.12
    01:52:41: RADIUS(00000008): Send Access-Request to 10.95.6.12:1812 id 1645/6, len 85
    Home_Switch#
    01:52:41: RADIUS:  authenticator 95 FB 3F FE 79 BB AA D6 - C9 26 F4 EC 95 32 80 06
    01:52:41: RADIUS:  User-Name           [1]   7   "cisco"
    01:52:41: RADIUS:  User-Password       [2]   18  *
    01:52:41: RADIUS:  NAS-Port            [5]   6   2                         
    01:52:41: RADIUS:  NAS-Port-Id         [87]  6   "tty2"
    01:52:41: RADIUS:  NAS-Port-Type       [61]  6   Virtual                   [5]
    01:52:41: RADIUS:  Calling-Station-Id  [31]  16  "192.193.194.50"
    01:52:41: RADIUS:  NAS-IP-Address      [4]   6   10.95.6.11                
    01:52:41: RADIUS(00000008): Started 5 sec timeout
    Home_Switch#
    01:52:46: RADIUS(00000008): Request timed out 
    01:52:46: RADIUS: Retransmit to (10.95.6.12:1812,1813) for id 1645/6
    01:52:46: RADIUS(00000008): Started 5 sec timeout
    Home_Switch#
    ===
    Any help will really appreciate. 

    Duplicate posts.  
    Go here:  http://supportforums.cisco.com/discussion/12154866/radius-authentication-error-across-subnet

  • Radius authentication error.

    I have radius configured to authentication a cisco switch. The ACS is V5.3.  The login worked fine, but the enable doesn’t work. It came back saying “
    22056 Subject not found in the   applicable identity store(s).
    Any idea?
    Thanks,
    Han

    Hi Han,
    A first hint would be to check if the authentication protocol you are using (PAP, CHAP, MS-CHAPv1/2, etc.) is compatible with the database configured on ACS:
    http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_server_for_windows/4.2.1/User_Guide/Overvw.html#wpxref846
    This table is from the ACS 4.2.1 configuration guide, but it is generally true for all types of databases and ACS versions.
    Regards,
    Fede
    If  this helps you and/or answers your question please mark the question as  "answered" and/or rate it, so other users can easily find it.

  • Authentication via RADIUS : MSCHAPv2 Error 691

    Hello All,
    I am working on setting up authentication into an Acme Packet Net-Net 3820 (SBC) via RADIUS. The accounting side of things is working just fine with no issues. The authentication side of things is another matter. I can see from a packet capture that the access-request
    messages are in fact getting to the RADIUS server at which point the RADIUS server starts communicating with the domain controllers. I then see the chain of communication going back to the RADIUS and then finally back to the SBC. The problem is the response
    I get back is always an access-reject message with a reason code of 16 (Authentication failed due to a user credentials mismatch. Either the user name provided does not match an existing user account or the password was incorrect). This is confirmed by looking
    at the security event logs where I can see events 4625 and 6273. See the events below (Note: The names and IPs have been changed to protect the innocent):
    Event ID: 6273
    Network Policy Server denied access to a user.
    Contact the Network Policy Server administrator for more information.
    User:
    Security ID:
    NULL SID
    Account Name:
    real_username
    Account Domain:
    real_domain
    Fully Qualified Account Name:
    real_domain\real_username
    Client Machine:
    Security ID:
    NULL SID
    Account Name:
    Fully Qualified Account Name:
    OS-Version:
    Called Station Identifier:
    Calling Station Identifier:
    NAS:
    NAS IPv4 Address:
    10.0.0.10
    NAS IPv6 Address:
    NAS Identifier:
    radius1.real_domain
    NAS Port-Type:
    NAS Port:
    101451540
    RADIUS Client:
    Client Friendly Name:
    sbc1mgmt
    Client IP Address:
    10.0.0.10
    Authentication Details:
    Connection Request Policy Name:
    SBC Authentication
    Network Policy Name:
    Authentication Provider:
    Windows
    Authentication Server:
    RADIUS1.real_domain
    Authentication Type:
    MS-CHAPv2
    EAP Type:
    Account Session Identifier:
    Logging Results:
    Accounting information was written to the SQL data store and the local log file.
    Reason Code:
    16
    Reason:
    Authentication failed due to a user credentials mismatch. Either the user name provided does not map to an existing user account or the password was incorrect.
    Event ID: 4625
    An account failed to log on.
    Subject:
    Security ID:
    SYSTEM
    Account Name:
    RADIUS1$
    Account Domain:
    REAL_DOMAIN
    Logon ID:
    0x3E7
    Logon Type: 3
    Account For Which Logon Failed:
    Security ID:
    NULL SID
    Account Name:
    real_username
    Account Domain:
    REAL_DOMAIN
    Failure Information:
    Failure Reason:
    Unknown user name or bad password.
    Status:
    0xC000006D
    Sub Status:
    0xC000006A
    Process Information:
    Caller Process ID:
    0x2cc
    Caller Process Name:
    C:\Windows\System32\svchost.exe
    Network Information:
    Workstation Name:
    Source Network Address:
    Source Port:
    Detailed Authentication Information:
    Logon Process:
    IAS
    Authentication Package:
    MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
    Transited Services:
    Package Name (NTLM only):
    Key Length:
    0
    This event is generated when a logon request fails. It is generated on the computer where access was attempted.
    The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
    The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
    The Process Information fields indicate which account and process on the system requested the logon.
    The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
    The authentication information fields provide detailed information about this specific logon request.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
    So at first glance it would seem that the issue is merely a case of an invalid username or mismatched password. This is further confirmed in the packet capture where I can see the MSCHAPv2 response has an error code of 691 (Access denied because username or
    password, or both, are not valid on the domain). The thing is I know I am using a valid username and I have tried many usernames including new ones I created just for troubleshooting. I don't know how many times I have reset the password in an attempt to ensure
    it is not a mismatch password. I have even made sure to use passwords that are fairly short and contain only letters to ensure there was no terminal encoding issues (we connect to the SBC via SSH clients). I have also done this same thing with the shared secret
    used during communication between the SBC and the RADIUS server. I have tried prefixing the username with the domain name at login (though I don't think that should be necessary). I have also tried using the full UPN of the user to login. I have tried several
    RADIUS testing clients (NTRadPing, RadiusTest, etc.), but they either don't support MSCHAPv2 or only support EAP-MSCHAPv2. I have even created my own client using PHP's PECL RADIUS module. Still it always seems to fail with the MSCHAPv2 authentication with
    an error code of 691. Does anyone have any ideas as to why I always get an invalid username or bad password response when I have done everything possible to ensure that is not the case?
    Here are the specs for our RADIUS configuration:
    Windows Server 2012 R2
    SQL Server 2012 Back End Database for accounting.
    The server has been authorized on the domain and is a member of the "RAS and IAS Servers" group. For which that group does have access to the accounts we are testing with.
    The accounts we are testing with do have the "Control access through NPS Network Policy" option checked under their "Dial-in" property tab.
    RADIUS clients configured to simply match on the IP address which you can see from the events above that it is applying the client friendly name.
    Connection Request Policy: The "SBC Authenication" policy is being applied as seen above. The only condition is a regex expression that does successfully match the friendly name.
    Network Policy: As seen in events above, none are getting applied. For troubleshooting purposes I have created a Network Policy that is set to "1" for the processing order and its only condition is a Day and Time Restriction currently set to any
    time, any day.
    The authentication method is set to only MSCHAPv2 or MSCHAPv2 (User can change password after it has expired). I have tried adding this to just the Network Policy and I have also tried adding this to the Connection Request Policy and setting it to override
    the authentication method of the Network Policy.
    We do have other RADIUS servers in our domain that use PEAP to authenticate wireless clients and they all work fine. However, we need this to work with MSCHAPv2 only (No EAP).
    All other configurations are set to the defaults.
    The only other things of note to consider is the fact that in the events above you can see that the Security ID is "NULL SID". Now I know this is common especially among failed logons but given that this issue is stating an invalid username or
    bad password, perhaps it matters in this case. Also, this server has been rebuilt using the same computer account in Active Directory. I do not know if it would have worked before the rebuild. Essentially we built this server and only got as far as authorizing
    the server to the domain and adding SQL when we decided to separate out the SQL role onto another server. Rather than uninstalling SQL we just rebuilt the machine. However, before reinstalling Windows I did do a reset on the computer account. I don't think
    this should matter but thought I would point it out if there is some weird quirk where reusing the same SID of a previously authorized NPS server would cause an issue.
    All in all it is a fairly basic setup and hopefully I have provided enough information for someone to get an idea of what might be going on. I hope this was the right forum to post this too, I figured there would be a higher number of RADIUS experts here than
    any of the other categories. Apologies if my understanding of this seems a bit basic, after all, when it comes to RADIUS servers I guess you could say I'm the new guy here.

    Update 1:
    In an attempt to further troubleshoot this issue I have tried bringing up additional servers for testing. Here are the additional tests I have performed.
    Multiple Domains
    I have now tried this in 3 different isolated domains. Both our test and production domains as well as my private home domain which has very little in the way of customizations aside from the modifications made for Exchange and ConfigMgr. All have the same
    results described above.
    VPN Service
    Using Windows Server 2012 R2 we brought up a separate server to run a standard VPN setup. The intent was to see if we could use RADIUS authentication with the VPN and if that worked we would know the issue is with the SBCs. However, before we could even
    configure it to use RADIUS we just attempted to make sure it worked with standard Windows Authentication on the local VPN server. Interestingly, it too fails with the same events getting logged as the RADIUS servers. The client machine being a Windows 8.1
    workstation. Again I point out that we have working RADIUS servers used specifically for our wireless environment. The only difference between those RADIUS servers and the ones I am having problems with is that the working wireless servers are using PEAP instead
    of MSCHAPv2.
    FreeRADIUS
    Now I'm no Linux guru but I believe I have it up and running. I am able to use ntlm_auth to authenticate users when logged on to the console. However, when the radiusd service tries to use ntlm_auth to do essentially the same thing it fails and returns the
    same message I've been getting with the Windows server (E=691). I have the radiusd service running in debug mode so I can see more of what is going on. I can post the debug info I am getting if requested. The lines I am seeing of particular interest however
    are as follows:
    (1) ERROR: mschap : Program returned code (1) and output 'Logon failure (0xc000006d)'
    (1) mschap : External script failed.
    (1) ERROR: mschap : External script says: Logon Failure (0xc000006d)
    (1) ERROR: mschap : MS-CHAP2-Response is incorrect
    The thing to note here is that while we are essentially still getting a "wrong password" message, the actual status code (0xc000006d) is slightly different than what I was getting on the Windows Servers which was (0xc000006a). From this document
    you can see what these codes mean:
    NTSTATUS values . The good thing about this FreeRADIUS server is that I can see all of the challenge responses when it is in debug mode. So if I can wrap my head around how a MSCHAPv2 response is computed I can compare it to see if this is simply a miscomputed
    challenge response. Update: Was just noticing that the 6a code is just the sub-status code for the 6d code. So nothing different from the Windows Servers, I still wonder if there is a computation error with the challenge responses though.
    Currently, I am working on bringing up a Windows Server 2008 R2 instance of a RADIUS server to see if that helps at all. However, I would be surprised if something with the service broke between W2K8 R2 and W2K12 R2 without anyone noticing until now. If this
    doesn't work I may have to open a case with Microsoft. Update: Same results with W2K8 R2.

  • MacBook Pro will not connect to RADIUS authenticated SSID

    We are having problems with MacBook Pros and a MacBook Air not connecting to our wireless network. We have successfully connected hundreds of iPads and multiple other machines. All of the non-working machines are running OS X 10.9.5. The MacBook Air is brand new.
    We have a centrally managed wireless system made by Avaya. The SSID they are trying to connect to is protected by a password and RADIUS authentication. The SSID is called KT_MAC.
    A typical scenario looks like this:
    I add the device's MAC address to the RADIUS server (add it to the MAC OU in AD and add it to the MACAuth group)
    I attempt to connect to the KT_MAC SSID
    I am prompted for the password, which I type in
    Sometimes it connects on the first try, but usually it doesn't.  It will say something along the lines of Unable to join KT_MAC network or something.
    I then attempt to connect to the KT_MAC SSID again
    I am prompted for the password again, which I type in again
    It generally connects on this second attempt but not always.
    We have tried resetting the PRAM as well as deleting the saved profiles from each machine. Any guidance you can provide would be appreciated. Thank you.
    Here is the wifi.log from one of the affected MacBook Pros:
    Wed Apr 16 06:45:25.344 ***Starting Up***
    Wed Apr 16 06:45:38.389 <airportd[79]> airportdProcessDLILEvent: en1 attached (down)
    Wed Apr 16 06:45:39.056 <airportd[79]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Wed Apr 16 10:40:37.435 ***Starting Up***
    Wed Apr 16 10:40:53.769 <airportd[79]> airportdProcessDLILEvent: en1 attached (down)
    Wed Apr 16 10:40:53.786 <airportd[79]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Wed Apr 16 10:44:46.113 ***Starting Up***
    Wed Apr 16 10:44:46.130 <airportd[61]> airportdProcessDLILEvent: en1 attached (up)
    Thu Apr 17 09:20:53.884 ***Starting Up***
    Thu Apr 17 09:21:09.766 <airportd[79]> airportdProcessDLILEvent: en1 attached (down)
    Thu Apr 17 09:21:09.794 <airportd[79]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Thu Apr 17 09:25:11.200 ***Starting Up***
    Thu Apr 17 09:25:11.223 <airportd[62]> airportdProcessDLILEvent: en1 attached (up)
    Fri Jun  6 09:31:42.478 ***Starting Up***
    Fri Jun  6 09:31:58.966 <airportd[80]> airportdProcessDLILEvent: en1 attached (down)
    Fri Jun  6 09:31:59.026 <airportd[80]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Fri Jun  6 09:36:06.250 ***Starting Up***
    Fri Jun  6 09:36:06.270 <airportd[62]> airportdProcessDLILEvent: en1 attached (up)
    Fri Jun  6 09:45:40.827 ***Starting Up***
    Fri Jun  6 09:45:41.100 <airportd[64]> airportdProcessDLILEvent: en1 attached (up)
    Thu Aug  7 14:07:36.331 ***Starting Up***
    Thu Aug  7 14:07:51.354 <airportd[79]> airportdProcessDLILEvent: en1 attached (down)
    Thu Aug  7 14:07:51.362 <airportd[79]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Thu Aug  7 14:09:52.852 ***Starting Up***
    Thu Aug  7 14:09:52.863 <airportd[65]> airportdProcessDLILEvent: en1 attached (up)
    Thu Aug  7 14:18:27.352 ***Starting Up***
    Thu Aug  7 14:18:27.478 <airportd[64]> airportdProcessDLILEvent: en1 attached (up)
    Wed Aug 13 10:08:40.677 ***Starting Up***
    Wed Aug 13 10:08:54.747 <airportd[79]> airportdProcessDLILEvent: en1 attached (down)
    Wed Aug 13 10:08:54.775 <airportd[79]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Wed Aug 13 10:11:16.001 ***Starting Up***
    Wed Aug 13 10:11:16.019 <airportd[65]> airportdProcessDLILEvent: en1 attached (up)
    Wed Aug 13 10:36:42.311 <airportd[65]> _processSystemPSKAssoc: No password for network <CWNetwork: 0x7fb319c0c600> [ssid=KT_MAC, bssid=cc:f9:54:9c:0c:95, security=WPA/WPA2 Personal, rssi=-48, channel=<CWChannel: 0x7fb319c0be20> [channelNumber=11(2GHz), channelWidth={20MHz}], ibss=0] in the system keychain
    Wed Aug 13 10:37:06.172 <airportd[65]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 10:37:06.319 <airportd[65]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 10:42:28.162 <airportd[65]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 10:42:28.927 <airportd[65]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 10:46:15.069 <airportd[65]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 10:55:15.558 <airportd[65]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 10:55:48.574 ***Starting Up***
    Wed Aug 13 10:55:48.607 <airportd[65]> airportdProcessDLILEvent: en1 attached (up)
    Wed Aug 13 10:57:06.316 <airportd[65]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 11:01:36.170 <airportd[65]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 11:02:08.821 ***Starting Up***
    Wed Aug 13 11:02:08.860 <airportd[66]> airportdProcessDLILEvent: en1 attached (up)
    Wed Aug 13 11:03:30.508 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 11:51:20.003 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 11:51:21.436 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 11:51:28.110 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:19:51.335 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:19:51.881 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:20:42.635 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:24:03.774 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:24:04.289 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:24:13.201 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:28:39.658 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:28:40.139 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:29:19.235 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:30:30.152 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:30:30.639 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:30:39.280 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:41:45.386 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:41:45.870 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:42:01.343 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:45:19.733 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:45:20.322 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:46:21.947 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:46:46.015 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:46:46.938 <airportd[66]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:47:23.876 ***Starting Up***
    Wed Aug 13 14:47:23.980 <airportd[76]> airportdProcessDLILEvent: en1 attached (down)
    Wed Aug 13 14:47:30.166 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:47:49.006 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:50:45.857 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:50:46.733 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:50:53.301 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:53:50.650 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:53:51.139 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:53:55.950 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:54:04.344 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:54:04.890 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 14:54:10.672 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 15:29:37.354 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 15:29:37.949 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 13 15:29:43.381 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 14 07:45:08.606 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 14 07:45:09.095 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 14 07:45:15.685 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 14 07:52:36.817 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 14 07:52:37.317 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 14 07:52:43.699 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 14 10:35:31.857 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 14 10:35:32.343 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 14 10:35:37.513 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 14 15:14:58.070 <airportd[76]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Wed Aug 20 09:02:37.988 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 09:04:16.526 <airportd[76]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Wed Aug 20 13:38:15.045 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 13:42:00.449 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 13:42:00.947 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 13:42:06.664 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:19:00.054 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:19:00.467 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:19:05.892 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:19:12.064 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:19:12.709 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:19:17.467 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:19:26.654 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:19:27.140 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:19:32.104 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:19:38.083 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:19:38.597 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:19:44.561 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:20:58.990 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 20 14:20:59.540 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:48:48.223 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:51:31.070 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:51:31.627 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:51:44.224 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:55:39.838 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:55:40.309 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:55:48.012 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:56:10.669 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:56:11.170 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:56:16.734 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:56:38.283 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:56:38.782 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:56:43.755 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:57:27.425 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 07:57:27.862 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 11:00:35.541 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 11:07:15.263 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 11:07:20.996 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 11:07:35.210 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 11:08:08.856 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 11:08:09.394 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 11:09:40.498 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 14:00:57.796 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 14:00:58.388 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 14:01:09.718 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 14:02:10.320 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 14:02:10.841 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 14:02:16.251 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 21 15:19:57.730 <airportd[76]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Thu Aug 21 17:20:21.212 <airportd[76]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Tue Aug 26 09:40:29.421 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Aug 26 09:40:31.018 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Aug 26 09:40:39.112 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Aug 26 12:33:17.002 <airportd[76]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Wed Aug 27 11:19:57.907 <airportd[76]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Wed Aug 27 13:39:45.540 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 27 13:39:49.983 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 27 13:39:51.109 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 27 13:40:03.295 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 27 13:40:24.889 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 27 13:40:25.379 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 27 13:40:25.412 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 27 13:43:14.013 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 27 14:00:05.235 <airportd[76]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Wed Aug 27 14:39:41.454 <airportd[76]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Aug 27 14:40:24.778 ***Starting Up***
    Wed Aug 27 14:40:24.962 <airportd[74]> airportdProcessDLILEvent: en1 attached (up)
    Wed Aug 27 16:19:03.698 <airportd[74]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Thu Aug 28 08:46:43.526 <airportd[74]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 28 10:17:27.689 <airportd[74]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Thu Aug 28 11:28:30.790 <airportd[74]> _handleLinkEvent: Got an error trying to query WiFi for power. Resetting state variables.
    Thu Aug 28 11:29:13.259 <airportd[74]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 28 11:29:44.661 ***Starting Up***
    Thu Aug 28 11:29:45.001 <airportd[69]> airportdProcessDLILEvent: en1 attached (up)
    Thu Aug 28 11:30:36.331 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 28 11:46:38.432 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 28 11:46:39.745 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 28 11:46:47.701 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 28 11:57:42.197 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 28 11:57:42.769 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 28 11:58:11.783 <airportd[69]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Thu Aug 28 14:20:25.408 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 28 14:24:19.381 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 28 14:24:19.850 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Aug 28 14:24:31.421 <airportd[69]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Fri Aug 29 14:56:26.295 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:22:35.627 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:22:36.623 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:22:55.827 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:23:02.069 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:23:02.769 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:23:09.667 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:23:16.290 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:23:16.963 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:23:22.575 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:25:26.678 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:25:27.200 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:25:32.201 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:26:13.725 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:26:14.253 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:26:20.486 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:26:42.304 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:26:42.817 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:26:47.337 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:27:16.340 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:27:16.796 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:27:23.720 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:29:15.644 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:29:16.061 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Aug 29 15:29:18.938 <airportd[69]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Wed Sep  3 09:35:54.553 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep  3 09:35:55.902 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep  3 09:36:02.003 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep  3 10:16:04.232 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep  3 10:16:05.097 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep  3 10:16:11.571 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep  3 11:23:20.719 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep  3 11:23:41.332 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep  3 11:23:42.272 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep  3 11:24:19.455 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep  3 11:24:26.410 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep  3 11:24:56.452 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep  3 11:25:01.587 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep  3 11:25:01.710 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Sep  4 08:07:04.320 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Sep  4 08:07:05.150 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Sep  4 09:30:29.203 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Sep  4 15:37:43.025 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Sep  4 15:37:43.637 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Sep  4 15:39:31.062 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Sep  4 15:42:25.933 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Sep  4 15:42:26.467 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Sep  4 15:42:34.515 <airportd[69]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Fri Sep  5 07:50:25.167 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Sep  5 07:50:25.648 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Fri Sep  5 07:50:42.279 <airportd[69]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Fri Sep  5 11:54:40.981 <airportd[69]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Wed Sep 10 08:41:58.791 <airportd[69]> _handleLinkEvent: Got an error trying to query WiFi for power. Resetting state variables.
    Thu Sep 11 10:07:01.271 <airportd[69]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Wed Sep 17 15:36:49.049 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep 17 16:01:44.231 <airportd[69]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Thu Sep 18 08:56:41.771 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Sep 18 08:56:43.081 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Sep 18 08:56:43.186 <airportd[69]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Thu Sep 18 09:00:32.568 ***Starting Up***
    Thu Sep 18 09:00:33.214 <airportd[64]> airportdProcessDLILEvent: en1 attached (up)
    Mon Sep 22 09:22:24.363 <airportd[64]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Mon Sep 22 09:22:32.890 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Sep 23 14:41:33.196 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Sep 23 14:45:22.840 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Sep 23 14:45:23.438 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Sep 23 14:45:32.513 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep 24 14:30:58.274 <airportd[64]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Wed Sep 24 14:56:26.902 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep 24 14:57:33.995 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep 24 14:57:34.531 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep 24 14:57:34.646 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep 24 15:39:07.563 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep 24 15:40:16.183 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep 24 15:40:16.637 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Wed Sep 24 15:40:43.234 <airportd[64]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Fri Oct  3 07:41:49.370 <airportd[64]> _handleLinkEvent: WiFi is not powered. Resetting state variables.
    Tue Oct  7 07:54:00.397 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Oct  7 08:10:14.340 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Oct  7 08:10:15.306 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Oct  7 08:10:21.639 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Oct  7 09:04:53.718 <airportd[64]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Oct  7 09:05:55.913 ***Starting Up***
    Tue Oct  7 09:05:55.937 <airportd[63]> airportdProcessDLILEvent: en1 attached (down)
    Tue Oct  7 09:08:48.018 <kernel> IO80211ScanManager::startScanMultiple: Scan request received from 'airportd' (pid 63) (2 SSIDs, 0 BSSIDs).
    Tue Oct  7 09:08:48.018 <kernel> IO80211ScanManager::startScanMultiple: Initiating scan.
    Tue Oct  7 09:08:48.323 <airportd[63]> userOnConsole: user: physed
    Tue Oct  7 09:08:48.323 <airportd[63]> __startAutoJoinForInterface_block_invoke: AUTOJOIN: Already in progress for interface en1 in wake context 0.
    Tue Oct  7 09:08:48.437 <airportd[63]> userOnConsole: user: physed
    Tue Oct  7 09:08:48.437 <airportd[63]> __startAutoJoinForInterface_block_invoke: AUTOJOIN: Already in progress for interface en1 in wake context 0.
    Tue Oct  7 09:08:48.870 <kernel> IO80211ScanManager::startScan: Broadcast scan request received from 'locationd' (pid 41) ().
    Tue Oct  7 09:08:48.870 <kernel> IO80211ScanManager::getScanResult: All scan results returned for 'airportd' (pid 63).
    Tue Oct  7 09:08:48.871 <kernel> IO80211ScanManager::getScanResult: All scan results returned for 'locationd' (pid 41).
    Tue Oct  7 09:08:48.881 <airportd[63]> matchAndJoinNetworkListAgainstScanResults: matched with SSID “KT_MAC”
    Tue Oct  7 09:08:48.881 <airportd[63]> _doAssociate: network: “KT_MAC”, systemMode: 1, userOnConsole: 1
    Tue Oct  7 09:08:48.888 <airportd[63]> _doAssociate: Successfully pulled the password from the keychain. Now trying to associate.
    Tue Oct  7 09:08:48.920 <airportd[63]> _handleNewMessage: Received XPC message, event = ASSOC_EVENT, pid = 63
    Tue Oct  7 09:08:48.921 <airportd[63]> associate: INFO: airportd associate: network=<CWNetwork: 0x7fb243510a20> [ssid=KT_MAC, bssid=cc:f9:54:9c:0c:95, security=WPA/WPA2 Personal, rssi=-46, channel=<CWChannel: 0x7fb2435157d0> [channelNumber=1(2GHz), channelWidth={20MHz}], ibss=0], is8021X=0, remember=1
    Tue Oct  7 09:08:48.930 <airportd[63]> associate: INFO: Checking if admin authorization is required
    Tue Oct  7 09:08:48.936 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/CachedScanRecord' 'State:/Network/Interface/en1/AirPort/Power Status' }
    Tue Oct  7 09:08:48.936 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/CachedScanRecord'
    Tue Oct  7 09:08:48.936 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/Power Status'
    Tue Oct  7 09:08:48.936 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/Busy' }
    Tue Oct  7 09:08:48.936 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/Busy'
    Tue Oct  7 09:08:48.937 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/CHANNEL' 'State:/Network/Interface/en1/AirPort/AutoJoinTimestamp' }
    Tue Oct  7 09:08:48.937 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/CHANNEL'
    Tue Oct  7 09:08:48.937 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/AutoJoinTimestamp'
    Tue Oct  7 09:08:48.982 <kernel> parseRSNIE: groupCipherType = 3 pairwiseCipherType = 5 authSel = 2
    Tue Oct  7 09:08:48.982 <kernel> initWithInterfaceAndIE: _myMacAddress 2c:be:08:eb:fc:9e
    Tue Oct  7 09:08:48.982 <kernel> setPMK: PMK SET!
    Tue Oct  7 09:08:48.988 <airportd[63]> _p2pSupEventCallback: APPLE80211_M_LINK_CHANGED
    Tue Oct  7 09:08:48.988 <airportd[63]> _p2pSupEventCallback: Primary interface link marked up
    Tue Oct  7 09:08:48.988 <airportd[63]> _p2pSupEventCallback: New channel = 36 (flags=0x214)
    Tue Oct  7 09:08:48.988 <airportd[63]> _bsd_80211_event_callback: LINK_CHANGED (en1)
    Tue Oct  7 09:08:48.988 <airportd[63]> airportdProcessDriverEvent: link changed
    Tue Oct  7 09:08:48.993 <airportd[63]> _bsd_80211_event_callback: SSID_CHANGED (en1)
    Tue Oct  7 09:08:48.993 <airportd[63]> _bsd_80211_event_callback: BSSID_CHANGED (en1)
    Tue Oct  7 09:08:48.993 <airportd[63]> _p2pSupEventCallback: APPLE80211_M_BSSID_CHANGED
    Tue Oct  7 09:08:48.993 <airportd[63]> __AirPortOpportunisticRoamBSSIDChanged: <en1> BSSID Change Event old <CC:F9:54:9C:0C:85>, new <CC:F9:54:9C:0C:85>reset Opp Roam to <-2147483648>
    Tue Oct  7 09:08:48.993 <airportd[63]> _bsd_80211_event_callback: Frequency Band updated <2>
    Tue Oct  7 09:08:48.993 <airportd[63]> BluetoothCoexHandleUpdateForNode: <en1> Handle Bluetooth Coex: FrequencyBand <2>, Bluetooth Bandwidth Utilization <0>, Clamshell Mode <0>
    Tue Oct  7 09:08:48.993 <airportd[63]> BluetoothCoexModeSet: <en1> already set to BT Coex mode 'Off', do not perform APPLE80211_IOC_BTCOEX_MODE
    Tue Oct  7 09:08:48.993 <airportd[63]> BluetoothCoexSettingPerChainTransmitPowerOffsets: Per TX Chain Power Offset Control (
    Tue Oct  7 09:08:48.993     0,
    Tue Oct  7 09:08:48.993     0,
    Tue Oct  7 09:08:48.993     0
    Tue Oct  7 09:08:48.993 )
    Tue Oct  7 09:08:48.996 <kernel> en1: Received EAPOL packet (length = 113)
    Tue Oct  7 09:08:48.996 <kernel> inputEAPOLFrame: 0 extra bytes present in EAPOL frame.
    Tue Oct  7 09:08:48.996 <kernel> inputEAPOLFrame: Received message 1 of 4
    Tue Oct  7 09:08:48.996 <kernel> FULL RSN IE FOUND:
    Tue Oct  7 09:08:48.996 [00000000] 30 18 01 00 00 0F AC 02 02 00 00 0F AC 04 00 0F AC 02 01 00 00 0F AC 02 0C 00
    Tue Oct  7 09:08:48.996 <kernel> storeFullRSNIE: getAP_IE_LIST returned 0
    Tue Oct  7 09:08:48.996 <kernel> PMK:
    Tue Oct  7 09:08:48.996 [00000000] 61 35 71 AB 2C F6 AF 24 23 06 8D C5 1E 5F 75 88 0A B9 72 A4 5E 05 BA F2 54 A5 2E 64 0E 2F
    Tue Oct  7 09:08:48.996 [0000001E] F1 E3
    Tue Oct  7 09:08:48.996 <kernel> TPTK:
    Tue Oct  7 09:08:48.996 [00000000] 35 38 A9 BA 8C C2 A7 E2 8B FF 84 0B AC 62 21 01 E8 7C 00 CB 0C 64 36 C7 17 F7 BD 4A 20 1C
    Tue Oct  7 09:08:48.996 [0000001E] 59 9E 58 DC 8C 88 BF 46 31 43 7F 3D 63 07 BC E4 2D B8 B9 4D AA D7 D0 AB 2F CB 49 F0 CB F7
    Tue Oct  7 09:08:48.996 [0000003C] B5 D1 85 CC
    Tue Oct  7 09:08:48.996 <kernel> KEY MIC:
    Tue Oct  7 09:08:48.996 [00000000] 47 E1 FD 97 16 21 0F 8F BE 93 08 63 65 E7 83 50
    Tue Oct  7 09:08:48.996 <kernel> process1of4: sending replyPacket 135 bytes
    Tue Oct  7 09:08:48.996 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/Power Status' 'State:/Network/Interface/en1/AirPort/AutoJoinTimestamp' 'State:/Network/Interface/en1/AirPort/Busy' }
    Tue Oct  7 09:08:48.997 <kernel> en1: Received EAPOL packet (length = 217)
    Tue Oct  7 09:08:48.997 <kernel> inputEAPOLFrame: 0 extra bytes present in EAPOL frame.
    Tue Oct  7 09:08:48.997 <kernel> inputEAPOLFrame: decrypting key data
    Tue Oct  7 09:08:48.997 <kernel> inputEAPOLFrame: Received message 3 of 4
    Tue Oct  7 09:08:48.997 <kernel> process3of4: Performing IE check.
    Tue Oct  7 09:08:48.997 <kernel> process3of4: sending replyPacket ( len = 113 ).
    Tue Oct  7 09:08:48.997 <kernel> process3of4: received pairwise GTK
    Tue Oct  7 09:08:48.997 <kernel> ptkThread: Sleeping!
    Tue Oct  7 09:08:48.997 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/SSID' 'State:/Network/Interface/en1/AirPort/CachedScanRecord' 'State:/Network/Interface/en1/AirPort/SSID_STR' }
    Tue Oct  7 09:08:48.999 <kernel> ptkThread: Installing PTK!
    Tue Oct  7 09:08:48.999 <kernel> PTK:
    Tue Oct  7 09:08:48.999 [00000000] 58 DC 8C 88 BF 46 31 43 7F 3D 63 07 BC E4 2D B8
    Tue Oct  7 09:08:48.999 <kernel> ptkThread: Installing GTK!
    Tue Oct  7 09:08:48.999 <kernel> installGTK: setting cipher key (flags = 0x0)
    Tue Oct  7 09:08:49.000 <kernel> RSC:
    Tue Oct  7 09:08:49.000 [00000000] 22 0B 1F 01 00 00
    Tue Oct  7 09:08:49.000 <kernel> GTK:
    Tue Oct  7 09:08:49.000 [00000000] 12 64 92 29 99 8D 4C 8A D2 D5 CC E5 5B CB B7 09 96 6B 53 F9 88 F4 C7 B7 71 72 DD 88 F1 EB
    Tue Oct  7 09:08:49.000 [0000001E] 0C FC
    Tue Oct  7 09:08:49.000 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/CHANNEL' }
    Tue Oct  7 09:08:49.000 <airportd[63]> airportdProcessDriverEvent: SSID changed
    Tue Oct  7 09:08:49.000 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/BSSID' }
    Tue Oct  7 09:08:49.000 <airportd[63]> airportdProcessDriverEvent: BSSID changed
    Tue Oct  7 09:08:49.000 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/Power Status'
    Tue Oct  7 09:08:49.000 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/AutoJoinTimestamp'
    Tue Oct  7 09:08:49.000 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/Busy'
    Tue Oct  7 09:08:49.000 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/SSID'
    Tue Oct  7 09:08:49.000 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/CachedScanRecord'
    Tue Oct  7 09:08:49.000 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/SSID_STR'
    Tue Oct  7 09:08:49.001 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/CHANNEL'
    Tue Oct  7 09:08:49.001 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/BSSID'
    Tue Oct  7 09:08:49.028 <airportd[63]> _bsd_80211_event_callback: LINK_QUALITY (en1)
    Tue Oct  7 09:08:49.103 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/Power Status' 'State:/Network/Interface/en1/AirPort/UserMode8021X' }
    Tue Oct  7 09:08:49.103 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/Power Status'
    Tue Oct  7 09:08:49.104 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/UserMode8021X'
    Tue Oct  7 09:08:49.105 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/AutoJoinTimestamp' }
    Tue Oct  7 09:08:49.105 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/AutoJoinTimestamp'
    Tue Oct  7 09:08:49.109 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/Busy' 'State:/Network/Interface/en1/AirPort/SSID' 'State:/Network/Interface/en1/AirPort/CachedScanRecord' }
    Tue Oct  7 09:08:49.110 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/Busy'
    Tue Oct  7 09:08:49.110 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/SSID'
    Tue Oct  7 09:08:49.110 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/CachedScanRecord'
    Tue Oct  7 09:08:49.110 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/SSID_STR' 'State:/Network/Interface/en1/AirPort/CHANNEL' }
    Tue Oct  7 09:08:49.110 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/SSID_STR'
    Tue Oct  7 09:08:49.110 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/CHANNEL'
    Tue Oct  7 09:08:49.110 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/BSSID' }
    Tue Oct  7 09:08:49.111 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/BSSID'
    Tue Oct  7 09:08:49.112 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/WEPOpenSystem' }
    Tue Oct  7 09:08:49.112 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/WEPOpenSystem'
    Tue Oct  7 09:08:49.112 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/WEP40' }
    Tue Oct  7 09:08:49.113 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/WEP40'
    Tue Oct  7 09:08:49.383 <airportd[63]> userOnConsole: user: physed
    Tue Oct  7 09:08:49.383 <airportd[63]> __startAutoJoinForInterface_block_invoke: AUTOJOIN: Already in progress for interface en1 in wake context 0.
    Tue Oct  7 09:08:49.394 <kernel> IO80211ScanManager::startScan: Broadcast scan request received from 'airportd' (pid 63) ().
    Tue Oct  7 09:08:49.395 <kernel> IO80211ScanManager::getScanResult: All scan results returned for 'airportd' (pid 63).
    Tue Oct  7 09:08:49.512 <kernel> IO80211ScanManager::startScan: Broadcast scan request received from 'airportd' (pid 63) ().
    Tue Oct  7 09:08:49.513 <kernel> IO80211ScanManager::getScanResult: All scan results returned for 'airportd' (pid 63).
    Tue Oct  7 09:08:49.522 <airportd[63]> _doAssociate: assocError (0)
    Tue Oct  7 09:08:49.522 <airportd[63]> matchAndJoinNetworkListAgainstScanResults: successfully associated to “KT_MAC”
    Tue Oct  7 09:08:49.527 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/Power Status' 'State:/Network/Interface/en1/AirPort/UserMode8021X' }
    Tue Oct  7 09:08:49.527 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/Power Status'
    Tue Oct  7 09:08:49.527 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/UserMode8021X'
    Tue Oct  7 09:08:49.528 <kernel> IO80211ScanManager::startScan: Broadcast scan request received from 'SystemUIServer' (pid 167) ().
    Tue Oct  7 09:08:49.528 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/AutoJoinTimestamp' 'State:/Network/Interface/en1/AirPort/WEPOpenSystem' }
    Tue Oct  7 09:08:49.529 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/AutoJoinTimestamp'
    Tue Oct  7 09:08:49.530 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/WEPOpenSystem'
    Tue Oct  7 09:08:49.530 <kernel> IO80211ScanManager::getScanResult: All scan results returned for 'SystemUIServer' (pid 167).
    Tue Oct  7 09:08:49.530 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/WEP40' }
    Tue Oct  7 09:08:49.532 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/WEP40'
    Tue Oct  7 09:08:49.532 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/Busy' }
    Tue Oct  7 09:08:49.532 <airportd[63]> interfaceBusyStateChanged: Busy state for en1 changed to not busy. gSystemSleeping = 0, gMaintenanceWake = 0
    Tue Oct  7 09:08:49.532 <airportd[63]> _updateInterfaceBusySetting: Disabling P2P scan suppress
    Tue Oct  7 09:08:49.532 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/Busy'
    Tue Oct  7 09:08:49.534 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/SSID' 'State:/Network/Interface/en1/AirPort/CachedScanRecord' 'State:/Network/Interface/en1/AirPort/SSID_STR' 'State:/Network/Interface/en1/AirPort/CHANNEL' }
    Tue Oct  7 09:08:49.534 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/SSID'
    Tue Oct  7 09:08:49.534 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/CachedScanRecord'
    Tue Oct  7 09:08:49.534 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/SSID_STR'
    Tue Oct  7 09:08:49.534 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/CHANNEL'
    Tue Oct  7 09:08:49.534 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/BSSID' }
    Tue Oct  7 09:08:49.534 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/BSSID'
    Tue Oct  7 09:08:49.535 <airportd[63]> __startAutoJoinForInterface_block_invoke_2: exiting
    Tue Oct  7 09:08:52.043 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Service/7916B194-D6E3-4D97-947E-70FBB10ECCED/DHCP' }
    Tue Oct  7 09:08:52.043 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Service/7916B194-D6E3-4D97-947E-70FBB10ECCED/DHCP'
    Tue Oct  7 09:08:52.043 <airportd[63]> _processDHCPChanges: State:/Network/Service/7916B194-D6E3-4D97-947E-70FBB10ECCED/DHCP
    Tue Oct  7 09:08:52.043 <airportd[63]> _processDHCPChanges: DHCP airport_changed = 1
    Tue Oct  7 09:08:52.044 <airportd[63]> _setDHCPMessage: dhcpInfoKey "State:/Network/Interface/en1/AirPort/DHCP Message" = (null)
    Tue Oct  7 09:08:54.695 <kernel> IO80211ScanManager::startScanMultiple: Scan request received from 'SystemUIServer' (pid 167) (2 SSIDs, 0 BSSIDs).
    Tue Oct  7 09:08:54.695 <kernel> IO80211ScanManager::startScanMultiple: Initiating scan.
    Tue Oct  7 09:08:57.902 <kernel> IO80211ScanManager::getScanResult: All scan results returned for 'SystemUIServer' (pid 167).
    Tue Oct  7 09:08:57.902 <kernel> IO80211ScanManager::startScan: Broadcast scan request received from 'locationd' (pid 41) ().
    Tue Oct  7 09:08:57.903 <kernel> IO80211ScanManager::getScanResult: All scan results returned for 'locationd' (pid 41).
    Tue Oct  7 09:08:58.788 <airportd[63]> _SC_callback: Changed keys = { 'Setup:/Network/Interface/en1/AirPort' }
    Tue Oct  7 09:08:58.788 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'Setup:/Network/Interface/en1/AirPort'
    Tue Oct  7 09:08:58.798 <airportd[63]> userOnConsole: user: physed
    Tue Oct  7 09:08:58.798 <airportd[63]> __startAutoJoinForInterface_block_invoke_2: AUTOJOIN: Starting for interface en1 in wake context 0.
    Tue Oct  7 09:08:58.802 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/Power Status' 'State:/Network/Interface/en1/AirPort/UserMode8021X' 'State:/Network/Interface/en1/AirPort/BSSID' }
    Tue Oct  7 09:08:58.802 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/Power Status'
    Tue Oct  7 09:08:58.802 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/UserMode8021X'
    Tue Oct  7 09:08:58.802 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/BSSID'
    Tue Oct  7 09:08:58.803 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/AutoJoinTimestamp' }
    Tue Oct  7 09:08:58.803 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/AutoJoinTimestamp'
    Tue Oct  7 09:08:58.805 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/WEPOpenSystem' 'State:/Network/Interface/en1/AirPort/CHANNEL' 'State:/Network/Interface/en1/AirPort/WEP40' }
    Tue Oct  7 09:08:58.805 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/WEPOpenSystem'
    Tue Oct  7 09:08:58.805 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/CHANNEL'
    Tue Oct  7 09:08:58.805 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/WEP40'
    Tue Oct  7 09:08:58.808 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/Busy' }
    Tue Oct  7 09:08:58.808 <airportd[63]> interfaceBusyStateChanged: Busy state for en1 changed to busy. gSystemSleeping = 0, gMaintenanceWake = 0
    Tue Oct  7 09:08:58.808 <airportd[63]> _updateInterfaceBusySetting: Enabling P2P scan suppress
    Tue Oct  7 09:08:58.809 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/Busy'
    Tue Oct  7 09:08:58.809 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/SSID' 'State:/Network/Interface/en1/AirPort/CachedScanRecord' }
    Tue Oct  7 09:08:58.809 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/SSID'
    Tue Oct  7 09:08:58.809 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/CachedScanRecord'
    Tue Oct  7 09:08:58.809 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/SSID_STR' }
    Tue Oct  7 09:08:58.809 <airportd[63]> _doAutoJoin: Wi-Fi supports multiple-directed scans
    Tue Oct  7 09:08:58.809 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/SSID_STR'
    Tue Oct  7 09:08:58.809 <airportd[63]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Oct  7 09:08:58.812 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/Power Status' 'State:/Network/Interface/en1/AirPort/UserMode8021X' }
    Tue Oct  7 09:08:58.812 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/Power Status'
    Tue Oct  7 09:08:58.812 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/UserMode8021X'
    Tue Oct  7 09:08:58.812 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/BSSID' }
    Tue Oct  7 09:08:58.812 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/BSSID'
    Tue Oct  7 09:08:58.813 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/SSID_STR' }
    Tue Oct  7 09:08:58.813 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/SSID_STR'
    Tue Oct  7 09:08:58.814 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/AutoJoinTimestamp' }
    Tue Oct  7 09:08:58.814 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/AutoJoinTimestamp'
    Tue Oct  7 09:08:58.815 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/CachedScanRecord' }
    Tue Oct  7 09:08:58.815 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/CachedScanRecord'
    Tue Oct  7 09:08:58.816 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/WEPOpenSystem' }
    Tue Oct  7 09:08:58.816 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/WEPOpenSystem'
    Tue Oct  7 09:08:58.816 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/CHANNEL' }
    Tue Oct  7 09:08:58.816 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/CHANNEL'
    Tue Oct  7 09:08:58.817 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/WEP40' }
    Tue Oct  7 09:08:58.817 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/WEP40'
    Tue Oct  7 09:08:58.819 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/Busy' }
    Tue Oct  7 09:08:58.819 <airportd[63]> __startAutoJoinForInterface_block_invoke_2: exiting
    Tue Oct  7 09:08:58.819 <airportd[63]> interfaceBusyStateChanged: Busy state for en1 changed to not busy. gSystemSleeping = 0, gMaintenanceWake = 0
    Tue Oct  7 09:08:58.819 <airportd[63]> _updateInterfaceBusySetting: Disabling P2P scan suppress
    Tue Oct  7 09:08:58.819 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/Busy'
    Tue Oct  7 09:08:58.819 <airportd[63]> _SC_callback: Changed keys = { 'State:/Network/Interface/en1/AirPort/SSID' }
    Tue Oct  7 09:08:58.819 <airportd[63]> airportdProcessSystemConfigurationEvent: Processing 'State:/Network/Interface/en1/AirPort/SSID'
    Tue Oct  7 09:08:58.995 <airportd[63]> _handleNewMessage: Received XPC message, event = DEBUG_FLAGS_EVENT, pid = 274
    Tue Oct  7 09:08:59.037 <airportd[63]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.
    Tue Oct  7 09:08:59.147 <airportd[63]> _doAutoJoin: Already associated to “KT_MAC”. Bailing on auto-join.

    Eventually ended up on the phone with an Apple Engineer through Educational Support. They reported to us there are known issues with some RADIUS connections and didn't have any solutions beyond installing the new version of OS X 10.10 Yosemite
    We did install 10.10 on a spare machine and it did appear to solve the issue but was still in beta at the time.

  • ACS Express radius authentication AD authorization

    I work at a University and for some reason we have multiple systems for authentication and authorization.  That being said I am trying to use radius to do authentication and AD for authorization for VPNs.  I have the radius authentication working against our radius server.  I have my ACS express setup to join the AD domain and everything looks good there.  I setup the AD server as a radius object in AAA server groups on my ASA.  Then I add the server below in the servers in selected groups window.  I put all the info in there and when I hit test I click authorization and put in the username that I know is in the domain group I have associated with this on the ACS.  The test fails and with authorization failed with invalid password.  When I look at the logs on the ACS I see
    01/06/2011 20:14:26 acsxp/server Warning Server 0 AD Agent Plain Text Authentication Failed for user: username@domain
    01/06/2011 20:14:26 acsxp/server Warning Server 0 Authentication for user username failed for reason = 0
    01/06/2011 20:14:26 acsxp/server Error Protocol 0 Request from 172.20.5.2: User username rejected . by RemoteServer: AD (InvalidPassword). 
    Username and domain are correct I just edited them for posting.  It seems like it is trying to authenticate rather than authorize.  All I want it to do is say yes the user is in this group or no the user is not in this group?  You can't even fill in the password when testing authorization?  Maybe I have something setup wrong on the ACS side but when I look at AD under users and identity stores, it says it is joined to the domain.  When I do AD domain diagnostics under troubleshooting everything looks good.  I have the ASA I am testing from defined as a device and in the ASA device group.  Under access services in Radius access services I have one service that I setup that connects to the AD and it found the group so I know it is connecting.  Any idea what I am doing wrong or where to look?
    Any help would be GREATLY appreciated!
    Thanks
    Joe

    Hi Joe,
    We could take a deeper look at what is happening through some logs and debugs:
    1. On ACS Express, under
    Reports & Troubleshooting > Troubleshooting > Server Logs
    please set the Express Server Trace Level to 5 and the Web Server Trace Level to 4.
    Also, for the Log Level under OS Logging, please set its value to "Debug".
    If previous old logs are not essential to you, you may also wanna delete all the log files first, so that we capture logs for the last day only.
    2. On the ASA, please enable the following debugs
    debug aaa authentication
    debug aaa authorization
    debug radius
    3. Then please first recreate a successful authentication attempt, and then recreate the authorization test issue with the same user account for which you tested the successful authentication.
    4. After the issue is recreated, please attach the debugs from the ASA and following files from the ACS Server Logs:
    acsxp_adagent.log
    acsxp_agent_server.log
    acsxp_mcd.log
    acsxp_server.log
    acsxp_server_trace.log
    Regards,
    Fede
    If  this helps you and/or answers your question please mark the question as  "answered" and/or rate it, so other users can easily find it.

  • 802.1x RADIUS authentication problem with Cat 2950 to CiscoSecure ACS 3.3

    I wondered if anyone can help or shed any light on the following problem.
    I am getting an authentication error when doing a RADIUS authentication to CiscoSecure ACS 3.3 running on a Windows 2003 server, the authentication request is coming from a Catalyst 2950 switch which is doing 802.1x for Windows XP clients. This problem only happens when the XP client connects to 2950 switches, Cat 3550s and 3560s work fine.
    The Cat2950 is running 12.1.20 (EA1) which is more or less the latest IOS.
    The error I get from ACS 3.3 is "Invalid message authenticator in EAP request" when the 2950 tries to authenticate an XP client for 802.1x to the ACS server using RADIUS.
    Doing a RADIUS and 802.1x debug on the 2950 I see a message about 'Unknown EAP type', I am using PEAP on the XP client doing EAP-MS-CHAPv2 authentication, the same XP client authenticates fine with 3550 and 3560 switches problem only affects 2950s. Can anyone confirm the 2950 supports EAP-MS-CHAPv2?
    I have checked and re-checked the shared secret and it definitely matches on 2950 and ACS.
    One thing I noticed in the RADIUS debug is the 2950 sends 18 bytes for attribute 79 when the RFC defines attribute 79 should be 3 bytes or less, I don't know if this is related to the problem or is correct behaviour.

    Hi, I am new with 802.1x, and was hoping that someone would help with these queries:
    1. How is a certificate requested without being allowed on a network that is not authenticated with 802.1x. I had to first connect to an active network, retrieve a certificate with the proper username and password, and then physically connect to the port on the 2950 switch which was enabled to do 802.1x
    2. My config is as below:
    aaa new-model
    aaa authentication dot1x default group radius
    aaa authenication login default group radius
    dot1x system-auth-control
    interface f0/1
    switchport mode access
    dot1x port-control auto
    end
    I able to login using the radius server, so radius is working (on ports other than f1/0). However when connecting to f1/0, the port on the 2950 remains blocked.
    3. The certificate is issued by the ca server, is viewable via Internet explorer,and is issued to the correct username which is on the active directory.
    I even tried using local authenication with 802.1x, this did not work
    4. If I have a certificate, will this automatically give me access to the 802.1x port?
    5. I have windows 2000, and authenication is set to 'Smart Card or other certificate.
    Am I missing anything?
    Any advise will be greatly appreciated
    Chris

  • Pdp authentication error on iPad3

    Why is my APN telstra.corp setting coming up with a pdp authentication error.
    I am trying to connect to our secure network via telstra.corp.  When I use a 3G USB modem, I have no problems, as soon as I set the same config in my iPad I get the error.  I have sat for over an hour with a Telstra engineer and he can't see my iPad even trying to access our radius.  What is going on????
    I have heard that the iPad can not pass the @ sign found in the username (username@domainname) through for security authentication, is this true?
    If it is, how do I get around this.
    Any suggestions would be helpful.
    Thanks.

    Same issue.  Sitting here in Europe (Germany) trying to do some work.  From the Support technical discussions, there are numerous complaints like this.  Went by T-Mobile twiice already; they point the finger at Apple.   (I'm sure I could call back to the USA and sit on hold for an hour, with most likely Apple blaming the telco's.)  Not very impressed to say the least.  Wonder how Android is doing in this regard ...........?

  • Shell access required for RADIUS authentication?

    Hello all,
    A customer of mine has a fleet of modern Mac laptops, all accessing 3 AFP file servers. Access to those file servers is governed by a Snow Leopard Open Directory Master. Pretty simple.
    I’ve been tasked with introducing RADIUS authentication to the WLAN there. The WAPs are all Airport Extremes, so again the setup is pretty simple.
    But in testing, I see that users can authenticate to the RADIUS WLAN only if I give those user accounts shell access in Open Directory. If a user’s account has a login shell set to None (our previous default), then any RADIUS authentication attempt produces the following log error:
    Auth: [unix] [USERNAME]: invalid shell [/dev/null]
    If I switch that user’s login shell to (for example) /bin/bash, then restart RADIUS, that user authenticates successfully thereafter.
    Is this expected behavior? Is there an alternative to giving everyone shell access?
    Thanks for any info,
    Brandon White
    System Administrator
    www.technico.us

    Hi Peter,
    have a look at the RADIUS implementation CookBook (www.vasco.com/novell)
    chris
    > We use Vasco tokens for two things: Checkpoint Firewall-1 VPN
    > authentication, and iChain 2.2 RADIUS authentication. The current
    > RADIUS.NLM that we use is from the iChain authentication CD.
    >
    > The only problem I can think of to mention is the "Unknown RADIUS client"
    > error that we got after NW6 SP5. That was solved by the latest NMAS
    patches
    > and an upgrade from eDir 8.6.2 to 8.7.3.
    >
    >
    > "Peter van de Meerendonk" <[email protected]>
    wrote in
    > message news:JNiQd.595$[email protected]..
    > > > Well, just let me cover my hiney a little. We did have extremely bad
    > > > results with Activcard ACO000 tokens, but that is an old product from
    > > about
    > > > 3-4 years ago. I have no knowledge of the current Activcard tokens.
    > > >
    > > OK, but the licensing policy makes activcard a costly alternative.
    we've
    > got
    > > a good deal on RSA, and are negociating a deal on Vasco. eventually we
    > might
    > > need 250+ tokens.
    > >
    > > I am very interested in configuration details of your setup. do you use
    > the
    > > tokens only for checkpoint authentication, or for novell
    authentication as
    > > well?
    > >
    > >
    > >
    >
    >

  • NMAS based token for radius authentication towards checkpoint firewall

    hi,
    i'm looking for token based access towards a checkpoint firewall. i found
    out about radius, and think that's the way to go.
    our user administration is NW65SP2 & Edir 8.7.3 based.
    has anyone a success story about a token based radius server based on this
    configuration ?
    which token ?
    additional software ?
    anyone ?

    Hi Peter,
    have a look at the RADIUS implementation CookBook (www.vasco.com/novell)
    chris
    > We use Vasco tokens for two things: Checkpoint Firewall-1 VPN
    > authentication, and iChain 2.2 RADIUS authentication. The current
    > RADIUS.NLM that we use is from the iChain authentication CD.
    >
    > The only problem I can think of to mention is the "Unknown RADIUS client"
    > error that we got after NW6 SP5. That was solved by the latest NMAS
    patches
    > and an upgrade from eDir 8.6.2 to 8.7.3.
    >
    >
    > "Peter van de Meerendonk" <[email protected]>
    wrote in
    > message news:JNiQd.595$[email protected]..
    > > > Well, just let me cover my hiney a little. We did have extremely bad
    > > > results with Activcard ACO000 tokens, but that is an old product from
    > > about
    > > > 3-4 years ago. I have no knowledge of the current Activcard tokens.
    > > >
    > > OK, but the licensing policy makes activcard a costly alternative.
    we've
    > got
    > > a good deal on RSA, and are negociating a deal on Vasco. eventually we
    > might
    > > need 250+ tokens.
    > >
    > > I am very interested in configuration details of your setup. do you use
    > the
    > > tokens only for checkpoint authentication, or for novell
    authentication as
    > > well?
    > >
    > >
    > >
    >
    >

  • SBR for RADIUS Authentication

    Hi Everyone,
    Does anybody know if Steel Belt Radius would be able to authenticate both the telnet and enable passwords for RADIUS authentication?
    I have tried IAS, but apparently IAS does not have any understanding of the enable password and therefore returns an error.
    Any help would be great.
    Thanks,
    Dan

    "enable password" authorization is not supported in RADIUS authorization. TACACS+ supports it.

  • ACS 5.3 Radius authentication with ASA and DACL

    Hi,
    I am trying to do Radius authentication on the ACS 5.3 for VPN access (cisco client) using a downloadable ACL with AD identity
    Clients are connecting to an ASA 5510 with image asa843-K8.bin
    I followed the configuration example on the Cisco site, but I am having some problems
    First : AD identity is not triggered, I put a profile  :
    Status
    Name
    Conditions
    Results
    Hit Count
    NDG:Location
    Time And   Date
    AD1:memberOf
    Authorization   Profiles
    1
    TestVPNDACL
    -ANY-
    -ANY-
    equals Network Admin
    TEST DACL
    0
    But if I am getting no hits on it, Default Access is being used (Permit Access)
    So I tried putting the DACL in the default profile, but when connecting I am immediately disconnected.
    I can see the DACL/ASA being authenticated in the ACS log but no success
    I am using my user which is member of the Network Admin Group.
    Am I missing something?
    Any help greatly appreciated!
    Wim

    Hello Stephen,
    As per the IP Pools feature, the ACS 5.x does not include such functionality. It is not on the ACS 5.x roadmap either as the recommended scenario would be to use a dedicated DHCP server.
    ACS 4.x included that functionality, however, it was not the best solution as the ACS returned the IP Address value as a RADIUS Attribute instead of acting as a real DCHP server.
    As per the IMEI and MISDN I am assuming you are referring to International Mobile Equipment Identity and Mobile Subscriber ISDN. Correct me if I am wrong.
    In that case it seems that the ACS 5.x should be able to Allow or Deny access based on Radius Attribute 30 (Called-Station-Id) and 31 (Calling-Station-Id).
    In that case you might want to use the End-Station Filters feature and use it as the condition for the Rule. The End-Station Filter feature uses CLI/DNIS where CLI is Radius Attribute 31 and DNIS is Attribute 30.
    I am assuming a Generic Username will be embedded on the devices request. In that case you will define which end-user devices will be granted access based on the above attributes.
    Here is a snapshot of the section:

  • ASA , Cisco VPN client with RADIUS authentication

    Hi,
    I have configured ASA for Cisco VPN client with RADIUS authentication using Windows 2003 IAS.
    All seems to be working I get connected and authenticated. However even I use user name and password from Active Directory when connecting with Cisco VPN client I still have to provide these credentials once again when accessing domain resources.
    Should it work like this? Would it be possible to configure ASA/IAS/VPN client in such a way so I enter user name/password just once when connecting and getting access to domain resources straight away?
    Thank you.
    Kind regards,
    Alex

    Hi Alex,
    It is working as it should.
    You can enable the vpn client to start vpn before logon. That way you login to vpn and then logon to the domain. However, you are still entering credentials twice ( vpn and domain) but you have access to domain resources and profiles.
    thanks
    John

  • VPN 3000 and Radius authentication/authorization

    hello.
    I have to configure RADIUS authentication
    with a VPN 3000 concentrator.
    I'm completely new with this product
    (the concentrator).
    It seems that, if I want to perform authentication
    of username and password with Radius, then I also have to download the entire VPN configuration from the same Radius, using the attibute set loaded with the appropriate dictionary.
    am I rigth with this supposition?
    I mean: should be possible to authenticate only an username and password externally on RADIUS, while continuing to mantain the user (or group) VPN configuration locally in the concentrator?
    thank you.
    Davide

    No, downloading the entire VPN configuration from the RADIUS server is not necessary. If you are new to configuring VPN's on concentrators or the Concentrator iself, having a look at the support page will be agood idea. It is accessible at http://www.cisco.com/pcgi-bin/Support/browse/psp_view.pl?p=Hardware:Cisco_VPN_3000_Concentrator

  • How to fix authentic error in game centre of iPad mini?

    How to fix authentic error in game centre of iPad mini?

    Following further research, this keyboard lag issue appears to be related to the (botched) iOS 7.1 update. It's good to know I am not the only user who had his iPad mini rendered unusuable by the iOS 7.1 update, however that does not solve my problem.
    Anyone out there who has further suggestions (except doing a factory reset via iTunes)?

Maybe you are looking for