Security

Reply
Occasional Contributor II

Repeated Ageout

 

I have a single user who gets a timeout message when trying to connect.  In the logs, I see what I take as the machine repeattingly aging out when trying to connect.  I don't see any authentication attempts with initiating the connection.  Am I reading this correctly?  Any ideas on why this could be happening?  Thanks.

 

 

 

Jun 27 14:40:22 :501065:  <DBUG> |stm|  send_ageout_sta_ack 8157: Send ageout sta 7c:d1:c3:e0:eb:e5 ack back to AP (10.159.21.8)
Jun 27 14:40:22 :501114:  <NOTI> |stm|  Deauth from sta: 7c:d1:c3:e0:eb:e5: AP 10.159.21.8-00:24:6c:11:b0:ed-MOV4-AP03 Reason 255
Jun 27 14:40:22 :501044:  <NOTI> |stm|  Station 7c:d1:c3:e0:eb:e5: No authentication found trying to de-authenticate to BSSID 00:24:6c:11:b0:ed on AP MOV4-AP03
Jun 27 14:40:22 :501065:  <DBUG> |stm|  send_ageout_sta_ack 8157: Send ageout sta 7c:d1:c3:e0:eb:e5 ack back to AP (10.159.12.61)
Jun 27 14:40:22 :501114:  <NOTI> |stm|  Deauth from sta: 7c:d1:c3:e0:eb:e5: AP 10.159.12.61-00:24:6c:11:ae:8d-MOV4-AP02 Reason 255
Jun 27 14:40:22 :501044:  <NOTI> |stm|  Station 7c:d1:c3:e0:eb:e5: No authentication found trying to de-authenticate to BSSID 00:24:6c:11:ae:8d on AP MOV4-AP02
Jun 27 14:40:22 :501065:  <DBUG> |stm|  send_ageout_sta_ack 8157: Send ageout sta 7c:d1:c3:e0:eb:e5 ack back to AP (10.159.21.8)
Jun 27 14:40:22 :501114:  <NOTI> |stm|  Deauth from sta: 7c:d1:c3:e0:eb:e5: AP 10.159.21.8-00:24:6c:11:b0:e5-MOV4-AP03 Reason 255
Jun 27 14:40:22 :501044:  <NOTI> |stm|  Station 7c:d1:c3:e0:eb:e5: No authentication found trying to de-authenticate to BSSID 00:24:6c:11:b0:e5 on AP MOV4-AP03

 

Re: Repeated Ageout

I have seen this before .

A couple questions :

- are you using an intel wireless card ?
- what AOS code you have installed ?
- trying run the show auth-tracebuf while the user is trying to authenticate .

The reason 255 happens when the device deauth but doesn't send a reason for the death
Thank you

Victor Fabian
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Occasional Contributor II

Re: Repeated Ageout

Its a Mabook Air, so its using Broadcom and I'm curently running 6.1.3.6.  As for the auth-tracebuf,  nothing shows up for that user which only added to my confusion.  

 

On an addtional note, the user is able to connect to a similar configured SSID from his RAP, but doesn't seem to be able to connect to any of the SSIDs in the office.

Guru Elite

Re: Repeated Ageout


TimS wrote:

 

I have a single user who gets a timeout message when trying to connect.  In the logs, I see what I take as the machine repeattingly aging out when trying to connect.  I don't see any authentication attempts with initiating the connection.  Am I reading this correctly?  Any ideas on why this could be happening?  Thanks.

 

 

 

Jun 27 14:40:22 :501065:  <DBUG> |stm|  send_ageout_sta_ack 8157: Send ageout sta 7c:d1:c3:e0:eb:e5 ack back to AP (10.159.21.8)
Jun 27 14:40:22 :501114:  <NOTI> |stm|  Deauth from sta: 7c:d1:c3:e0:eb:e5: AP 10.159.21.8-00:24:6c:11:b0:ed-MOV4-AP03 Reason 255
Jun 27 14:40:22 :501044:  <NOTI> |stm|  Station 7c:d1:c3:e0:eb:e5: No authentication found trying to de-authenticate to BSSID 00:24:6c:11:b0:ed on AP MOV4-AP03
Jun 27 14:40:22 :501065:  <DBUG> |stm|  send_ageout_sta_ack 8157: Send ageout sta 7c:d1:c3:e0:eb:e5 ack back to AP (10.159.12.61)
Jun 27 14:40:22 :501114:  <NOTI> |stm|  Deauth from sta: 7c:d1:c3:e0:eb:e5: AP 10.159.12.61-00:24:6c:11:ae:8d-MOV4-AP02 Reason 255
Jun 27 14:40:22 :501044:  <NOTI> |stm|  Station 7c:d1:c3:e0:eb:e5: No authentication found trying to de-authenticate to BSSID 00:24:6c:11:ae:8d on AP MOV4-AP02
Jun 27 14:40:22 :501065:  <DBUG> |stm|  send_ageout_sta_ack 8157: Send ageout sta 7c:d1:c3:e0:eb:e5 ack back to AP (10.159.21.8)
Jun 27 14:40:22 :501114:  <NOTI> |stm|  Deauth from sta: 7c:d1:c3:e0:eb:e5: AP 10.159.21.8-00:24:6c:11:b0:e5-MOV4-AP03 Reason 255
Jun 27 14:40:22 :501044:  <NOTI> |stm|  Station 7c:d1:c3:e0:eb:e5: No authentication found trying to de-authenticate to BSSID 00:24:6c:11:b0:e5 on AP MOV4-AP03

 


Whether you are setting this up manually or automatically, the client does not like what it sees upon association.  I would double-check those parameters or even open a support case to get to the bottom of it.

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: