Reauthentication after roaming

I understand as part of EAP there's an extra GINA in Windows to allow authentication to SecureACS via the Access Point. Radius is used so user name & password must be sent to the SecureACS, then NTLM to Windows DC?
Then how does reauthentication take place after roaming to another access point? Are some credentials cached on the workstation? Or does the SecureACS handle some caching of credentials? Or does user name & password have to be input again?
Can't find good docs on this.
Thanks
Matthew

Windows will cache it until you log off I think. You shouldn’t have to keep re-authenticating.

Similar Messages

  • Anyconnect ios Wifi issues after roaming

    Hi,
    After roaming with cellular network, the wifi does not access the network despite the connection established. I have to renew the lease of the connection to have access to the network.
    I encounter the problem on IOS 5.1 with the latest version of AnyConnect. Have you everencountered this problem?
    thank you,
    Cedric H.
    France

    Hi,
    After roaming with cellular network, the wifi does not access the network despite the connection established. I have to renew the lease of the connection to have access to the network.
    I encounter the problem on IOS 5.1 with the latest version of AnyConnect. Have you everencountered this problem?
    thank you,
    Cedric H.
    France

  • Battery drains after roaming

    For several times I have now noticed that once I come back to my home country after roaming , my mobile behaves as if it is still roaming - in the sense that battery keeps getting drained constantly and does not even last like 4 hours. I am given to understand that while roaming it is a common phenomenon for bateery to behave like that but why once I am back? The problem also rectifies itself after several days for no known reason! Is this a issue other have faced and how to over come this?

    To resolve this issue when you get home, remove the battery for a full 5 minutes, then reinsert. This should get your BlackBerry to reconnect correctly to your home network if you're noticing these issues as it will push updates to your phone.
    If you want to thank someone for their comment, do so by clicking the Thumbs Up icon.
    If your issue is resolved, don't forget to click the Solution button on the resolution!

  • MailForExchange failing on E61 after roaming

    Hi,
    We have several users with E61 phones that are complaining that once they visit another country where they are in roaming mode, MailForExchange no longer works when they return to the home network. We have had to reinstall everything from scratch to get M4E working again.
    Phone op sys:
    3.0633.09.04 20-11-06 RM-89 Nokia E61
    Mail for Exchange version is 2.0.
    Any ideas how to fix this without a complete reinstall?
    Access to the internet is working. We've tried to fix this by manually setting the access point but it still is not working.
    T: Tomi

    I am having the same problem did anyone managed to find a solution.

  • Sleeping iOS Device, Waking Up After Roam & EAP Authentication

    Has anyone here (Scott Fella, maybe?) experienced an iOS device waking up from sleep and completing a successful EAP authentication?
    All the Cisco recommended WLC tweaks discussed on these forums (load balancing off, lower data rates disabled, etc.) have been implemented.  The WLAN is very well designed with proper SNR, channel separation, etc.  Still, iOS devices will wake up having roamed to a new AP and take 20 seconds or more to authenticate.  This is in a retail environment with customers staring, waiting.  20 seconds can be a long time with a customer staring at you.  Non iOS devices do not have the issue.  iOS devices on an open SSID do not have an issue, so I'm questioning EAP timing and wonder if anyone here can chime in with suggestions.
    Any insight appreciated.

    It should be done within seconds. Could you give us the output of the following commands?
    Show sysinfo
    Show wlan x
    Debug mac x from an client waking up?

  • Carrier wont change on iphone 3g after roaming

    Hi all,
    I was on holiday few days ago in Turkey,
    The iphone worked great.
    But when i returend to my country it still got the same carrier name and it's working with my local carrier.
    I tried to restore the iphone,
    Nothing helps
    Thanks in advance,
    Alik
    Message was edited by: alik r

    did you reset the phone?
    restoring and reseting are two different things. Sometimes just simply turning off the phone and turning it back on will work.

  • Problems after upgrading LMS from 4.1 to 4.2.3

    After the upgrade of the LMS we have the situation that all our deviced are visible in the subnet groups but not in "all devices".
    When I want to launch an inventory collection the following message is displayed:
    "ICSU0025: Problem with JRM. The JRM server may not be running. Check ICServerUI.log for more details. See the user guide Administration of CiscoWorks LMS for the log file location."
    When I do a Discovery, the deviced are being discovered but they are unreachable.
    And all the host names are changed into their IP addresses.
    I can't seem to find the problem. Even after roaming the forum here.
    I'm not able to pinpoint the exact cause of the problems...
    Any ideas?
    regards,
    W

    That is a healthy normal state for ANIServer. I checked some similar cases and it seems most of them were transient and got resolved once daemon was reatarted.
    I would suggest to follow this procedure once additionally :
    > Stop Daemon manager
    > Regenerate SSL certificate
    > Do a transaction log for RME DB
    > Start the daemon
    For 2nd and 3rd check my this post for process :
    https://supportforums.cisco.com/message/3597059#3597059
    If this is Solaris/linux, for transaction log, check this link (under Recovering From a Server Crash).
    -Thanks

  • Advanced Analysis - Problems after patch 5

    Just installed patch 5 of Advanced Analysis (12/09/2011) and get this error message when I try to log on to any SAP BW system. It accepts the password and then stops with the error below.
    The folder and file mentioned does not exist on my C drive. It starts going wrong after Roaming, I don't have a SAP AG folder.
    Could not find a part of the path 'C:\Users\<my_user_name_replaced_for_this_post>\AppData\Roaming\SAP AG\SAP BusinessObjects Advanced Analysis\logonHistory2.xml'.
    Does anybody know how to fix this?
    In the meantime I probably re-install the patch and maybe even the first install.
    kind regards,
    Ralf

    I didn't touch the installation (no re-install or anything) but just created an empty file logonHistory2.xml in the mentioned folder.
    After this I was able to log on and after that I had content in this file, as well as another file named xlsRecentDataSourceList.xml
    Now Advanced Analisys patch 5 works fine.

  • Voice VLAN on Wireless and Roaming

    While roaming on 1200 AP's with multiple VLANS using cards and VOIP phones the VLAN will quit passing traffice after roaming between multiple access points. Any answers

    Did you ever figure anything out, I too am having problems roaming between AP's Using 7920's

  • SPA8000 not re-establishing PPPoE Session after extended outage

    Hi,
    I have an SPA8000 Bridged to a ADSL2+ Modem and the SPA8000 performs PPPoE Authentication. If there is a drop in the service, it will automatically redial back in, however if there is an extended outage (eg. Loss of Line Sync, Carrier Issues) the SPA8000 will refuse to reconnect automatically without intervention (eg. Rebooting).
    The SPA8000 is running version 6.1.11, some basic settings:
    Under WAN:
    WAN Type: PPPoE
    DNS Server: Manual
    Username and Password are setup as per the PPPoE Account Details.
    Everything is default.
    Under Voice:
    SIP Registry Expires on the Line are set to 600 seconds, Provider SIP Proxy is set along (DNS Based not IP Address) with Username and Password - everything else is left as default.
    This is been tested on 3 separate SPA8000 devices experencing the same issue. NAT Keep Alive has been toggled to no success either.
    Are you able to provide insight into this? I can supply further information if required.
    Thanks
    David

    Hi Dan,
    Apologies for the late reply to this message - I had to setup a test environment to emulate this problem. It appears there is a problem where by the SPA8000 (and this may apply to other models as well) does not try to re-authenticate again after initially retrying 4 Times (in quick 2 second increments) after receiving an Invalid Username/Password Response or Timeout from a PPPoE Server or LNS. It does however work if there it does not respond to a PPPoE discovery (eg. Unplugging the Ethernet Cable between the SPA8000 and the Modem/NTU or there is no communication between the network and Modem/NTU).
    Here are the debug logs from where it did not try to re-authenticate and the only requests that I had back on the LNS. In this example the SIP Registry Expiry was set to 600 seconds and I changed the Password that it originally connected with and dropped/cleared the connection from the LNS. I waited the full 600 seconds and the PPPoE did not try again to re-authenticate.
    The Logs don't seem to indicate much (and I have changed IP Addresses/Hostnames in the below logs as well):
    <134>M2: System started: [email protected], reboot reason:H0
        192.168.0.3    23/04 17:10:32.642   
    <134>M2: System started: [email protected], reboot reason:H0
        192.168.0.3    23/04 17:10:32.642   
    <143>M2:     subnet mask:    255.255.255.0
        192.168.0.3    23/04 17:10:32.642   
    <143>M2:     gateway ip:    192.168.0.1
        192.168.0.3    23/04 17:10:32.642   
    <143>M2:     dns servers(1):        192.168.0.3    23/04 17:10:32.642   
    <143>M2: 192.168.0.1     192.168.0.3    23/04 17:10:32.642   
    <143>M2: 
        192.168.0.3    23/04 17:10:32.642   
    <159>M0: IDBG: st-0
        192.168.0.1    23/04 17:10:32.682   
    <159>M2: mslink server task up (2)
        192.168.0.3    23/04 17:10:34.422   
    <134>M3: System started: [email protected], reboot reason:H0
        192.168.0.4    23/04 17:10:35.793   
    <134>M3: System started: [email protected], reboot reason:H0
        192.168.0.4    23/04 17:10:35.793   
    <143>M3:     subnet mask:    255.255.255.0
        192.168.0.4    23/04 17:10:35.793   
    <143>M3:     gateway ip:    192.168.0.1
        192.168.0.4    23/04 17:10:35.793   
    <134>M1: System started: [email protected], reboot reason:H0
        192.168.0.2    23/04 17:10:35.793   
    <143>M3:     dns servers(1):        192.168.0.4    23/04 17:10:35.793   
    <134>M1: System started: [email protected], reboot reason:H0
        192.168.0.2    23/04 17:10:35.793   
    <143>M3: 192.168.0.1     192.168.0.4    23/04 17:10:35.793   
    <143>M1:     subnet mask:    255.255.255.0
        192.168.0.2    23/04 17:10:35.793   
    <143>M3: 
        192.168.0.4    23/04 17:10:35.793   
    <143>M1:     gateway ip:    192.168.0.1
        192.168.0.2    23/04 17:10:35.793   
    <143>M1:     dns servers(1):        192.168.0.2    23/04 17:10:35.793   
    <143>M1: 192.168.0.1     192.168.0.2    23/04 17:10:35.793   
    <143>M1: 
        192.168.0.2    23/04 17:10:35.793   
    <159>M3: mslink server task up (3)
        192.168.0.4    23/04 17:10:37.493   
    <159>M1: mslink server task up (1)
        192.168.0.2    23/04 17:10:37.533   
    <159>M1: IDBG: st-0
        192.168.0.2    23/04 17:10:38.203   
    <159>M1: fs:008275:008693:131072
        192.168.0.2    23/04 17:10:38.303   
    <159>M1: fls:af:1:0:0
        192.168.0.2    23/04 17:10:38.303   
    <159>M1: fbr:0:3000:3000:03985:0002:0001:6.1.12
        192.168.0.2    23/04 17:10:38.303   
    <159>M1: PLKUP: 8192, 2102, 12, 1.5
        192.168.0.2    23/04 17:10:38.333   
    <159>M1: fu:0:3997, 0003 0001
        192.168.0.2    23/04 17:10:38.483   
    <159>M2: IDBG: st-0
        192.168.0.3    23/04 17:10:39.093   
    <159>M2: fs:008200:008342:131072
        192.168.0.3    23/04 17:10:39.193   
    <159>M2: fls:af:1:0:0
        192.168.0.3    23/04 17:10:39.193   
    <159>M2: fbr:0:3000:3000:0358b:0002:0001:6.1.12
        192.168.0.3    23/04 17:10:39.193   
    <159>M2: PLKUP: 8192, 2102, 12, 1.5
        192.168.0.3    23/04 17:10:39.223   
    <159>M2: fu:0:359d, 0003 0001
        192.168.0.3    23/04 17:10:39.373   
    <159>M2: mslink client task (2)  gw=192.168.0.1  ip=192.168.0.3
        192.168.0.3    23/04 17:10:39.423   
    <159>M0: MSLINK module 2 is at 192.168.0.3
        192.168.0.1    23/04 17:10:40.164   
    <159>M3: IDBG: st-0
        192.168.0.4    23/04 17:10:40.174   
    <159>M0: MSLINK code module 2: 0(32) sn:0
        192.168.0.1    23/04 17:10:40.214   
    <159>M3: fs:008200:008351:131072
        192.168.0.4    23/04 17:10:40.254   
    <159>M3: fls:af:1:0:0
        192.168.0.4    23/04 17:10:40.264   
    <159>M3: fbr:0:3000:3000:04219:0002:0001:6.1.12
        192.168.0.4    23/04 17:10:40.264   
    <159>M3: PLKUP: 8192, 2102, 12, 1.5
        192.168.0.4    23/04 17:10:40.284   
    <159>M3: fu:0:422b, 0003 0001
        192.168.0.4    23/04 17:10:40.444   
    <159>M3: mslink client task (3)  gw=192.168.0.1  ip=192.168.0.4
        192.168.0.4    23/04 17:10:42.484   
    <159>M1: mslink client task (1)  gw=192.168.0.1  ip=192.168.0.2
        192.168.0.2    23/04 17:10:42.524   
    <159>M0: MSLINK module 3 is at 192.168.0.4
        192.168.0.1    23/04 17:10:43.234   
    <159>M0: MSLINK module 1 is at 192.168.0.2
        192.168.0.1    23/04 17:10:43.374   
    <159>M0: MSLINK code module 3: 0(32) sn:0
        192.168.0.1    23/04 17:10:43.374   
    <159>M0: MSLINK code module 1: 0(32) sn:0
        192.168.0.1    23/04 17:10:43.864   
    <159>M0: fs:025125:025125:131072
        192.168.0.1    23/04 17:10:47.215   
    <159>M0: fls:af:1:0:0
        192.168.0.1    23/04 17:10:47.215   
    <159>M0: fbr:1:3000:3000:17329:0004:0005:6.1.12
        192.168.0.1    23/04 17:10:47.215   
    <159>M0: fhs:01:0:0001:upg:app:0:5.1.10
        192.168.0.1    23/04 17:10:47.225   
    <159>M0: fhs:02:0:0002:upg:app:1:5.1.10
        192.168.0.1    23/04 17:10:47.275   
    <159>M0: fhs:03:0:0003:upg:app:2:5.1.10
        192.168.0.1    23/04 17:10:47.315   
    <159>M0: fhs:04:0:0004:upg:app:0:6.1.12
        192.168.0.1    23/04 17:10:47.385   
    <159>M0: fhs:05:0:0005:upg:app:1:6.1.12
        192.168.0.1    23/04 17:10:47.405   
    <159>M0: fhs:06:0:0006:upg:app:2:6.1.12
        192.168.0.1    23/04 17:10:47.435   
    <159>M0: PLKUP: 8192, 2102, 12, 1.5
        192.168.0.1    23/04 17:10:47.525   
    <159>M0: fu:1:733b, 0003 0001
        192.168.0.1    23/04 17:10:47.885   
    <159>M0: mslink  P:12831  V:55495
        192.168.0.1    23/04 17:11:00.106   
    <159>M1: CC_init
        192.168.0.2    23/04 17:11:02.516   
    <134>M1: SLIC is si3215
        192.168.0.2    23/04 17:11:02.606   
    <134>M1: SLIC is si3215
        192.168.0.2    23/04 17:11:02.606   
    <159>M1: IDBG[0]:4
        192.168.0.2    23/04 17:11:03.107   
    <159>M1: IDBG[1]:4
        192.168.0.2    23/04 17:11:03.107   
    <159>M2: CC_init
        192.168.0.3    23/04 17:11:03.407   
    <134>M2: SLIC is si3215
        192.168.0.3    23/04 17:11:03.487   
    <134>M2: SLIC is si3215
        192.168.0.3    23/04 17:11:03.497   
    <159>M2: IDBG[0]:4
        192.168.0.3    23/04 17:11:03.997   
    <159>M2: IDBG[1]:4
        192.168.0.3    23/04 17:11:03.997   
    <134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.2    23/04 17:11:04.237   
    <134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.2    23/04 17:11:04.237   
    <134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.2    23/04 17:11:04.237   
    <134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.2    23/04 17:11:04.247   
    <159>M3: CC_init
        192.168.0.4    23/04 17:11:04.477   
    <134>M3: SLIC is si3215
        192.168.0.4    23/04 17:11:04.557   
    <134>M3: SLIC is si3215
        192.168.0.4    23/04 17:11:04.567   
    <159>M3: IDBG[0]:5
        192.168.0.4    23/04 17:11:05.057   
    <159>M3: IDBG[1]:3
        192.168.0.4    23/04 17:11:05.057   
    <159>M0: CC_init
        192.168.0.1    23/04 17:11:05.957   
    <134>M0: SLIC is si3215
        192.168.0.1    23/04 17:11:06.517   
    <134>M0: SLIC is si3215
        192.168.0.1    23/04 17:11:06.527   
    <159>M0: IDBG[0]:6
        192.168.0.1    23/04 17:11:07.017   
    <159>M0: IDBG[1]:4
        192.168.0.1    23/04 17:11:07.017   
    <159>M1: [0]RegFail. Retry in 30
        192.168.0.2    23/04 17:11:36.231   
    <159>M1: [1]RegFail. Retry in 30
        192.168.0.2    23/04 17:11:36.241   
    <151>M1: CID:OSI
        192.168.0.2    23/04 17:11:38.231   
    <151>M1: CID:OSI
        192.168.0.2    23/04 17:11:38.241   
    <151>M1: CID:OnHookTx Pol
        192.168.0.2    23/04 17:11:38.491   
    <151>M1: CID:OnHookTx Pol
        192.168.0.2    23/04 17:11:38.501   
    <151>M1: Start DTMF/FSK
        192.168.0.2    23/04 17:11:38.792   
    <151>M1: Start DTMF/FSK
        192.168.0.2    23/04 17:11:38.792   
    <151>M1: CID:DONE
        192.168.0.2    23/04 17:11:39.232   
    <151>M1: CID:DONE
        192.168.0.2    23/04 17:11:39.242   
    <134>M0: System started: [email protected], reboot reason:H0
        192.168.0.1    23/04 17:11:46.632   
    <134>M0: System started: [email protected], reboot reason:H0
        192.168.0.1    23/04 17:11:46.632   
    <143>M0:     subnet mask:    255.255.255.255
        192.168.0.1    23/04 17:11:46.632   
    <143>M0:     gateway ip:    10.128.1.254
        192.168.0.1    23/04 17:11:46.642   
    <143>M0:     dns servers(2):        192.168.0.1    23/04 17:11:46.642   
    <143>M0: 4.2.2.1     192.168.0.1    23/04 17:11:46.642   
    <143>M0: 4.2.2.1     192.168.0.1    23/04 17:11:46.642   
    <143>M0: 
        192.168.0.1    23/04 17:11:46.652   
    <134>M0: [0]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.1    23/04 17:11:46.883   
    <134>M0: [0]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.1    23/04 17:11:46.883   
    <134>M0: [1]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.1    23/04 17:11:46.883   
    <134>M0: [1]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.1    23/04 17:11:46.893   
    <134>M0: [2]Reg Addr Change(0) 0:0->7dfe3007:5060
        192.168.0.1    23/04 17:11:46.933   
    <134>M0: [2]Reg Addr Change(0) 0:0->7dfe3007:5060
        192.168.0.1    23/04 17:11:46.933   
    <134>M0: [2]->10.10.10.7:5060(577)
        192.168.0.1    23/04 17:11:46.933   
    <134>M0: [2]->10.10.10.7:5060(577)
        192.168.0.1    23/04 17:11:46.943   
    <134>M0:
        192.168.0.1    23/04 17:11:46.943   
    <134>M0:
        192.168.0.1    23/04 17:11:46.943   
    <134>M0: [pxy]<<127.0.0.1:5060(486)
        192.168.0.1    23/04 17:11:46.943   
    <134>M0: [pxy]<<127.0.0.1:5060(486)
        192.168.0.1    23/04 17:11:46.953   
    <134>M0:
        192.168.0.1    23/04 17:11:46.953   
    <134>M0:
        192.168.0.1    23/04 17:11:46.953   
    <134>M0: [pxy]->127.0.0.1:5060(395)
        192.168.0.1    23/04 17:11:46.953   
    <134>M0: [pxy]->127.0.0.1:5060(395)
        192.168.0.1    23/04 17:11:46.953   
    <134>M0:
        192.168.0.1    23/04 17:11:46.953   
    <134>M0:
        192.168.0.1    23/04 17:11:46.953   
    <134>M0: [pxy]<<127.0.0.1:5061(485)
        192.168.0.1    23/04 17:11:46.963   
    <134>M0: [pxy]<<127.0.0.1:5061(485)
        192.168.0.1    23/04 17:11:46.963   
    <134>M0:
        192.168.0.1    23/04 17:11:46.963   
    <134>M0:
        192.168.0.1    23/04 17:11:46.963   
    <134>M0: [pxy]->127.0.0.1:5061(394)
        192.168.0.1    23/04 17:11:46.963   
    <134>M0: [pxy]->127.0.0.1:5061(394)
        192.168.0.1    23/04 17:11:46.963   
    <134>M0:
        192.168.0.1    23/04 17:11:46.963   
    <134>M0:
        192.168.0.1    23/04 17:11:46.963   
    <159>M0: [0]RegOK. NextReg in 2130706430 (1)
        192.168.0.1    23/04 17:11:46.963   
    <159>M0: [1]RegOK. NextReg in 2130706430 (1)
        192.168.0.1    23/04 17:11:46.963   
    <134>M0: [pxy]<<127.0.0.1:5060(426)
        192.168.0.1    23/04 17:11:46.973   
    <134>M0: [pxy]<<127.0.0.1:5060(426)
        192.168.0.1    23/04 17:11:46.973   
    <134>M0:
        192.168.0.1    23/04 17:11:46.973   
    <134>M0:
        192.168.0.1    23/04 17:11:46.973   
    <134>M0: [pxy]->127.0.0.1:5060(363)
        192.168.0.1    23/04 17:11:46.973   
    <134>M0: [pxy]->127.0.0.1:5060(363)
        192.168.0.1    23/04 17:11:46.973   
    <134>M0:
        192.168.0.1    23/04 17:11:46.973   
    <134>M0:
        192.168.0.1    23/04 17:11:46.973   
    <134>M0: [pxy]->10.128.1.4:5060(463)
        192.168.0.1    23/04 17:11:46.973   
    <134>M0: [pxy]->10.128.1.4:5060(463)
        192.168.0.1    23/04 17:11:46.973   
    <134>M0:
        192.168.0.1    23/04 17:11:46.983   
    <134>M0:
        192.168.0.1    23/04 17:11:46.983   
    <134>M0: [pxy]<<127.0.0.1:5061(426)
        192.168.0.1    23/04 17:11:46.983   
    <134>M0: [pxy]<<127.0.0.1:5061(426)
        192.168.0.1    23/04 17:11:46.983   
    <134>M0:
        192.168.0.1    23/04 17:11:46.983   
    <134>M0:
        192.168.0.1    23/04 17:11:46.983   
    <134>M0: [pxy]->127.0.0.1:5061(363)
        192.168.0.1    23/04 17:11:46.983   
    <134>M0: [pxy]->127.0.0.1:5061(363)
        192.168.0.1    23/04 17:11:46.983   
    <134>M0:
        192.168.0.1    23/04 17:11:46.983   
    <134>M0:
        192.168.0.1    23/04 17:11:46.983   
    <134>M0: [pxy]->10.128.1.4:5061(463)
        192.168.0.1    23/04 17:11:46.983   
    <134>M0: [pxy]->10.128.1.4:5061(463)
        192.168.0.1    23/04 17:11:46.983   
    <134>M0:
        192.168.0.1    23/04 17:11:46.983   
    <134>M0:
        192.168.0.1    23/04 17:11:46.983   
    <151>M0: [0]SubOK
        192.168.0.1    23/04 17:11:46.983   
    <151>M0: NextSub in 2147483646 (1)
        192.168.0.1    23/04 17:11:46.993   
    <151>M0: [1]SubOK
        192.168.0.1    23/04 17:11:46.993   
    <151>M0: NextSub in 2147483646 (1)
        192.168.0.1    23/04 17:11:46.993   
    <134>M0: [2]<<10.10.10.7:5060(545)
        192.168.0.1    23/04 17:11:46.993   
    <134>M0: [2]<<10.10.10.7:5060(545)
        192.168.0.1    23/04 17:11:46.993   
    <134>M0:
        192.168.0.1    23/04 17:11:46.993   
    <134>M0:
        192.168.0.1    23/04 17:11:46.993   
    <134>M0: [pxy]<<127.0.0.1:5060(352)
        192.168.0.1    23/04 17:11:46.993   
    <134>M0: [pxy]<<127.0.0.1:5060(352)
        192.168.0.1    23/04 17:11:46.993   
    <134>M0:
        192.168.0.1    23/04 17:11:46.993   
    <134>M0:
        192.168.0.1    23/04 17:11:46.993   
    <134>M0: [pxy]<<127.0.0.1:5061(352)
        192.168.0.1    23/04 17:11:46.993   
    <134>M0: [pxy]<<127.0.0.1:5061(352)
        192.168.0.1    23/04 17:11:46.993   
    <134>M0:
        192.168.0.1    23/04 17:11:46.993   
    <134>M0:
        192.168.0.1    23/04 17:11:46.993   
    <134>M0: [2]->10.10.10.7:5060(745)
        192.168.0.1    23/04 17:11:46.993   
    <134>M0: [2]->10.10.10.7:5060(745)
        192.168.0.1    23/04 17:11:46.993   
    <134>M0:
        192.168.0.1    23/04 17:11:47.003   
    <134>M0:
        192.168.0.1    23/04 17:11:47.003   
    <134>M0: [2]<<10.10.10.7:5060(566)
        192.168.0.1    23/04 17:11:47.053   
    <134>M0: [2]<<10.10.10.7:5060(566)
        192.168.0.1    23/04 17:11:47.053   
    <134>M0:
        192.168.0.1    23/04 17:11:47.053   
    <134>M0:
        192.168.0.1    23/04 17:11:47.063   
    <159>M0: [2]RegOK. NextReg in 594 (1)
        192.168.0.1    23/04 17:11:47.063   
    <151>M0: CID:OSI
        192.168.0.1    23/04 17:11:48.973   
    <151>M0: CID:OSI
        192.168.0.1    23/04 17:11:48.983   
    <151>M0: CID:OnHookTx Pol
        192.168.0.1    23/04 17:11:49.233   
    <151>M0: CID:OnHookTx Pol
        192.168.0.1    23/04 17:11:49.243   
    <151>M0: Start DTMF/FSK
        192.168.0.1    23/04 17:11:49.533   
    <151>M0: Start DTMF/FSK
        192.168.0.1    23/04 17:11:49.543   
    <151>M0: CID:DONE
        192.168.0.1    23/04 17:11:49.983   
    <151>M0: CID:DONE
        192.168.0.1    23/04 17:11:49.993   
    <134>M0: [pxy]<<192.168.0.2:5160(487)
        192.168.0.1    23/04 17:12:06.235   
    <134>M0: [pxy]<<192.168.0.2:5160(487)
        192.168.0.1    23/04 17:12:06.235   
    <134>M0:
        192.168.0.1    23/04 17:12:06.235   
    <134>M0:
        192.168.0.1    23/04 17:12:06.235   
    <134>M0: [pxy]->192.168.0.2:5160(398)
        192.168.0.1    23/04 17:12:06.245   
    <134>M0: [pxy]->192.168.0.2:5160(398)
        192.168.0.1    23/04 17:12:06.245   
    <134>M0:
        192.168.0.1    23/04 17:12:06.245   
    <134>M0:
        192.168.0.1    23/04 17:12:06.255   
    <134>M0: [pxy]<<192.168.0.2:5161(487)
        192.168.0.1    23/04 17:12:06.255   
    <134>M0: [pxy]<<192.168.0.2:5161(487)
        192.168.0.1    23/04 17:12:06.255   
    <134>M0:
        192.168.0.1    23/04 17:12:06.255   
    <134>M0:
        192.168.0.1    23/04 17:12:06.265   
    <159>M1: [0]RegOK. NextReg in 2130706430 (1)
        192.168.0.2    23/04 17:12:06.265   
    <134>M0: [pxy]->192.168.0.2:5161(398)
        192.168.0.1    23/04 17:12:06.265   
    <134>M0: [pxy]->192.168.0.2:5161(398)
        192.168.0.1    23/04 17:12:06.275   
    <134>M0:
        192.168.0.1    23/04 17:12:06.275   
    <134>M0:
        192.168.0.1    23/04 17:12:06.275   
    <134>M0: [pxy]<<192.168.0.2:5160(426)
        192.168.0.1    23/04 17:12:06.275   
    <134>M0: [pxy]<<192.168.0.2:5160(426)
        192.168.0.1    23/04 17:12:06.275   
    <134>M0:
        192.168.0.1    23/04 17:12:06.275   
    <134>M0:
        192.168.0.1    23/04 17:12:06.275   
    <159>M1: [1]RegOK. NextReg in 2130706430 (1)
        192.168.0.2    23/04 17:12:06.275   
    <134>M0: [pxy]->192.168.0.2:5160(363)
        192.168.0.1    23/04 17:12:06.275   
    <134>M0: [pxy]->192.168.0.2:5160(363)
        192.168.0.1    23/04 17:12:06.285   
    <134>M0:
        192.168.0.1    23/04 17:12:06.285   
    <134>M0:
        192.168.0.1    23/04 17:12:06.285   
    <134>M0: [pxy]->10.128.1.4:5160(464)
        192.168.0.1    23/04 17:12:06.285   
    <134>M0: [pxy]->10.128.1.4:5160(464)
        192.168.0.1    23/04 17:12:06.285   
    <134>M0:
        192.168.0.1    23/04 17:12:06.285   
    <134>M0:
        192.168.0.1    23/04 17:12:06.285   
    <151>M1: [0]SubOK
        192.168.0.2    23/04 17:12:06.285   
    <151>M1: NextSub in 2147483646 (1)
        192.168.0.2    23/04 17:12:06.285   
    <134>M0: [pxy]<<192.168.0.2:5161(427)
        192.168.0.1    23/04 17:12:06.285   
    <134>M0: [pxy]<<192.168.0.2:5161(427)
        192.168.0.1    23/04 17:12:06.285   
    <134>M0:
        192.168.0.1    23/04 17:12:06.285   
    <134>M0:
        192.168.0.1    23/04 17:12:06.295   
    <134>M0: [pxy]->192.168.0.2:5161(364)
        192.168.0.1    23/04 17:12:06.295   
    <134>M0: [pxy]->192.168.0.2:5161(364)
        192.168.0.1    23/04 17:12:06.295   
    <134>M0:
        192.168.0.1    23/04 17:12:06.295   
    <134>M0:
        192.168.0.1    23/04 17:12:06.295   
    <151>M1: [1]SubOK
        192.168.0.2    23/04 17:12:06.295   
    <151>M1: NextSub in 2147483646 (1)
        192.168.0.2    23/04 17:12:06.295   
    <134>M0: [pxy]->10.128.1.4:5161(464)
        192.168.0.1    23/04 17:12:06.295   
    <134>M0: [pxy]->10.128.1.4:5161(464)
        192.168.0.1    23/04 17:12:06.295   
    <134>M0:
        192.168.0.1    23/04 17:12:06.295   
    <134>M0:
        192.168.0.1    23/04 17:12:06.295   
    <134>M0: [pxy]<<192.168.0.2:5160(352)
        192.168.0.1    23/04 17:12:06.295   
    <134>M0: [pxy]<<192.168.0.2:5160(352)
        192.168.0.1    23/04 17:12:06.295   
    <134>M0:
        192.168.0.1    23/04 17:12:06.295   
    <134>M0:
        192.168.0.1    23/04 17:12:06.295   
    <134>M0: [pxy]<<192.168.0.2:5161(353)
        192.168.0.1    23/04 17:12:06.295   
    <134>M0: [pxy]<<192.168.0.2:5161(353)
        192.168.0.1    23/04 17:12:06.295   
    <134>M0:
        192.168.0.1    23/04 17:12:06.305   
    <134>M0:
        192.168.0.1    23/04 17:12:06.305   
    <151>M0: IDBG: pppld
        192.168.0.1    23/04 17:12:26.798   
    <151>M0: [2]SIP:ICMP Error -1 (7dfe3007:5060, 8)
        192.168.0.1    23/04 17:21:41.045   
    <134>M0: [2]->10.10.10.7:5060(745)
        192.168.0.1    23/04 17:21:41.045   
    <134>M0: [2]->10.10.10.7:5060(745)
        192.168.0.1    23/04 17:21:41.045   
    <134>M0:
        192.168.0.1    23/04 17:21:41.045   
    <134>M0:
        192.168.0.1    23/04 17:21:41.045   
    <159>M0: RSE_DEBUG: getting alternate from domain:sip.siptest.com
        192.168.0.1    23/04 17:21:41.055   
    <159>M0: [2]RegFail. Retry in 30
        192.168.0.1    23/04 17:21:41.055   
    <151>M0: [2]SIP:ICMP Error -1 (7dfe3007:5060, 8)
        192.168.0.1    23/04 17:22:11.049   
    <134>M0: [2]->10.10.10.7:5060(577)
        192.168.0.1    23/04 17:22:11.059   
    <134>M0: [2]->10.10.10.7:5060(577)
        192.168.0.1    23/04 17:22:11.069   
    <134>M0:
        192.168.0.1    23/04 17:22:11.069   
    <134>M0:
        192.168.0.1    23/04 17:22:11.069   
    <159>M0: RSE_DEBUG: getting alternate from domain:sip.siptest.com
        192.168.0.1    23/04 17:22:11.069   
    <159>M0: [2]RegFail. Retry in 30
        192.168.0.1    23/04 17:22:11.069   
    core-rtr#
    Apr 23 07:12:28.636: %LINK-3-UPDOWN: Interface Virtual-Access78, changed state to down
    Apr 23 07:12:29.636: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access78, changed state to down
    Apr 23 07:12:33.688: ppp261 PPP: Authorization required
    Apr 23 07:12:33.692: ppp261 PPP: Authorization required
    Apr 23 07:12:33.732: ppp261 CHAP: O CHALLENGE id 2 len 29 from "core-rtr"
    Apr 23 07:12:33.776: ppp261 CHAP: I RESPONSE id 2 len 55 from "[email protected]"
    Apr 23 07:12:33.776: ppp261 PPP: Sent CHAP LOGIN Request
    Apr 23 07:12:35.776: ppp261 PPP: Received LOGIN Response FAIL
    Apr 23 07:12:35.776: ppp261 CHAP: O FAILURE id 2 len 25 msg is "Authentication failed"
    Apr 23 07:12:37.788: ppp262 PPP: Authorization required
    Apr 23 07:12:37.788: ppp262 PPP: Authorization required
    Apr 23 07:12:37.832: ppp262 CHAP: O CHALLENGE id 2 len 29 from "core-rtr"
    Apr 23 07:12:37.872: ppp262 CHAP: I RESPONSE id 2 len 55 from "[email protected]"
    Apr 23 07:12:37.872: ppp262 PPP: Sent CHAP LOGIN Request
    Apr 23 07:12:39.872: ppp262 PPP: Received LOGIN Response FAIL
    Apr 23 07:12:39.872: ppp262 CHAP: O FAILURE id 2 len 25 msg is "Authentication failed"
    Apr 23 07:12:41.880: ppp263 PPP: Authorization required
    Apr 23 07:12:41.880: ppp263 PPP: Authorization required
    Apr 23 07:12:41.924: ppp263 CHAP: O CHALLENGE id 2 len 29 from "core-rtr"
    Apr 23 07:12:41.964: ppp263 CHAP: I RESPONSE id 2 len 55 from "[email protected]"
    Apr 23 07:12:41.964: ppp263 PPP: Sent CHAP LOGIN Request
    Apr 23 07:12:43.968: ppp263 PPP: Received LOGIN Response FAIL
    Apr 23 07:12:43.968: ppp263 CHAP: O FAILURE id 2 len 25 msg is "Authentication failed"
    Apr 23 07:12:45.980: ppp264 PPP: Authorization required
    Apr 23 07:12:45.980: ppp264 PPP: Authorization required
    Apr 23 07:12:46.020: ppp264 CHAP: O CHALLENGE id 2 len 29 from "core-rtr"
    Apr 23 07:12:46.064: ppp264 CHAP: I RESPONSE id 2 len 55 from "[email protected]"
    Apr 23 07:12:46.064: ppp264 PPP: Sent CHAP LOGIN Request
    Apr 23 07:12:48.064: ppp264 PPP: Received LOGIN Response FAIL
    Apr 23 07:12:48.064: ppp264 CHAP: O FAILURE id 2 len 25 msg is "Authentication failed"
    core-rtr#
    Here is the log from a successful reauthentication AFTER the modem/NTU had lost connectivity to the network:
    <134>M1: System started: [email protected], reboot reason:H0
        192.168.0.2    23/04 17:26:12.220   
    <134>M1: System started: [email protected], reboot reason:H0
        192.168.0.2    23/04 17:26:12.220   
    <143>M1:     subnet mask:    255.255.255.0
        192.168.0.2    23/04 17:26:12.220   
    <143>M1:     gateway ip:    192.168.0.1
        192.168.0.2    23/04 17:26:12.220   
    <143>M1:     dns servers(1):        192.168.0.2    23/04 17:26:12.220   
    <143>M1: 192.168.0.1     192.168.0.2    23/04 17:26:12.220   
    <143>M1: 
        192.168.0.2    23/04 17:26:12.220   
    <159>M1: mslink server task up (1)
        192.168.0.2    23/04 17:26:12.290   
    <159>M0: IDBG: st-0
        192.168.0.1    23/04 17:26:12.430   
    <134>M3: System started: [email protected], reboot reason:H0
        192.168.0.4    23/04 17:26:14.390   
    <134>M3: System started: [email protected], reboot reason:H0
        192.168.0.4    23/04 17:26:14.390   
    <143>M3:     subnet mask:    255.255.255.0
        192.168.0.4    23/04 17:26:14.390   
    <143>M3:     gateway ip:    192.168.0.1
        192.168.0.4    23/04 17:26:14.390   
    <143>M3:     dns servers(1):        192.168.0.4    23/04 17:26:14.400   
    <143>M3: 192.168.0.1     192.168.0.4    23/04 17:26:14.400   
    <143>M3: 
        192.168.0.4    23/04 17:26:14.400   
    <134>M2: System started: [email protected], reboot reason:H0
        192.168.0.3    23/04 17:26:14.400   
    <134>M2: System started: [email protected], reboot reason:H0
        192.168.0.3    23/04 17:26:14.400   
    <143>M2:     subnet mask:    255.255.255.0
        192.168.0.3    23/04 17:26:14.400   
    <143>M2:     gateway ip:    192.168.0.1
        192.168.0.3    23/04 17:26:14.400   
    <143>M2:     dns servers(1):        192.168.0.3    23/04 17:26:14.400   
    <143>M2: 192.168.0.1     192.168.0.3    23/04 17:26:14.400   
    <143>M2: 
        192.168.0.3    23/04 17:26:14.400   
    <159>M2: mslink server task up (2)
        192.168.0.3    23/04 17:26:16.190   
    <159>M3: mslink server task up (3)
        192.168.0.4    23/04 17:26:16.260   
    <159>M1: mslink client task (1)  gw=192.168.0.1  ip=192.168.0.2
        192.168.0.2    23/04 17:26:16.280   
    <159>M0: MSLINK module 1 is at 192.168.0.2
        192.168.0.1    23/04 17:26:17.010   
    <159>M0: MSLINK code module 1: 0(32) sn:0
        192.168.0.1    23/04 17:26:17.060   
    <159>M1: IDBG: st-0
        192.168.0.2    23/04 17:26:18.240   
    <159>M1: fs:008275:008693:131072
        192.168.0.2    23/04 17:26:18.330   
    <159>M1: fls:af:1:0:0
        192.168.0.2    23/04 17:26:18.330   
    <159>M1: fbr:0:3000:3000:03997:0002:0001:6.1.12
        192.168.0.2    23/04 17:26:18.330   
    <159>M1: PLKUP: 8192, 2102, 12, 1.5
        192.168.0.2    23/04 17:26:18.370   
    <159>M1: fu:0:39a9, 0003 0001
        192.168.0.2    23/04 17:26:18.540   
    <159>M2: IDBG: st-0
        192.168.0.3    23/04 17:26:18.860   
    <159>M2: fs:008200:008342:131072
        192.168.0.3    23/04 17:26:18.960   
    <159>M2: fls:af:1:0:0
        192.168.0.3    23/04 17:26:18.960   
    <159>M2: fbr:0:3000:3000:0359d:0002:0001:6.1.12
        192.168.0.3    23/04 17:26:18.960   
    <159>M2: PLKUP: 8192, 2102, 12, 1.5
        192.168.0.3    23/04 17:26:18.990   
    <159>M2: fu:0:35af, 0003 0001
        192.168.0.3    23/04 17:26:19.150   
    <159>M3: IDBG: st-0
        192.168.0.4    23/04 17:26:19.931   
    <159>M3: fs:008200:008351:131072
        192.168.0.4    23/04 17:26:20.021   
    <159>M3: fls:af:1:0:0
        192.168.0.4    23/04 17:26:20.021   
    <159>M3: fbr:0:3000:3000:0422b:0002:0001:6.1.12
        192.168.0.4    23/04 17:26:20.021   
    <159>M3: PLKUP: 8192, 2102, 12, 1.5
        192.168.0.4    23/04 17:26:20.051   
    <159>M3: fu:0:423d, 0003 0001
        192.168.0.4    23/04 17:26:20.211   
    <159>M3: mslink client task (3)  gw=192.168.0.1  ip=192.168.0.4
        192.168.0.4    23/04 17:26:20.251   
    <159>M0: MSLINK module 3 is at 192.168.0.4
        192.168.0.1    23/04 17:26:20.991   
    <159>M0: MSLINK code module 3: 0(32) sn:0
        192.168.0.1    23/04 17:26:21.041   
    <159>M2: mslink client task (2)  gw=192.168.0.1  ip=192.168.0.3
        192.168.0.3    23/04 17:26:21.181   
    <159>M0: MSLINK module 2 is at 192.168.0.3
        192.168.0.1    23/04 17:26:22.262   
    <159>M0: MSLINK code module 2: 0(32) sn:0
        192.168.0.1    23/04 17:26:22.332   
    <159>M0: fs:025125:025125:131072
        192.168.0.1    23/04 17:26:26.852   
    <159>M0: fls:af:1:0:0
        192.168.0.1    23/04 17:26:26.852   
    <159>M0: fbr:1:3000:3000:1733b:0004:0005:6.1.12
        192.168.0.1    23/04 17:26:26.852   
    <159>M0: fhs:01:0:0001:upg:app:0:5.1.10
        192.168.0.1    23/04 17:26:26.852   
    <159>M0: fhs:02:0:0002:upg:app:1:5.1.10
        192.168.0.1    23/04 17:26:26.882   
    <159>M0: fhs:03:0:0003:upg:app:2:5.1.10
        192.168.0.1    23/04 17:26:26.922   
    <159>M0: fhs:04:0:0004:upg:app:0:6.1.12
        192.168.0.1    23/04 17:26:26.962   
    <159>M0: fhs:05:0:0005:upg:app:1:6.1.12
        192.168.0.1    23/04 17:26:26.992   
    <159>M0: fhs:06:0:0006:upg:app:2:6.1.12
        192.168.0.1    23/04 17:26:27.032   
    <159>M0: PLKUP: 8192, 2102, 12, 1.5
        192.168.0.1    23/04 17:26:27.132   
    <159>M0: fu:1:734d, 0003 0001
        192.168.0.1    23/04 17:26:27.442   
    <159>M0: mslink  P:12222  V:58850
        192.168.0.1    23/04 17:26:39.354   
    <159>M1: CC_init
        192.168.0.2    23/04 17:26:42.275   
    <134>M1: SLIC is si3215
        192.168.0.2    23/04 17:26:42.355   
    <134>M1: SLIC is si3215
        192.168.0.2    23/04 17:26:42.355   
    <159>M1: IDBG[0]:4
        192.168.0.2    23/04 17:26:42.845   
    <159>M1: IDBG[1]:4
        192.168.0.2    23/04 17:26:42.845   
    <159>M2: CC_init
        192.168.0.3    23/04 17:26:43.175   
    <134>M2: SLIC is si3215
        192.168.0.3    23/04 17:26:43.255   
    <134>M2: SLIC is si3215
        192.168.0.3    23/04 17:26:43.255   
    <159>M2: IDBG[0]:4
        192.168.0.3    23/04 17:26:43.745   
    <159>M2: IDBG[1]:3
        192.168.0.3    23/04 17:26:43.745   
    <134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.2    23/04 17:26:43.985   
    <134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.2    23/04 17:26:43.985   
    <134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.2    23/04 17:26:43.985   
    <134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.2    23/04 17:26:43.985   
    <159>M3: CC_init
        192.168.0.4    23/04 17:26:44.245   
    <134>M3: SLIC is si3215
        192.168.0.4    23/04 17:26:44.325   
    <134>M3: SLIC is si3215
        192.168.0.4    23/04 17:26:44.325   
    <159>M3: IDBG[0]:5
        192.168.0.4    23/04 17:26:44.815   
    <159>M3: IDBG[1]:4
        192.168.0.4    23/04 17:26:44.815   
    <159>M0: CC_init
        192.168.0.1    23/04 17:26:45.715   
    <134>M0: SLIC is si3215
        192.168.0.1    23/04 17:26:46.275   
    <134>M0: SLIC is si3215
        192.168.0.1    23/04 17:26:46.275   
    <159>M0: IDBG[0]:6
        192.168.0.1    23/04 17:26:46.755   
    <159>M0: IDBG[1]:4
        192.168.0.1    23/04 17:26:46.765   
    <134>M0: System started: [email protected], reboot reason:H0
        192.168.0.1    23/04 17:27:13.110   
    <134>M0: System started: [email protected], reboot reason:H0
        192.168.0.1    23/04 17:27:13.110   
    <143>M0:     subnet mask:    255.255.255.255
        192.168.0.1    23/04 17:27:13.120   
    <143>M0:     gateway ip:    125.254.48.254
        192.168.0.1    23/04 17:27:13.120   
    <143>M0:     dns servers(2):        192.168.0.1    23/04 17:27:13.120   
    <143>M0: 4.2.2.1     192.168.0.1    23/04 17:27:13.120   
    <143>M0: 4.2.2.2     192.168.0.1    23/04 17:27:13.120   
    <143>M0: 
        192.168.0.1    23/04 17:27:13.120   
    <134>M0: [0]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.1    23/04 17:27:13.370   
    <134>M0: [0]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.1    23/04 17:27:13.370   
    <134>M0: [1]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.1    23/04 17:27:13.370   
    <134>M0: [1]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.1    23/04 17:27:13.370   
    <134>M0: [2]Reg Addr Change(0) 0:0->7dfe3007:5060
        192.168.0.1    23/04 17:27:13.420   
    <134>M0: [2]Reg Addr Change(0) 0:0->7dfe3007:5060
        192.168.0.1    23/04 17:27:13.420   
    <134>M0: [2]->10.10.10.7:5060(577)
        192.168.0.1    23/04 17:27:13.420   
    <134>M0: [2]->10.10.10.7:5060(577)
        192.168.0.1    23/04 17:27:13.420   
    <134>M0:
        192.168.0.1    23/04 17:27:13.420   
    <134>M0:
        192.168.0.1    23/04 17:27:13.420   
    <134>M0: [pxy]<<127.0.0.1:5060(485)
        192.168.0.1    23/04 17:27:13.420   
    <134>M0: [pxy]<<127.0.0.1:5060(485)
        192.168.0.1    23/04 17:27:13.420   
    <134>M0:
        192.168.0.1    23/04 17:27:13.420   
    <134>M0:
        192.168.0.1    23/04 17:27:13.420   
    <134>M0: [pxy]->127.0.0.1:5060(394)
        192.168.0.1    23/04 17:27:13.420   
    <134>M0: [pxy]->127.0.0.1:5060(394)
        192.168.0.1    23/04 17:27:13.420   
    <134>M0:
        192.168.0.1    23/04 17:27:13.420   
    <134>M0:
        192.168.0.1    23/04 17:27:13.420   
    <134>M0: [pxy]<<127.0.0.1:5061(486)
        192.168.0.1    23/04 17:27:13.430   
    <134>M0: [pxy]<<127.0.0.1:5061(486)
        192.168.0.1    23/04 17:27:13.430   
    <134>M0:
        192.168.0.1    23/04 17:27:13.430   
    <134>M0:
        192.168.0.1    23/04 17:27:13.430   
    <134>M0: [pxy]->127.0.0.1:5061(395)
        192.168.0.1    23/04 17:27:13.430   
    <134>M0: [pxy]->127.0.0.1:5061(395)
        192.168.0.1    23/04 17:27:13.430   
    <134>M0:
        192.168.0.1    23/04 17:27:13.430   
    <134>M0:
        192.168.0.1    23/04 17:27:13.430   
    <159>M0: [0]RegOK. NextReg in 2130706430 (1)
        192.168.0.1    23/04 17:27:13.430   
    <159>M0: [1]RegOK. NextReg in 2130706430 (1)
        192.168.0.1    23/04 17:27:13.440   
    <134>M0: [pxy]<<127.0.0.1:5060(433)
        192.168.0.1    23/04 17:27:13.440   
    <134>M0: [pxy]<<127.0.0.1:5060(433)
        192.168.0.1    23/04 17:27:13.440   
    <134>M0:
        192.168.0.1    23/04 17:27:13.440   
    <134>M0:
        192.168.0.1    23/04 17:27:13.440   
    <134>M0: [pxy]->127.0.0.1:5060(363)
        192.168.0.1    23/04 17:27:13.450   
    <134>M0: [pxy]->127.0.0.1:5060(363)
        192.168.0.1    23/04 17:27:13.450   
    <134>M0:
        192.168.0.1    23/04 17:27:13.450   
    <134>M0:
        192.168.0.1    23/04 17:27:13.450   
    <134>M0: [pxy]->10.128.1.4:5060(463)
        192.168.0.1    23/04 17:27:13.450   
    <134>M0: [pxy]->10.128.1.4:5060(463)
        192.168.0.1    23/04 17:27:13.450   
    <134>M0:
        192.168.0.1    23/04 17:27:13.450   
    <134>M0:
        192.168.0.1    23/04 17:27:13.450   
    <134>M0: [pxy]<<127.0.0.1:5061(425)
        192.168.0.1    23/04 17:27:13.450   
    <134>M0: [pxy]<<127.0.0.1:5061(425)
        192.168.0.1    23/04 17:27:13.450   
    <134>M0:
        192.168.0.1    23/04 17:27:13.450   
    <134>M0:
        192.168.0.1    23/04 17:27:13.450   
    <134>M0: [pxy]->127.0.0.1:5061(362)
        192.168.0.1    23/04 17:27:13.460   
    <134>M0: [pxy]->127.0.0.1:5061(362)
        192.168.0.1    23/04 17:27:13.460   
    <134>M0:
        192.168.0.1    23/04 17:27:13.460   
    <134>M0:
        192.168.0.1    23/04 17:27:13.460   
    <134>M0: [pxy]->10.128.1.4:5061(463)
        192.168.0.1    23/04 17:27:13.460   
    <134>M0: [pxy]->10.128.1.4:5061(463)
        192.168.0.1    23/04 17:27:13.460   
    <134>M0:
        192.168.0.1    23/04 17:27:13.460   
    <134>M0:
        192.168.0.1    23/04 17:27:13.460   
    <151>M0: [0]SubOK
        192.168.0.1    23/04 17:27:13.460   
    <151>M0: NextSub in 2147483646 (1)
        192.168.0.1    23/04 17:27:13.460   
    <151>M0: [1]SubOK
        192.168.0.1    23/04 17:27:13.470   
    <151>M0: NextSub in 2147483646 (1)
        192.168.0.1    23/04 17:27:13.470   
    <134>M0: [2]<<10.10.10.7:5060(545)
        192.168.0.1    23/04 17:27:13.470   
    <134>M0: [2]<<10.10.10.7:5060(545)
        192.168.0.1    23/04 17:27:13.470   
    <134>M0:
        192.168.0.1    23/04 17:27:13.470   
    <134>M0:
        192.168.0.1    23/04 17:27:13.470   
    <134>M0: [pxy]<<127.0.0.1:5060(351)
        192.168.0.1    23/04 17:27:13.480   
    <134>M0: [pxy]<<127.0.0.1:5060(351)
        192.168.0.1    23/04 17:27:13.480   
    <134>M0:
        192.168.0.1    23/04 17:27:13.480   
    <134>M0:
        192.168.0.1    23/04 17:27:13.480   
    <134>M0: [pxy]<<127.0.0.1:5061(350)
        192.168.0.1    23/04 17:27:13.480   
    <134>M0: [pxy]<<127.0.0.1:5061(350)
        192.168.0.1    23/04 17:27:13.480   
    <134>M0:
        192.168.0.1    23/04 17:27:13.480   
    <134>M0:
        192.168.0.1    23/04 17:27:13.480   
    <134>M0: [2]->10.10.10.7:5060(745)
        192.168.0.1    23/04 17:27:13.480   
    <134>M0: [2]->10.10.10.7:5060(745)
        192.168.0.1    23/04 17:27:13.480   
    <134>M0:
        192.168.0.1    23/04 17:27:13.480   
    <134>M0:
        192.168.0.1    23/04 17:27:13.480   
    <134>M0: [2]<<10.10.10.7:5060(566)
        192.168.0.1    23/04 17:27:13.550   
    <134>M0: [2]<<10.10.10.7:5060(566)
        192.168.0.1    23/04 17:27:13.550   
    <134>M0:
        192.168.0.1    23/04 17:27:13.550   
    <134>M0:
        192.168.0.1    23/04 17:27:13.550   
    <159>M0: [2]RegOK. NextReg in 594 (1)
        192.168.0.1    23/04 17:27:13.550   
    <151>M0: CID:OSI
        192.168.0.1    23/04 17:27:15.460   
    <151>M0: CID:OSI
        192.168.0.1    23/04 17:27:15.460   
    <134>M0: [pxy]<<192.168.0.2:5160(486)
        192.168.0.1    23/04 17:27:15.480   
    <134>M0: [pxy]<<192.168.0.2:5160(486)
        192.168.0.1    23/04 17:27:15.480   
    <134>M0:
        192.168.0.1    23/04 17:27:15.480   
    <134>M0:
        192.168.0.1    23/04 17:27:15.480   
    <134>M0: [pxy]->192.168.0.2:5160(398)
        192.168.0.1    23/04 17:27:15.480   
    <134>M0: [pxy]->192.168.0.2:5160(398)
        192.168.0.1    23/04 17:27:15.480   
    <134>M0:
        192.168.0.1    23/04 17:27:15.480   
    <134>M0:
        192.168.0.1    23/04 17:27:15.480   
    <134>M0: [pxy]<<192.168.0.2:5161(486)
        192.168.0.1    23/04 17:27:15.490   
    <134>M0: [pxy]<<192.168.0.2:5161(486)
        192.168.0.1    23/04 17:27:15.490   
    <134>M0:
        192.168.0.1    23/04 17:27:15.490   
    <134>M0:
        192.168.0.1    23/04 17:27:15.490   
    <159>M1: [0]RegOK. NextReg in 2130706400 (31)
        192.168.0.2    23/04 17:27:15.490   
    <134>M0: [pxy]->192.168.0.2:5161(398)
        192.168.0.1    23/04 17:27:15.490   
    <134>M0: [pxy]->192.168.0.2:5161(398)
        192.168.0.1    23/04 17:27:15.490   
    <134>M0:
        192.168.0.1    23/04 17:27:15.490   
    <134>M0:
        192.168.0.1    23/04 17:27:15.490   
    <134>M0: [pxy]<<192.168.0.2:5160(427)
        192.168.0.1    23/04 17:27:15.500   
    <134>M0: [pxy]<<192.168.0.2:5160(427)
        192.168.0.1    23/04 17:27:15.500   
    <134>M0:
        192.168.0.1    23/04 17:27:15.500   
    <134>M0:
        192.168.0.1    23/04 17:27:15.500   
    <159>M1: [1]RegOK. NextReg in 2130706400 (31)
        192.168.0.2    23/04 17:27:15.500   
    <134>M0: [pxy]->192.168.0.2:5160(364)
        192.168.0.1    23/04 17:27:15.500   
    <134>M0: [pxy]->192.168.0.2:5160(364)
        192.168.0.1    23/04 17:27:15.500   
    <134>M0:
        192.168.0.1    23/04 17:27:15.500   
    <134>M0:
        192.168.0.1    23/04 17:27:15.500   
    <134>M0: [pxy]->10.128.1.4:5160(463)
        192.168.0.1    23/04 17:27:15.500   
    <134>M0: [pxy]->10.128.1.4:5160(463)
        192.168.0.1    23/04 17:27:15.500   
    <134>M0:
        192.168.0.1    23/04 17:27:15.500   
    <134>M0:
        192.168.0.1    23/04 17:27:15.500   
    <151>M1: [0]SubOK
        192.168.0.2    23/04 17:27:15.500   
    <151>M1: NextSub in 2147483646 (1)
        192.168.0.2    23/04 17:27:15.510   
    <134>M0: [pxy]<<192.168.0.2:5161(426)
        192.168.0.1    23/04 17:27:15.510   
    <134>M0: [pxy]<<192.168.0.2:5161(426)
        192.168.0.1    23/04 17:27:15.510   
    <134>M0:
        192.168.0.1    23/04 17:27:15.510   
    <134>M0:
        192.168.0.1    23/04 17:27:15.510   
    <134>M0: [pxy]->192.168.0.2:5161(363)
        192.168.0.1    23/04 17:27:15.510   
    <134>M0: [pxy]->192.168.0.2:5161(363)
        192.168.0.1    23/04 17:27:15.510   
    <134>M0:
        192.168.0.1    23/04 17:27:15.510   
    <134>M0:
        192.168.0.1    23/04 17:27:15.510   
    <151>M1: [1]SubOK
        192.168.0.2    23/04 17:27:15.510   
    <134>M0: [pxy]->10.128.1.4:5161(463)
        192.168.0.1    23/04 17:27:15.510   
    <151>M1: NextSub in 2147483646 (1)
        192.168.0.2    23/04 17:27:15.510   
    <134>M0: [pxy]->10.128.1.4:5161(463)
        192.168.0.1    23/04 17:27:15.510   
    <134>M0:
        192.168.0.1    23/04 17:27:15.520   
    <134>M0:
        192.168.0.1    23/04 17:27:15.520   
    <134>M0: [pxy]<<192.168.0.2:5160(352)
        192.168.0.1    23/04 17:27:15.520   
    <134>M0: [pxy]<<192.168.0.2:5160(352)
        192.168.0.1    23/04 17:27:15.520   
    <134>M0:
        192.168.0.1    23/04 17:27:15.520   
    <134>M0:
        192.168.0.1    23/04 17:27:15.520   
    <134>M0: [pxy]<<192.168.0.2:5161(352)
        192.168.0.1    23/04 17:27:15.520   
    <134>M0: [pxy]<<192.168.0.2:5161(352)
        192.168.0.1    23/04 17:27:15.520   
    <134>M0:
        192.168.0.1    23/04 17:27:15.520   
    <134>M0:
        192.168.0.1    23/04 17:27:15.520   
    <151>M0: CID:OnHookTx Pol
        192.168.0.1    23/04 17:27:15.720   
    <151>M0: CID:OnHookTx Pol
        192.168.0.1    23/04 17:27:15.720   
    <151>M0: Start DTMF/FSK
        192.168.0.1    23/04 17:27:16.020   
    <151>M0: Start DTMF/FSK
        192.168.0.1    23/04 17:27:16.030   
    <151>M0: CID:DONE
        192.168.0.1    23/04 17:27:16.470   
    <151>M0: CID:DONE
        192.168.0.1    23/04 17:27:16.470   
    <151>M1: CID:OSI
        192.168.0.2    23/04 17:27:17.500   
    <151>M1: CID:OSI
        192.168.0.2    23/04 17:27:17.510   
    <151>M1: CID:OnHookTx Pol
        192.168.0.2    23/04 17:27:17.760   
    <151>M1: CID:OnHookTx Pol
        192.168.0.2    23/04 17:27:17.770   
    <151>M1: Start DTMF/FSK
        192.168.0.2    23/04 17:27:18.060   
    <151>M1: Start DTMF/FSK
        192.168.0.2    23/04 17:27:18.070   
    <151>M1: CID:DONE
        192.168.0.2    23/04 17:27:18.510   
    <151>M1: CID:DONE
        192.168.0.2    23/04 17:27:18.520   
    <159>M0: system request reboot
        192.168.0.1    23/04 17:28:04.277   
    <159>M0: fu:1:7380, 0038 0049 043c 0445 0001
        192.168.0.1    23/04 17:28:07.347   
    <151>M0: IDBG: pppld
        192.168.0.1    23/04 17:28:07.357   
    <159>M0: fu:1:742e, 03e4 05b0 0001
        192.168.0.1    23/04 17:28:07.437   
    <134>M1: System started: [email protected], reboot reason:H0
        192.168.0.2    23/04 17:28:22.570   
    <134>M1: System started: [email protected], reboot reason:H0
        192.168.0.2    23/04 17:28:22.570   
    <143>M1:     subnet mask:    255.255.255.0
        192.168.0.2    23/04 17:28:22.570   
    <143>M1:     gateway ip:    192.168.0.1
        192.168.0.2    23/04 17:28:22.570   
    <143>M1:     dns servers(1):        192.168.0.2    23/04 17:28:22.580   
    <143>M1: 192.168.0.1     192.168.0.2    23/04 17:28:22.580   
    <143>M1: 
        192.168.0.2    23/04 17:28:22.580   
    <159>M0: IDBG: st-0
        192.168.0.1    23/04 17:28:22.690   
    <159>M1: mslink server task up (1)
        192.168.0.2    23/04 17:28:24.560   
    <134>M2: System started: [email protected], reboot reason:H0
        192.168.0.3    23/04 17:28:25.620   
    <134>M2: System started: [email protected], reboot reason:H0
        192.168.0.3    23/04 17:28:25.620   
    <143>M2:     subnet mask:    255.255.255.0
        192.168.0.3    23/04 17:28:25.620   
    <143>M2:     gateway ip:    192.168.0.1
        192.168.0.3    23/04 17:28:25.620   
    <143>M2:     dns servers(1):        192.168.0.3    23/04 17:28:25.630   
    <143>M2: 192.168.0.1     192.168.0.3    23/04 17:28:25.630   
    <143>M2: 
        192.168.0.3    23/04 17:28:25.630   
    <134>M3: System started: [email protected], reboot reason:H0
        192.168.0.4    23/04 17:28:25.630   
    <134>M3: System started: [email protected], reboot reason:H0
        192.168.0.4    23/04 17:28:25.630   
    <143>M3:     subnet mask:    255.255.255.0
        192.168.0.4    23/04 17:28:25.630   
    <143>M3:     gateway ip:    192.168.0.1
        192.168.0.4    23/04 17:28:25.630   
    <143>M3:     dns servers(1):        192.168.0.4    23/04 17:28:25.640   
    <143>M3: 192.168.0.1     192.168.0.4    23/04 17:28:25.640   
    <143>M3: 
        192.168.0.4    23/04 17:28:25.640   
    <159>M2: mslink server task up (2)
        192.168.0.3    23/04 17:28:27.451   
    <159>M3: mslink server task up (3)
        192.168.0.4    23/04 17:28:27.521   
    <159>M1: IDBG: st-0
        192.168.0.2    23/04 17:28:28.221   
    <159>M1: fs:008275:008693:131072
        192.168.0.2    23/04 17:28:28.321   
    <159>M1: fls:af:1:0:0
        192.168.0.2    23/04 17:28:28.331   
    <159>M1: fbr:0:3000:3000:039a9:0002:0001:6.1.12
        192.168.0.2    23/04 17:28:28.331   
    <159>M1: PLKUP: 8192, 2102, 12, 1.5
        192.168.0.2    23/04 17:28:28.351   
    <159>M1: fu:0:39bb, 0003 0001
        192.168.0.2    23/04 17:28:28.511   
    <159>M1: mslink client task (1)  gw=192.168.0.1  ip=192.168.0.2
        192.168.0.2    23/04 17:28:28.541   
    <159>M2: IDBG: st-0
        192.168.0.3    23/04 17:28:29.121   
    <159>M2: fs:008200:008342:131072
        192.168.0.3    23/04 17:28:29.221   
    <159>M2: fls:af:1:0:0
        192.168.0.3    23/04 17:28:29.221   
    <159>M2: fbr:0:3000:3000:035af:0002:0001:6.1.12
        192.168.0.3    23/04 17:28:29.221   
    <159>M2: PLKUP: 8192, 2102, 12, 1.5
        192.168.0.3    23/04 17:28:29.241   
    <159>M0: MSLINK module 1 is at 192.168.0.2
        192.168.0.1    23/04 17:28:29.291   
    <159>M0: MSLINK code module 1: 0(32) sn:0
        192.168.0.1    23/04 17:28:29.341   
    <159>M2: fu:0:35c1, 0003 0001
        192.168.0.3    23/04 17:28:29.401   
    <159>M3: IDBG: st-0
        192.168.0.4    23/04 17:28:30.191   
    <159>M3: fs:008200:008351:131072
        192.168.0.4    23/04 17:28:30.281   
    <159>M3: fls:af:1:0:0
        192.168.0.4    23/04 17:28:30.291   
    <159>M3: fbr:0:3000:3000:0423d:0002:0001:6.1.12
        192.168.0.4    23/04 17:28:30.291   
    <159>M3: PLKUP: 8192, 2102, 12, 1.5
        192.168.0.4    23/04 17:28:30.311   
    <159>M3: fu:0:424f, 0003 0001
        192.168.0.4    23/04 17:28:30.471   
    <159>M2: mslink client task (2)  gw=192.168.0.1  ip=192.168.0.3
        192.168.0.3    23/04 17:28:31.441   
    <159>M0: MSLINK module 2 is at 192.168.0.3
        192.168.0.1    23/04 17:28:32.261   
    <159>M0: MSLINK code module 2: 0(32) sn:0
        192.168.0.1    23/04 17:28:32.461   
    <159>M3: mslink client task (3)  gw=192.168.0.1  ip=192.168.0.4
        192.168.0.4    23/04 17:28:32.511   
    <159>M0: MSLINK module 3 is at 192.168.0.4
        192.168.0.1    23/04 17:28:33.431   
    <159>M0: MSLINK code module 3: 0(32) sn:0
        192.168.0.1    23/04 17:28:34.211   
    <159>M0: fs:025278:025278:131072
        192.168.0.1    23/04 17:28:37.382   
    <159>M0: fls:af:1:0:0
        192.168.0.1    23/04 17:28:37.382   
    <159>M0: fbr:1:3000:3000:1742e:0004:0005:6.1.12
        192.168.0.1    23/04 17:28:37.382   
    <159>M0: fhs:01:0:0001:upg:app:0:5.1.10
        192.168.0.1    23/04 17:28:37.382   
    <159>M0: fhs:02:0:0002:upg:app:1:5.1.10
        192.168.0.1    23/04 17:28:37.422   
    <159>M0: fhs:03:0:0003:upg:app:2:5.1.10
        192.168.0.1    23/04 17:28:37.482   
    <159>M0: fhs:04:0:0004:upg:app:0:6.1.12
        192.168.0.1    23/04 17:28:37.542   
    <159>M0: fhs:05:0:0005:upg:app:1:6.1.12
        192.168.0.1    23/04 17:28:37.592   
    <159>M0: fhs:06:0:0006:upg:app:2:6.1.12
        192.168.0.1    23/04 17:28:37.632   
    <159>M0: PLKUP: 8192, 2102, 12, 1.5
        192.168.0.1    23/04 17:28:37.692   
    <159>M0: fu:1:7440, 0003 0001
        192.168.0.1    23/04 17:28:38.182   
    <159>M0: mslink  P:12378  V:53243
        192.168.0.1    23/04 17:28:50.064   
    <159>M1: CC_init
        192.168.0.2    23/04 17:28:52.534   
    <134>M1: SLIC is si3215
        192.168.0.2    23/04 17:28:52.614   
    <134>M1: SLIC is si3215
        192.168.0.2    23/04 17:28:52.624   
    <159>M1: IDBG[0]:4
        192.168.0.2    23/04 17:28:53.124   
    <159>M1: IDBG[1]:3
        192.168.0.2    23/04 17:28:53.124   
    <159>M2: CC_init
        192.168.0.3    23/04 17:28:53.434   
    <134>M2: SLIC is si3215
        192.168.0.3    23/04 17:28:53.514   
    <134>M2: SLIC is si3215
        192.168.0.3    23/04 17:28:53.524   
    <159>M2: IDBG[0]:4
        192.168.0.3    23/04 17:28:54.024   
    <159>M2: IDBG[1]:3
        192.168.0.3    23/04 17:28:54.024   
    <134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.2    23/04 17:28:54.254   
    <134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.2    23/04 17:28:54.254   
    <134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.2    23/04 17:28:54.254   
    <134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
        192.168.0.2    23/04 17:28:54.264   
    <159>M3: CC_init
        192.168.0.4    23/04 17:28:54.504   
    <134>M3: SLIC is si3215
        192.168.0.4    23/04 17:28:54.584   
    <134>M3: SLIC is si3215
        192.168.0.4    23/04 17:28:54.594   
    <159>M3: IDBG[0]:4
        192.168.0.4    23/04 17:28:55.084   
    <159>M3: IDBG[1]:3
        192.168.0.4    23/04 17:28:55.084   
    <159>M0: CC_init
        192.168.0.1    23/04 17:28:55.965   
    <134>M0: SLIC is si3215
        192.168.0.1    23/04 17:28:56.525   
    <134>M0: SLIC is si3215
        192.168.0.1    23/04 17:28:56.525   
    <159>M0: fu:1:7455, 03e4 05b0 0001
        192.168.0.1    23/04 17:28:56.605   
    <159>M0: IDBG[0]:6
        192.168.0.1    23/04 17:28:57.025   
    <159>M0: IDBG[1]:4
        192.168.0.1    23/04 17:28:57.025   
    <134>M0: System started: [email protected], reboot reason:C200
        192.168.0.1    23/04 17:29:23.348   
    <134>M0: System started: [email protected], reboot reason:C200
        192.168.0.1    23/04 17:29:23.348   
    <143>M0:     subnet mask:    255.255.255.255
        192.168.0.1    23/04 17:29:23.348   
    <143>M0:     gateway ip:    10.128.1.254
        192.168.0.1    23/04 17:29:23.358   
    <143>M0:     dns servers(2):        192.168.0.1    23/04 17:29:23.358   
    <143>M0: 4.2.2.1     192.168.0.1    23/04 17:29:23.358   
    <143>M0: 4.2.2.2     192.168.0.1  

  • 802.1x authentication on Macbooks running Lion..

    Hi Guys,
    I was wondering if anyone has experienced problems with 802.1x authentication on their Cisco Wifi network using Macbook Pro/Airs running Lion.
    We have..
    2x Controllers with WiSMs running 7.0.116.0
    A mixture of 1131 and 1142 APs..  ( APs mainly in HREAP mode with some APs located on the same local network as the Controller in Local Mode )
    Macbook Airs/ Pro running Lion
    The symptoms we are experiencing are very similar to those described in this thread.. https://supportforums.cisco.com/message/3485552
    In summary, we are finding that when our MacBooks are coming out of sleep/standby or roaming between APs, the devices get stuck during the 802.1x authentication process and will either get the self assigned 169 address or continuously try to authenticate.
    This can occasionally be solved by turning the wifi interface off and on or manually stopping and starting the 802.1x process on the Mac
    From reading various online forums, we have tried the following to resolve this..
    - Disabled WPA across our wifi network as we don't use it anymore.. We now just use WPA2 with AES and Dot1x authentication.
    - Disabled Client Load Balancing on the SSID configuration… this does not seem to have made things any better or worse although we are seeing more Load Profile threshold notification alerts for some of our APs which are used heavily.
    - The 802.1x time out is currently set at 20secs.
    - Some APs which are in Local mode ( due to them being on the same local network as our wifi controllers ) have been changed to HREAP mode and assigned a static IP address.. We found that this was required at our spoke sites where we were originally experiencing issues with our old Windows based devices.. Incidentally, we have not experienced any of these delayed authentication issues with our Window laptops, all our problems seem to be with our MacBooks running Lion..
    As I mentioned earlier, there seems to be many discussions online regarding problems with the Lion OS and 802.1x authentication..
    Has anyone experienced these problems in the past on there Cisco Aps and successfully managed to resolve it.. ?
    Any ideas would be appreciated..
    Many thanks.
    Jon.

    Ran across this old post while researching this same issue. For us, the problem appears to be with the Mac's trying to request an IPv6 address if set to Automatically or Link-local only for Configure IPv6 under the TCP/IP tab. When we changed this to Manually and set a manual link local address, the problem went away and could reconnect after roaming between APs or coming out of sleep/standby.
    Enjoy,
    Wayne 
    UPDATE 1: This 'fix' did not solve the issue. After a day, we're still seeing the problem. 
    UPDATE 2: Found the solution to my problem. It was the cert chain of trust and CRL lookup. The link below describes the problem, but basically the Mac's were unable to check the certs and causing a time out. No network = no CRL lookup = no network......
    http://support.apple.com/kb/TS5258?viewlocale=en_US&locale=en_US

  • Licence for ASA5505?

    Hi everybody,
    My question, after roaming the internet and cisco page,is:
    Does ASA5505 comes with VPN SSL licence or do you need to purchase it? My guess is that you do need to buy it!
    Can I purchase VPN SSL licence for Cisco 1941 ISR G2 router and then after my company upgrades its network infrastructure and buys ASA's, transfer those licences on to ASA's? We are talking about 3 router on different locations, hence there will also be 3 ASA's when the time comes.
    Is there a link somewhere where I can see prices of all licences?
    Hope you can help me
    Thanks a lot!

    Hello;
    No, there is no way to transfer the license from a router to an ASA.
    The ASA has a license for 2 clients to connect via SSL (Just for you to test it out).
    The pricing list is not posted on Cisco, you can contact a Vendor such as CDW or Cisco directly to get you to a partner that can assist you.
    Mike.

  • Fluxbox dies when starting some applications

    I instaled fluxbox and now I can start fluxbox using startx. I also generated menu using "fluxbox-generate_menu" but now as soon as I start applications like firefox, rox, opera, fluxbox dies and leaves me in console with differnt error messages for different clients and that the app has lost connection with xserver. However, few applications like aterm, gmplayer, starts up fine.

    For Christ's sake, then remove this version from the stable repo... I installed Arch yesterday after roaming in the Vista/Ubuntu world for a year or so - thought of getting back to fluxbox and the locale causes random Xserver shutdowns And pretty please don't be a troll with:
    1. change your locale
    2. use another wm

  • First bill from AT&T

    Hi all, I was wondering what the final cost of the phone bill would be if one selects the $39.99 voice plan along with the iPhone Data plan? I just was hit with a bill of almost $80! Is this normal? I was well within the 450 daytime minutes and so there are no extra charges on my plan. Does almost $20 of taxes seem right?

    Sounds like your activation fee might be in that bill also. I have the 900 min/month plan with the RAZR and I was charged about $85 to $89 per month with phone insurance and some variation in text and data. I check the ball game scores every so often. I haven't gotten my first Iphone bill from them yet but I expect it to be about $105 and I expect my rolling block of 3500 rollover minutes to remain secure. I might invest the extra $25.00 month to the international plan since I've been burned in Canada a few times roaming on Rogers network after roaming in Canada it was not unusual for my bill to exceed $250 at times.

  • Iphone now says roaming after ios 7.1 update

    After updating our phones to ios 7.1 my wife and I now see roaming on our iPhones (5 and 5s). We had full Verizon LTE coverage.
    Called verizon and there are no issues in our area. Anyone have any ideas?
    TIA

    Hey there nixxon2000,
    It sounds like you are unable to connect to your LTE connection on the Verizon network. I recommend these troubleshooting steps from the article named:
    iPhone: Troubleshooting a cellular data connection
    http://support.apple.com/kb/ts3780
    Toggle airplane mode: Tap Settings, turn airplane mode on, wait three seconds, and then turn off again.
    Restart your iPhone.
    Make sure that your software is up to date:
    Check for a Carrier Settings Update: Tap Settings > General > About.
    Check for an iOS Software Update: Tap Settings > General > Software Update.
    Note: Some updates may require a Wi-Fi connection.
    Remove the SIM Card and reinsert it. Allow the iPhone to acquire the network again.
    If your SIM card has SIM PIN enabled, try turning it off: Tap Settings > Phone > SIM PIN.
    Try another location. If a different location works, but the original location still doesn't, contact your carrier to report the issue.
    Reset network settings: Tap Settings > General > Reset > Reset Network Settings.
    Restore the iPhone as new.
    Contact your carrier to:
    Verify that the iPhone is properly set up on the account with the appropriate, current data plan.
    Verify that there are no account-related blocks.
    Find out if there are specific error messages in the carrier logs that could help determine why the issue is occurring.
    If none of the above steps resolves the issue, contact your carrier, make an appointment at an Apple Retail Store, or contact AppleCare to troubleshoot further.
    Thank you for using Apple Support Communities.
    Take care,
    Sterling

Maybe you are looking for

  • Error in Transport the info object

    Dear all, i am trying to transport  the info object 0CM_CTAR during transpot i am getting the error as Characteristic 0CM_CTAR: Unit 0UNIT_DIM no allowed in compounding but i checked in development i  not got any error but when i am trasport iam gett

  • Bash-completion for archlinux (ready for testing)

    EDIT (20031013): new url & version 1.0 is out Hello all, I've created a bash-completion script for AL. Get it from : http://www.kegep.tuc.gr/~manolis/archli - ion.script Then : pacman -S bash-completion copy my script as /etc/bash_completion.d/archli

  • MW 2.08: Unable to create a Project in the MW after creating a customer

    error from Apache logs for this issue: Ranga: [Thu Dec 27 23:49:15 2007] [error] [client 10.200.200.41] [ecid: 1198779553:192.168.5.14:23842:0:19,0] mod_plsql: /pls/EOF/Eof_Manage_Instance.insert_record HTTP-404 ORA-29541: class MW.oracle/support/mw/

  • C Wrappering

    To all... I have never done any C Wrappering so please excuse the ignorance of this question. I had always thought of this as a way to get a C function that I had written into Forte so that it could be called in Tool code. I was recently presented wi

  • .SWF File With Unwanted Border

    I've designed a website where there is a flash banner playing near the top.  I inserted it into the correct area, but for some unknown reason, there's a white border surrounding it.  I turned off the borders at the bottom control thing, but now inste