Peap client timeout

We implement PEAP and it takes quit a long time for clients to complete authentication. from the debug: "debug dot11 aaa authenticator state−machine". I get: " dot11_auth_dot1x_run_rfsm: Executing Action(CLIENT_WAIT,TIMEOUT)". The default timeout is 30 seconds, in Cisco documents it is stated that this value can be changed. How can I change it to say 120 seconds, I was unable to do it!!!
Thanks

The debug message you referenced is an indication that the client is not responding. In my experience, if the client doesn't respond in 30 seconds, it probably isn't going to respond at all. The only exception that I've seen is when the client is waiting for user input (username/password).
Usually this type of issue is a driver, firmware or operating system issue. I usually check for updated drivers, and assuming that you are running a Windows OS, check for hotfixes or other patches.
If you want to change this parameter, I believe that it actually needs to be set in your RADIUS server. There is a parameter that can be set in IOS but that is only used if the server does not provide a timeout attribute.
Kent.

Similar Messages

Hi, I am using HP11 and iPlanet web server. When trying to upload files over HTTP using FORM ENCTYPE="multipart/form-data" that are bigger than a few Kilobytes i get a 408 error. (client timeout).

Hi, I am using HP11 and iPlanet web server. When trying to upload files over HTTP using FORM ENCTYPE="multipart/form-data" that are bigger than a few Kilobytes i get a 408 error. (client timeout). It is as if the server has decided that the client has timed out during the file upload. The default setting is 30 seconds for AcceptTimeout in the magnus.conf file. This should be ample to get the file across, even increasing this to 2 minutes just produces the same error after 2 minutes. Any help appreciated. Apologies if this is not the correct forum for this, I couldn't see one for iPlanet and Web, many thanks, Kieran.

Hi,
You didnt mention which version of IWS. follow these steps.
(1)Goto Web Server Administration Server, select the server you want to manage.
(2)Select Preference >> Perfomance Tuning.
(3)set HTTP Persistent Connection Timeout to your choice (eg 180 sec for three minutes)
(4) Apply changes and restart the server.
*Setting the timeout to a lower value, however, may prevent the transfer of large files as timeout does not refer to the time that the connection has been idle. For example, if you are using a 2400 baud modem, and the request timeout is set to 180 seconds, then the maximum file size that can be transferred before the connection is closed is 432000 bits (2400 multiplied by 180)
Regards
T.Raghulan
[email protected]

Web service client timeout

Hi,
I'm trying to set a timeout on my web service client. But its not working. Your tutorials do not seem to address this.
I am using weblogic 10.3.2, with Java 1.6.
============
Properties propSys = System.getProperties();
propSys.put( "weblogic.webservice.UseWebLogicURLStreamHandler", "true" );
Stub stub = (Stub)portObject;
BindingInfo bindingInfo = (weblogic.webservice.binding.BindingInfo)stub._getProperty("weblogic.webservice.bindinginfo");
bindingInfo.setTimeout(1);
Iterator itr = stub._getPropertyNames();
while (itr.hasNext()){
Object element = itr.next();
log("\n properties that can be set: "+element);
stub._setProperty("weblogic.webservice.rpc.timeoutsecs","1");
===========
I've also tried setting the transaction-timeout and the remove-client-timeout in the weblogic-ear-jar.xml.
===========
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>ExternalEntryEJB</ejb-name>
<transaction-descriptor>
<trans-timeout-seconds>1</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>ExternalEntry</jndi-name>
<remote-client-timeout>1</remote-client-timeout>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>InternalEJB</ejb-name>
<local-jndi-name>Internal</local-jndi-name>
<enable-call-by-reference>True</enable-call-by-reference>
<remote-client-timeout>1</remote-client-timeout>
<transaction-descriptor>
<trans-timeout-seconds>1</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
===========
in case it matters, I am using weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask as the clientgen task in my build.xml
============
<clientgen autotype="False" ear="${dist}/${app.earname}" warName="${servlet.warname}" packageName="MyPackage.webservices.client"
keepgenerated="False" useServerTypes="True" clientJar="${dist}/MyAppClient.jar">
<classpath refid="build.classpath.builddir"/>
</clientgen>
============
I am testing by putting a Thread.sleep(75000) in the method which is called in the internal EJB. But the method runs to completion and returns the reply object after 90 seconds or so (it normally takes about 12 seconds), but does not timeout.
I've been told that because it is a web services client, the remote-client-timeout will be ineffective. I've also been told that because the EJBs run in the same JVM, the transaction-timeout will be ineffective. Is this so?
Thanks,
Walter

Can you change the clientgen task to weblogic.wsee.tools.anttasks.ClientGenTask this is for jax-rpc 1.1.
<taskdef name="clientgen"
classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
((Stub)port)._setProperty(weblogic.wsee.transport.connection.timeout,2);
((Stub)port)._setProperty(weblogic.wsee.transport.read.timeoutt,2);
Hope that helps.

Clients timeout on DHCP lease with Aironet 1141

Hello
I have an interesting problem that I can't find a solution for.
Backround info:
I'm setting up a Cisco Aironet 1141 (standalone mode, AP) to handle wireless traffic in the office. It gives out 2 mbssids, one of which authenticates domain users through a RADIUS server and places them in an appropriate VLAN (RADIUS options 64, 65, and 81). The other is a guest ssid that uses WPA-PSK and places users in the restricted guest VLAN. Physically, the AP is connected to a 3750 PoE Catalyst, to which RADIUS and DHCP servers are also connected. AP, SSIDs, RADIUS and EAP authentication all work. The configuration given below is a working configuration. People do get authenticated and do get placed in the appropriate vlan.
The problem is that, once authenticated, the "Obtaining IP Address" phase on the client hangs and most clients timeout without getting an IP address. Given that the DHCP server is on the same switch and a test simple ASUS Wi-Fi IP gives out the same scenario (except the multiple VLAN) at the speed of light, I don't think that it's a problem with the network connections between clients and the DHCP server.
After reading some topics here, I realized that probably other communication will be extremely slow, as well, but haven't tested that for sure.
Clients are all non-Cisco - smartphones, notebooks, etc. Most of them are 802.11G, not N.
Configuration is attached below.
Does anyone have any ideas?

Sure, possibly relevant parts:
errdisable recovery cause udld
errdisable recovery cause bpduguard
errdisable recovery cause security-violation
errdisable recovery cause channel-misconfig (STP)
errdisable recovery cause pagp-flap
errdisable recovery cause dtp-flap
errdisable recovery cause link-flap
errdisable recovery cause gbic-invalid
errdisable recovery cause l2ptguard
errdisable recovery cause psecure-violation
errdisable recovery cause dhcp-rate-limit
errdisable recovery cause vmps
errdisable recovery cause storm-control
errdisable recovery cause arp-inspection
spanning-tree mode rapid-pvst
spanning-tree loopguard default
spanning-tree portfast bpduguard default
spanning-tree extend system-id
vlan internal allocation policy ascending
ip ssh time-out 60
ip ssh authentication-retries 5
ip ssh logging events
ip ssh version 2
interface GigabitEthernet1/0/1
description Gi1/0/1 to CAT-CORE
switchport trunk encapsulation dot1q
switchport mode trunk
interface GigabitEthernet1/0/4
description Gi1/0/4 to RADIUS_serv
switchport access vlan 240
switchport mode access
spanning-tree portfast
spanning-tree bpdufilter enable
spanning-tree bpduguard enable
interface GigabitEthernet1/0/8
description Gi1/0/8 to DHCP_serv
switchport access vlan 240
switchport mode access
spanning-tree portfast
spanning-tree bpdufilter enable
spanning-tree bpduguard enable
interface GigabitEthernet1/0/11
description Aironet 1141 AIRONET-MO-1
switchport trunk encapsulation dot1q
switchport trunk native vlan 240
switchport trunk allowed vlan 240-246,248,249
switchport mode trunk
interface Vlan240
description Admin_Vlan
ip address 192.168.240.244 255.255.255.0
ip default-gateway 192.168.240.1
ip classless
no ip http server
ip http secure-server

PEAP clients stuck in the 8021X_REQD state

Hi,
I've got complaining for lots of PEAP clients not connecting to wireless network. Everything was working fine before. I logged into WLC and found out these clients are associated but stuck in the 8021X_REQD state. I checked our Radius server and couldn't find the failed log. The below message shows the debug for a client 00:0b:6b:24:66:55 and the attachment is the client info shown on the WLC. Please help. Thanks.
(vau-cr-wlc4402-1) >debug client 00:0b:6b:24:66:55
(vau-cr-wlc4402-1) >Mon Aug 8 15:40:53 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
Mon Aug 8 15:40:53 2011: 00:0b:6b:24:66:55 Retransmit 1 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 Association received from mobile on AP 00:1c:57:8b:34:e0
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 STA - rates (8): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 STA - rates (12): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 Processing RSN IE type 48, length 20 for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 Received RSN IE with 0 PMKIDs from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Initializing policy
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Change state to AUTHCHECK (2) last state 8021X_REQD (3)
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 10.115.148.80 AUTHCHECK (2) Change state to 8021X_REQD (3) last state 8021X_REQD (3)
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 00:1c:57:8b:34:e0
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 apfPemAddUser2 (apf_policy.c:209) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:34:e0 from Associated to Associated
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 Stopping deletion of Mobile Station: (callerId: 48)
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 Sending Assoc Response to station on BSSID 00:1c:57:8b:34:e0 (status 0)
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 apfProcessAssocReq (apf_80211.c:3838) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:34:e0 from Associated to Associated
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Connecting state
Mon Aug 8 15:41:23 2011: 00:0b:6b:24:66:55 Sending EAP-Request/Identity to mobile 00:0b:6b:24:66:55 (EAP Id 1)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL START from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Connecting state
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP-Request/Identity to mobile 00:0b:6b:24:66:55 (EAP Id 2)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received Identity Response (count=2) from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 EAP State update from Connecting to Authenticating for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Authenticating state
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=204) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 WARNING: updated EAP-Identifer 2 ===> 204 for STA 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 204)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 204, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=205) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 205)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 205, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=206) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 206)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 206, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=207) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 207)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 207, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=208) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 208)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 208, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=209) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 209)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 209, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=210) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 210)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 210, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=211) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 211)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 211, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=212) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 212)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 212, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=213) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 213)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 213, EAP Type 25)
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=214) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:41:34 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 214)
Mon Aug 8 15:42:04 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
Mon Aug 8 15:42:04 2011: 00:0b:6b:24:66:55 Retransmit 1 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Association received from mobile on AP 00:1c:57:8b:0d:40
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 STA - rates (8): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 STA - rates (12): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing RSN IE type 48, length 20 for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received RSN IE with 0 PMKIDs from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Deleted mobile LWAPP rule on AP [00:1c:57:8b:34:e0]
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Updated location for station old AP 00:00:00:00:00:00-0, new AP 00:1c:57:8b:0d:40-0
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Initializing policy
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Change state to AUTHCHECK (2) last state 8021X_REQD (3)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 AUTHCHECK (2) Change state to 8021X_REQD (3) last state 8021X_REQD (3)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 00:1c:57:8b:0d:40
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 apfPemAddUser2 (apf_policy.c:209) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:0d:40 from Associated to Associated
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Stopping deletion of Mobile Station: (callerId: 48)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending Assoc Response to station on BSSID 00:1c:57:8b:0d:40 (status 0)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 apfProcessAssocReq (apf_80211.c:3838) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:0d:40 from Associated to Associated
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Connecting state
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP-Request/Identity to mobile 00:0b:6b:24:66:55 (EAP Id 1)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received Identity Response (count=1) from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 EAP State update from Connecting to Authenticating for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Authenticating state
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=153) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 WARNING: updated EAP-Identifer 1 ===> 153 for STA 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 153)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 153, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=154) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 154)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response packet with mismatching id (currentid=154, eapid=153) from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 154, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=155) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 155)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 155, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=156) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 156)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 156, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=157) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 157)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 157, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=158) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 158)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 158, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=159) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 159)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 159, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=160) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 160)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 160, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=161) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 161)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 161, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=162) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 162)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 162, EAP Type 25)
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=163) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:42:33 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 163)
Mon Aug 8 15:43:03 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
Mon Aug 8 15:43:03 2011: 00:0b:6b:24:66:55 Retransmit 1 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:33 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
Mon Aug 8 15:43:33 2011: 00:0b:6b:24:66:55 Retransmit 2 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Association received from mobile on AP 00:1c:57:8b:0d:40
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 STA - rates (8): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 STA - rates (12): 130 132 139 150 140 18 152 36 176 72 96 108 0 0 0 0
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing RSN IE type 48, length 20 for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received RSN IE with 0 PMKIDs from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Initializing policy
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Change state to AUTHCHECK (2) last state 8021X_REQD (3)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 10.115.148.80 AUTHCHECK (2) Change state to 8021X_REQD (3) last state 8021X_REQD (3)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 10.115.148.80 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 00:1c:57:8b:0d:40
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 apfPemAddUser2 (apf_policy.c:209) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:0d:40 from Associated to Associated
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Stopping deletion of Mobile Station: (callerId: 48)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending Assoc Response to station on BSSID 00:1c:57:8b:0d:40 (status 0)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 apfProcessAssocReq (apf_80211.c:3838) Changing state for mobile 00:0b:6b:24:66:55 on AP 00:1c:57:8b:0d:40 from Associated to Associated
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Connecting state
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP-Request/Identity to mobile 00:0b:6b:24:66:55 (EAP Id 1)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received Identity Response (count=1) from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 EAP State update from Connecting to Authenticating for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 dot1x - moving mobile 00:0b:6b:24:66:55 into Authenticating state
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=174) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 WARNING: updated EAP-Identifer 1 ===> 174 for STA 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 174)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 174, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=175) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 175)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 175, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=176) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 176)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 176, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=177) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 177)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 177, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=178) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 178)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 178, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=179) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 179)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 179, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=180) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 180)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 180, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=181) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 181)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 181, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=182) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 182)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 182, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=183) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 183)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAPOL EAPPKT from mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Received EAP Response from mobile 00:0b:6b:24:66:55 (EAP Id 183, EAP Type 25)
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Response state for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Processing Access-Challenge for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Entering Backend Auth Req state (id=184) for mobile 00:0b:6b:24:66:55
Mon Aug 8 15:43:37 2011: 00:0b:6b:24:66:55 Sending EAP Request from AAA to mobile 00:0b:6b:24:66:55 (EAP Id 184)
Mon Aug 8 15:44:07 2011: 00:0b:6b:24:66:55 802.1x 'timeoutEvt' Timer expired for station 00:0b:6b:24:66:55
Mon Aug 8 15:44:07 2011: 00:0b:6b:24:66:55 Retransmit 1 of EAP-Request (length 127) for mobile 00:0b:6b:24:66:55
(vau-cr-wlc4402-1) >debug disable-all

Hi,
Check the username/password database on the AD if ur using one or check if the AD is integrated correctly with the IAS or the ACS.
Issue either on the IAS or ACS (RADIUS server) , the WLC is waiting for the response from the RADIUS.
Regards
Surendra

Phonefactor with RRAS(Windows Server 2003) - VPN client timeout after 20 seconds -- too fast!

[Note that I have previously posted this question on Experts Exchange... but have not found a solution yet].
We are a small business and would like to switch to two-factor authentication for VPN connections. We spent nearly a year helping Barracuda debug their small business VPN appliance and finally they took their boxes back and gave us back our money - they
just couldn't get file sharing to work consistently with some new firmware they had to install due to a patent case.
So... now we are trying Phonefactor.
Our VPN setup is RRAS on a Windows Server 2003 domain controller.
We have installed Phonefactor, enabled it as a Radius server, and configured RRAS to point to Phonefactor for Radius authentication. We configured phonefactor to send text messages for authentication, as we figured that would be less disruptive than a phone
call.
It all works except... the timeout for VPN clients is only 20 seconds! By the time we receive the text message on a cell phone, sometimes there is only 5 or 6 seconds to get the six digit code typed into a reply on the cell phone... and unless we are really
nimble, that is frequently not enough time!
When the VPN client times out, it gives an Error 718 "The connection was terminated because the remote computer did not respond in a timely manner."
How can we increase the timeout on the VPN clients, so we can more reliably enter the authentication code in a reply back to phonefactor?
Things we have tried:
1) Connecting (PPTP) from different Windows clients to see if we get different timeout limits. So far we have tried several Windows 7 boxes and a Windows Server 2003 as the client, but in all cases the timeout is 20 seconds.
2) On the windows clients: Searching through the PPTP client settings to see if there is one labeled "connection timeout". So far we have found nothing.
3) On the windows 2003 server: Modifying the RRAS Radius Server time-out to be 30 seconds, 60 seconds, 300 seconds. We've tried restarting RRAS after these changes, but the client connection timeout is still 20 seconds.
4) In the phonefactor configuration: Searching through the radius server settings to see if there is one labeled "connection timeout". So far we have found nothing.
5) Using NTRadPing to connect directly to the phonefactor radius server. With NTRadPing we were able to wait more than 60 seconds without a timeout from phonefactor. So we don't *think* at this point that the issue is within phonefactor.
6) We have asked phonefactor support, but their response is "hmmm... good question, we don't know, that sounds like a problem with your vpn client". And they could well be correct.
7) Search the web for how to increase either the stock windows VPN client timeout, or the RRAS radius authentication timeout. No luck so far.
8) Try this registry hack:
http://windowsitpro.com/networking/solving-ras-718-error. Didn't help.
Any ideas?
thanks!

Hi fdc2005,
Thanks for the post.
However, generally, we first type User Name, Password, then click connect to establish the VPN connection. Such as:
Therefore, I have a little confusion about the timeout you mentioned. Would you please provide us more details.
Regarding error 718, please check if the following could help:
If you have a third-party VPN server which does not support MS-CHAPv2 as an authentication method and supports only MS-CHAPv1, you will need to use either CHAP or PAP to connect from the Windows Vista VPN client until the server you use starts supporting MS-CHAPv2.
Steps to follow for resolution:
(1) Check if the Routing and Remote Access Server (RRAS) is configured to allow connections with MS-CHAPv2
(2) Check if the RADIUS server policy supports MSCHAPv2 (This step is needed if you control access to clients using Remote Access Policies on the IAS/NPS server)
Quote from:
Troubleshooting Vista VPN problems.
Hope this helps.
Jeremy Wu
TechNet Community Support

Servlet/JSP client timeout handling

Hi,
Is it possible to detect a client timeout in a servlet / jsp ?
Example,
I go to a page that is displayed by a servlet. I put Thread.sleep in the servlet to simulate the request processing time.
Assuming now I close the browser (or any other client) and the servlet tries to write the response, will it throw any exceptions ?
What can I do to check the client status before trying to write the response back ?
Thanks
Mandar

Hi,
The servlet did not throw any exception when I tried to write the response back after sleep.
Code is as shown below
try{
Thread.sleep(60000);
catch (InterruptedException ie){
logger.error("Someone interrupted my sleep",ie);
logger.info("End sleep for 1 minute");
try{
response.getOutputStream().write(2);
response.flushBuffer();
catch (IOException ioe){
logger.error("IOException occured",ioe);
throw ioe;
}

How to handle received data after client timeout

I believe this is a common question and sorry if it is asked and answered before. I didn't find the answer.
I have a client/server app. there mainly two threads. one is to handle my regular GUI command, and the other one is to check if the server is still alive by sending ping command every 5 seconds. I set the client timeout 10 seconds. My problem is as the following:
1. client sends a command CMD
2. Client timeout after 10 seconds
3. The background thread sends a Ping command
4. Client received the response for the first command CMD
5. then the client assume the response is for the Ping CMD and mismatched!
I am thinking about using the following ways to handle this issue, wondering if anyone could let me know if they are ok and which one is better. OR there could be a better solution altogether.
Method 1 - if client time out, close everything, consider server is dead. try to re-establish connection again
method 2 - attach a ticket to each command and response, so that they can be matched regardless the order it is receive.
Thank you very much!
livz

Thanks for all the replies.
I use the ping to check if the server is connected and a lot of my GUI functions are enabled/diabled based on whether the server is in presence. for example, certain buttons or operations are disabled if the server is disconnected. I didn't find a better way to handle this. Please advice if there is anything better.
10 seconds was randomly chosen based on experience. It works most of the time but sometimes it times out.
again, thanks a lot for any advice!
livz

WebLogic Builder remote-client-timeout

Just wondering if anyone has encountered this before.
After using WebLogic Builder to make and save changes to an EAR file the weblogic-ejb-jar.xml file is updated to include the remote-client-timeout tag. This tag causes warning messages in the weblogic console.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>HelloWorldEJB</ejb-name>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>test.HelloWorldHome</jndi-name>
<remote-client-timeout>0</remote-client-timeout>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Warning Messages
<Nov 2, 2005 4:46:22 PM PST> <Warning> <EJB> <BEA-014009> <Warning: EJB HelloWorldEJB, has the remote-client-timeout set to 0 secs. This timeout specifies a rmi level timeout in seconds for remote clients that call the home and remote methods of the ejb. The method call(s) timeout on the client side after the specified number of seconds. The server will continue to process the request(s) and may change the state. The rmi level timeout shall be set by the container only for non-transactional methods (i.e, method with tx-attributes of Never or Not-Supported). Please ensure that the parameter is used only for methods that are idempotent in nature.>

I think the tool sets the default value for this flag. The default value
should not have any effect. However, I would expect the tool (weblogic
builder) not to insert this element in the descriptor.
More details on this setting can be found here -
http://e-docs.bea.com/wls/docs81/rmi/rmi_api.html#rmi_timeout
--Sathish
<Colin Yeung> wrote in message news:[email protected]..
Just wondering if anyone has encountered this before.
After using WebLogic Builder to make and save changes to an EAR file the
weblogic-ejb-jar.xml file is updated to include the remote-client-timeout
tag. This tag causes warning messages in the weblogic console.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>HelloWorldEJB</ejb-name>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>test.HelloWorldHome</jndi-name>
<remote-client-timeout>0</remote-client-timeout>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Warning Messages
<Nov 2, 2005 4:46:22 PM PST> <Warning> <EJB> <BEA-014009> <Warning: EJB
HelloWorldEJB, has the remote-client-timeout set to 0 secs. This timeout
specifies a rmi level timeout in seconds for remote clients that call the
home and remote methods of the ejb. The method call(s) timeout on the
client side after the specified number of seconds. The server will
continue to process the request(s) and may change the state. The rmi level
timeout shall be set by the container only for non-transactional methods
(i.e,
method with tx-attributes of Never or Not-Supported). Please ensure that
the parameter is used only for methods that are idempotent in nature.>

EAIObjMgr misconfigured generates client timeout

Sometimes on my production system, the EAI OM is spending too much time in the process "SessHello" (01min 46sec in the following exemple).
At the client side, on the sweapp, this delay it is too long, it causes a socket timeout :
SisnTcpIp SisnSockError 1 000001ec4ef420ec:0 2011-12-23 10:39:47 5920: [TCPIP-client] recv() failed for sd=2596 (err=10060 | Connection timeout.)
When the EAI OM is ready to process, it detects that the client has timeout, so the connection closes prematurely.
MessageFlow MsgFlowDetail 4 0002e7764ef420ec:0 2011-12-23 10:38:01 21892: ProcessSessHello(1) Sent Session Hello Acknowledge for task 20972415, pConn = 0x132c40c0, pErrStack = 0x0d5a1d40
MessageFlow MsgFlowDetail 4 0002e7764ef420ec:0 2011-12-23 10:39:47 21892: ProcessMessage() worker will process 0x1492d948, pErrStack = 0x0d5a1d40
TaskEvents SessionClose 3 0002e7764ef420ec:0 2011-12-23 10:39:47 Client closed session (taskId = 20972415)
The two redundant EAI OM are configured with the following parameters :
MaxTasks: 800
MinMTServers: 2
MaxMTServers: 5
SessPerSisnConn: 5
ConnIdleTime: -1
Thanks for any help you can.

There are various problems causing timeout of the client "[TCPIP-client] recv() failed", so I made a mistake :
- The first one : delay when opening a new task on EAI OM causing client timeout was resolved with MTServers parameters.
- The second one : client timeout after load balancing delay was resolved by setting corrects timeouts on OM/SWSE/Alteon.
Now I have a third problem with Sisnapi open session timeout (SBL-SSM-00005) but the original problem is solved.
Thank you!

Client timeout webservice

Hi,
how can I setting client timeout? I have a invocation with two-way authentication!
Please, help me!!

Hi Tanja,
Need more info on what you are doing please. Are you using a consumer proxy?
If you're using a consumer proxy then when you create your logical port, in the port config (under messaging tab) there are timeout setting options.
Regards, Trevor

RMI - How to set a client timeout?

Hey folks,
please don't crucify me, but i googled for "rmi client timeout" and i only found confusing and / or really dated information.
Could somebody enlighten me on how to set a timeout for an RMI-client?
Even an RTFM would be fine, but which?

Hi,
thanks for your insistence.....:-)
ejp wrote:
1. Are you using rmic? UnicastRemoteObject? or some JBoss API?Ehm, for the client?
The client's sourcecode for connecting to the Jboss-Server / my EJB-application is:
Hashtable<String, String> props = new Hashtable<String, String>();
props.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory");
props.put(Context.PROVIDER_URL,"jnp://" + "myhost");
props.put(Context.SECURITY_PRINCIPAL, "myuser");
props.put(Context.SECURITY_CREDENTIALS, "mypassword");
Context ctx = new InitialContext(props);
// get RMI stub
ISendCommand sendCommand = (ISendCommand) ctx.lookup(myjndiname);
String result = sendCommand.sendCommand(myArgs);So i think this corrensponds to "UnicastRemoteObject" from your enumeration?
ejp wrote:
2. How do you know JBoss terminates the connection?Because i have a timeout configured in my EJB-application, but in the example i try to get working, the client shall use its own timeout which is before the EJB-timeout.
The EJB-timeout works, but not the client timeout.....(as described above)
ejp wrote:
3. What happens at the client? An exception? Nothing?"Nothing", i.e. the client terminates when the connection times out (from the JBoss / EJB-side!)
ejp wrote:
4. Are you ignoring any exceptions at the client?No.
Shouldn't this client timeout be totally independent from any server / Jboss / whatever stuff?
Any more ideas?

RMI Client timeout set

I want to set a client timeout for RMI withing WLS. Is there a way to do
this? Any examples?
thanks,
Mike

Sorry.. I thought you were talking about rmi/iiop.
There is some time-out mechanism in Denali (5.1.x), but nothing in 4.5.x, as the neccessary infrastructure was not in place unitl Denali.
Let me know if you want me to look into how this is done in 5.1.x.
Michael Lee wrote:
I have 4.5.1 at the customer site now. Can this work with 4.5.1.
BTW, thanks.
----- Original Message -----
From: "Eduardo Ceballos" <[email protected]>
Newsgroups: weblogic.developer.interest.rmi-iiop
To: "Michael Lee" <[email protected]>
Sent: Wednesday, June 07, 2000 6:13 AM
Subject: Re: RMI Client timeout set
The idle disconnect timeout property will be aviable in service pack 4 and5.1.1.
Michael Lee wrote:
I want to set a client timeout for RMI withing WLS. Is there a way to do
this? Any examples?
thanks,
Mike

Upgrading from 8.1 to 9.2: non-WL SOAP/websvc client timeout

So, I was using a Weblogic 8.1 'clientgen' generated a SOAP/websvc client, based on a WSDL the svc provider gave me. The generated components were accessing an Axis SOAP svc from a WL 8.1 deployed svc.
To set the conn timeout and SOAP-end-point-URL dynamically, I did this:
System.setProperty("weblogic.webservice.UseWebLogicURLStreamHandler","true");
BindingInfo bindingInfo =(weblogic.webservice.binding.BindingInfo) stub._getProperty("weblogic.webservice.bindinginfo");
bindingInfo.setTimeout(3);
bindingInfo.setAddress("http://someco.com/SOAPEndPoint");
After regenerating using WL 9.2 'clientgen', it turns out BindingInfo is deprecated, but it only says "please migrate to jws for webservices". Not sure what that means, but after some searching, I was able to figure out that I might be able to do this:
stub._setProperty(MyStub.ENDPOINT_ADDRESS_PROPERTY,"http://someco.com/SOAPEndPoint");
stub._setProperty("weblogic.wsee.transport.connection.timeout",3);
Sadly, my env is not ready yet, so I haven't been able to try it out, so I thought I'd check here for comments.
I know I could do this using Axis' wsdl2java generated components, but I want to keep it within weblogic for now.
Also, I'm suspecting that the URL stream handler is no longer needed either.
Any comments?
Karoly

Hi All,
I am also having the same problem.
Some one PLEASE HELP, its very urgent.
Thanks,

How to implement web service client timeout

I'm trying to implement a web service client using JAX-RPC specification and the client is generated by clientgen utility. We are using weblogic8.1(sp5).
How do I control the connection timeout and data transmission timeout? I have tried:
BindingInfo.setTimeout() method and stub._setProperty("weblogic.webservice.rpc.timeoutsecs", "1" /* secs */);
and they don't seem to be working...
I have searched the web service documentation and didn't found any mentioning on this. Can someone shred some light on this?
Thanks.
Ren
null

Hi,
I had a problem too for setting the timeout of a webservice client. but i didn't find any thing on this.
But there is a work around for this see if it suits you but for this you have to use Apache AXIS webservice api to generate the client in that Api you have the Stub.timeOut() function to over come this problem
Cheers !!
Vivek:-)

Peap client timeout

Similar Messages

Maybe you are looking for