Wireless Access

Reply
Occasional Contributor II

Re: Controller doesn't seem to pass ip addresses from various vlans

I have been told that having more then 250 clients per vlan can cause broadcast issues on a wireless network.  I have well over that ammount that will be connecting to my network in less then a month.  what i have done is created a bunch of scopes in my dhcp that have ~250 address per vlan.  (EX. vlan 720,721,722,ect...)  when i add just one vlan to the vap it works just fine but that will only give me 250 addresses untill i am out.  i am wanting to add several vlans.  the problem occurs when i do this once more then one vlan is added to the vap then nothing works.

Occasional Contributor II

Re: Controller doesn't seem to pass ip addresses from various vlans

(Aruba7210-US) #show ap association client-mac d0:23:db:7b:64:a7

The phy column shows client's operational capabilities for current association

Flags: A: Active, B: Band Steerable, H: Hotspot(802.11u) client, K: 802.11K clie nt, R: 802.11R client, W: WMM client, w: 802.11w client

PHY Details: HT : High throughput; 20: 20MHz; 40: 40MHz
VHT : Very High throughput; 80: 80MHz; 160: 160MHz; 80p80: 80MHz + 80MHz
<n>ss: <n> spatial streams

Association Table
-----------------
Name bssid mac auth assoc aid l-int essid vlan-id tunnel-id phy assoc. time num assoc Flags Band s teer moves (T/S)
---- ----- --- ---- ----- --- ----- ----- ------- --------- --- ----------- --------- ----- ------ ----------------
TESTAP1 d8:c7:c8:ac:30:62 d0:23:db:7b:64:a7 y y 1 15 FortOsag e-Mobile 720 0x10094 g-HT-20-1ss 48s 1 WA 0/0

d0:23:db:7b:64:a7-d8:c7:c8:ac:30:62 Stats
------------------------------------------
Parameter Value
--------- -----
Channel 11
Channel Frame Retry Rate(%) 0
Channel Frame Low Speed Rate(%) 0
Channel Frame Non Unicast Rate(%) 0
Channel Frame Fragmentation Rate(%) 0
Channel Frame Error Rate(%) 0
Channel Bandwidth Rate(kbps) 12
Channel Noise 94
Client Frame Retry Rate(%) 0
Client Frame Low Speed Rate(%) 0
Client Frame Non Unicast Rate(%) 0
Client Frame Fragmentation Rate(%) 0
Client Frame Receive Error Rate(%) 0
Client Bandwidth Rate(kbps) 0
Client Tx Packets 64
Client Rx Packets 20
Client Tx Bytes 4558
Client Rx Bytes 4769
Client SNR 38

 

 

 

(Aruba7210-US) # show user | include d0:23:db:7b:64:a7

(Aruba7210-US) # show user | include d0:23:db:7b:64:a7

 

 

no output

 

Aruba Employee

Re: Controller doesn't seem to pass ip addresses from various vlans

the client is currently falling in vlan 720.  i see you have tested the vlan 721 using access port. can you try assigning vlan 720 to the access port and see if you are getting IP address on wired laptop..

 

Also i see ur client is associated but not in user table. might be the 169-valid user acl might have blocked this becuase of no ip. please provide us the 

show auth-tracebuff mac <client mac>

to verify if the client has issues in connecting to wireless. 

 

 

Vinod Kumaar AVM ACMX, ACDX
Principal Network Engineer
Customer Advocacy | Aruba Networks Inc.

Did something you read in the Community solve a problem for you? If so, click "Accept as Solution" in the bottom right hand corner of the post.
MVP Guru

Re: Controller doesn't seem to pass ip addresses from various vlans

Please enable:
logging level debugging network process dhcp
Logging level debugging user

Show log all : include <device mac >
Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Occasional Contributor II

Re: Controller doesn't seem to pass ip addresses from various vlans

Jul 15 14:14:24 mobileip[3539]: <500511> <DBUG> |mobileip| Station d0:23:db:7b:64:a7, 0.0.0.0: Received association on ESSID: FortOsage-Mobile Mobility service ON, HA Discovery on Association ON, Fastroaming Disabled, AP: Name TESTAP1 Group FortOsage3 BSSID d8:c7:c8:ac:30:62, phy g, VLAN 720
Jul 15 14:14:24 mobileip[3539]: <500511> <DBUG> |mobileip| Station d0:23:db:7b:64:a7, 0.0.0.0: Received association on ESSID: FortOsage-Mobile Mobility service ON, HA Discovery on Association ON, Fastroaming Disabled, AP: Name TESTAP1 Group FortOsage3 BSSID d8:c7:c8:ac:30:62, phy g, VLAN 720
Jul 15 14:14:24 stm[3478]: <501095> <NOTI> |stm| Assoc request @ 14:14:24.190033: d0:23:db:7b:64:a7 (SN 3): AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1
Jul 15 14:14:24 stm[3478]: <501095> <NOTI> |stm| Assoc request @ 14:14:24.190209: d0:23:db:7b:64:a7 (SN 3): AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1
Jul 15 14:14:24 stm[3478]: <501100> <NOTI> |stm| Assoc success @ 14:14:24.190886: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1
Jul 15 14:14:24 stm[3478]: <501100> <NOTI> |stm| Assoc success @ 14:14:24.191110: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1
Jul 15 14:14:24 stm[736]: <501065> <DBUG> |AP TESTAP1@10.10.3.17 stm| remove_stale_sta 2420: client d0:23:db:7b:64:a7 not in stale hash table
Jul 15 14:14:24 stm[736]: <501093> <NOTI> |AP TESTAP1@10.10.3.17 stm| Auth success: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1
Jul 15 14:14:24 stm[736]: <501095> <NOTI> |AP TESTAP1@10.10.3.17 stm| Assoc request @ 14:14:24.178985: d0:23:db:7b:64:a7 (SN 3): AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1
Jul 15 14:14:24 stm[736]: <501100> <NOTI> |AP TESTAP1@10.10.3.17 stm| Assoc success @ 14:14:24.180731: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1
Jul 15 14:14:24 stm[736]: <501109> <NOTI> |AP TESTAP1@10.10.3.17 stm| Auth request: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1 auth_alg 0
Jul 15 14:14:28 authmgr[3473]: <522137> <DBUG> |authmgr| Sibyte-d0:23:db:7b:64:a7/10.12.20.2 : User-Agent: CommCenterMobileHelper/1464.1 CFNetwork/609.1.4 Darwin/13.0.0.
Jul 15 14:14:28 authmgr[3473]: <522137> <DBUG> |authmgr| Sibyte-d0:23:db:7b:64:a7/10.12.20.2 : User-Agent: CommCenterMobileHelper/1464.1 CFNetwork/609.1.4 Darwin/13.0.0.
Jul 15 14:15:56 authmgr[3473]: <522234> <DBUG> |authmgr| Setting idle timer for user d0:23:db:7b:64:a7 to 300 seconds (idle timeout: 300 ageout: 0).
Jul 15 14:15:56 authmgr[3473]: <522234> <DBUG> |authmgr| Setting idle timer for user d0:23:db:7b:64:a7 to 300 seconds (idle timeout: 300 ageout: 0).
Jul 15 14:15:56 stm[3478]: <501000> <DBUG> |stm| Station d0:23:db:7b:64:a7: Clearing state
Jul 15 14:15:56 stm[3478]: <501000> <DBUG> |stm| Station d0:23:db:7b:64:a7: Clearing state
Jul 15 14:15:56 stm[3478]: <501102> <NOTI> |stm| Disassoc from sta: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1 Reason STA has left and is disassociated
Jul 15 14:15:56 stm[3478]: <501102> <NOTI> |stm| Disassoc from sta: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1 Reason STA has left and is disassociated
Jul 15 14:15:56 stm[736]: <501000> <DBUG> |AP TESTAP1@10.10.3.17 stm| Station d0:23:db:7b:64:a7: Clearing state
Jul 15 14:15:56 stm[736]: <501065> <DBUG> |AP TESTAP1@10.10.3.17 stm| store_stale_sta 2317: sta d0:23:db:7b:64:a7 saved to stale_sta_hash_table
Jul 15 14:15:56 stm[736]: <501102> <NOTI> |AP TESTAP1@10.10.3.17 stm| Disassoc from sta: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1 Reason STA has left and is disassociated
Jul 15 14:16:14 stm[3478]: <501044> <NOTI> |stm| Station d0:23:db:7b:64:a7: No authentication found trying to de-authenticate to BSSID d8:c7:c8:ac:30:62 on AP TESTAP1
Jul 15 14:16:14 stm[3478]: <501044> <NOTI> |stm| Station d0:23:db:7b:64:a7: No authentication found trying to de-authenticate to BSSID d8:c7:c8:ac:30:62 on AP TESTAP1
Jul 15 14:16:14 stm[3478]: <501105> <NOTI> |stm| Deauth from sta: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1 Reason STA has left and is deauthenticated
Jul 15 14:16:14 stm[3478]: <501105> <NOTI> |stm| Deauth from sta: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1 Reason STA has left and is deauthenticated
Jul 15 14:16:14 stm[736]: <501065> <DBUG> |AP TESTAP1@10.10.3.17 stm| group_resend_ageout_sta 13433: Resend ageout of client d0:23:db:7b:64:a7 to sw STM
Jul 15 14:16:14 stm[736]: <501065> <DBUG> |AP TESTAP1@10.10.3.17 stm| remove_stale_sta 2430: sta d0:23:db:7b:64:a7 is freed and removed from stale_sta_hash_table
Jul 15 14:16:25 stm[3478]: <501044> <NOTI> |stm| Station d0:23:db:7b:64:a7: No authentication found trying to de-authenticate to BSSID d8:c7:c8:ac:30:62 on AP TESTAP1
Jul 15 14:16:25 stm[3478]: <501044> <NOTI> |stm| Station d0:23:db:7b:64:a7: No authentication found trying to de-authenticate to BSSID d8:c7:c8:ac:30:62 on AP TESTAP1
Jul 15 14:16:25 stm[3478]: <501065> <DBUG> |stm| send_ageout_sta_ack 13104: Send ageout sta d0:23:db:7b:64:a7 ack back to AP (10.10.3.17)
Jul 15 14:16:25 stm[3478]: <501065> <DBUG> |stm| send_ageout_sta_ack 13104: Send ageout sta d0:23:db:7b:64:a7 ack back to AP (10.10.3.17)
Jul 15 14:16:25 stm[3478]: <501114> <NOTI> |stm| Deauth from sta: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1 Reason 255
Jul 15 14:16:25 stm[3478]: <501114> <NOTI> |stm| Deauth from sta: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1 Reason 255
Jul 15 14:16:25 stm[736]: <501065> <DBUG> |AP TESTAP1@10.10.3.17 stm| remove_stale_sta 2430: sta d0:23:db:7b:64:a7 is freed and removed from stale_sta_hash_table
Jul 15 14:16:25 stm[736]: <501065> <DBUG> |AP TESTAP1@10.10.3.17 stm| store_stale_sta 2317: sta d0:23:db:7b:64:a7 saved to stale_sta_hash_table
Jul 15 14:16:25 stm[736]: <501080> <NOTI> |AP TESTAP1@10.10.3.17 stm| Deauth to sta: d0:23:db:7b:64:a7: Ageout AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1 Sapcp Ageout (internal ageout)
Jul 15 14:16:25 stm[736]: <501106> <NOTI> |AP TESTAP1@10.10.3.17 stm| Deauth to sta: d0:23:db:7b:64:a7: Ageout AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1 handle_sapcp

MVP Guru

Re: Controller doesn't seem to pass ip addresses from various vlans

 

It seems like your device is able to pickup an IP address on VLAN 720 at some point  in the process :

 

ul 15 14:14:28 authmgr[3473]: <522137> <DBUG> |authmgr| Sibyte-d0:23:db:7b:64:a7/10.12.20.2 : User-Agent: CommCenterMobileHelper/1464.1 CFNetwork/609.1.4 Darwin/13.0.0.

 

But then the client disassociates :

 

Jul 15 14:15:56 stm[3478]: <501102> <NOTI> |stm| Disassoc from sta: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1 Reason STA has left and is disassociated
Jul 15 14:15:56 stm[3478]: <501102> <NOTI> |stm| Disassoc from sta: d0:23:db:7b:64:a7: AP 10.10.3.17-d8:c7:c8:ac:30:62-TESTAP1 Reason STA has left and is disassociated

 

Jul 15 14:16:14 stm[3478]: <501044> <NOTI> |stm| Station d0:23:db:7b:64:a7: No authentication found trying to de-authenticate to BSSID d8:c7:c8:ac:30:62 on AP TESTAP1
Jul 15 14:16:14 stm[3478]: <501044> <NOTI> |stm| Station d0:23:db:7b:64:a7: No authentication found trying to de-authenticate to BSSID d8:c7:c8:ac:30:62 on AP TESTAP1

 

What type of authentication are you using ?

 

As vkumaar please provide the show auth-tracebuff mac <client mac> this will give you an idea of what's going on during the authentication process.

 

In regards to the having a lot broadcast in a large segment /22 or /23 you could fix that by enabling the following :

 

Virtual AP (Drops broadcast/multicast on the wireless side of things)

Screen Shot 2013-07-15 at 7.31.05 PM.png

 

VLAN (Drops broadcast/multicast on the wire side of things)

Screen Shot 2013-07-15 at 7.31.05 PM.png

 

Note: This is only valid if you don't need applications that required multicast to transmit because once you enabled this it will drop multicast as well

Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Occasional Contributor II

Re: Controller doesn't seem to pass ip addresses from various vlans

We are using radius authentication.  using PEAP and EAP-MSCHAPv2

Aruba Employee

Re: Controller doesn't seem to pass ip addresses from various vlans

it looks more like a client connectivity issue. can you let me know the client type/version you are using and also give us the auth tracebuff output. 

Vinod Kumaar AVM ACMX, ACDX
Principal Network Engineer
Customer Advocacy | Aruba Networks Inc.

Did something you read in the Community solve a problem for you? If so, click "Accept as Solution" in the bottom right hand corner of the post.
Occasional Contributor II

Re: Controller doesn't seem to pass ip addresses from various vlans

iOS iPhone, and iPad Mini both are running 6.1.3

 

 

 

Jul 15 14:31:17 station-down * d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 - -
Jul 15 14:49:48 station-up * d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 - - wpa2 aes
Jul 15 14:49:48 eap-id-req <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 1 5
Jul 15 14:49:48 eap-id-resp -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 1 12 jtieman
Jul 15 14:49:48 rad-req -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 33 203
Jul 15 14:49:48 rad-resp <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 33 90
Jul 15 14:49:48 eap-req <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 2 6
Jul 15 14:49:48 eap-resp -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 2 166
Jul 15 14:49:48 rad-req -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 34 395
Jul 15 14:49:48 rad-resp <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 34 1188
Jul 15 14:49:48 eap-req <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 3 1096
Jul 15 14:49:48 eap-resp -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 3 6
Jul 15 14:49:48 rad-req -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 35 235
Jul 15 14:49:48 rad-resp <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 35 1188
Jul 15 14:49:48 eap-req <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 4 1096
Jul 15 14:49:48 eap-resp -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 4 6
Jul 15 14:49:48 rad-req -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 36 235
Jul 15 14:49:48 rad-resp <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 36 312
Jul 15 14:49:48 eap-req <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 5 228
Jul 15 14:49:48 eap-resp -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 5 220
Jul 15 14:49:48 rad-req -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 37 449
Jul 15 14:49:48 rad-resp <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 37 153
Jul 15 14:49:48 eap-req <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 6 69
Jul 15 14:49:48 eap-resp -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 6 6
Jul 15 14:49:48 rad-req -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 38 235
Jul 15 14:49:48 rad-resp <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 38 127
Jul 15 14:49:48 eap-req <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 7 43
Jul 15 14:49:48 eap-resp -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 7 43
Jul 15 14:49:48 rad-req -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 39 272
Jul 15 14:49:48 rad-resp <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 39 143
Jul 15 14:49:48 eap-req <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 8 59
Jul 15 14:49:48 eap-resp -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 8 43
Jul 15 14:49:48 rad-req -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 40 272
Jul 15 14:49:48 rad-resp <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 40 159
Jul 15 14:49:48 eap-req <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 9 75
Jul 15 14:49:48 eap-resp -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 9 107
Jul 15 14:49:48 rad-req -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 41 336
Jul 15 14:49:48 rad-resp <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 41 175
Jul 15 14:49:48 eap-req <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 10 91
Jul 15 14:49:48 eap-resp -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 10 43
Jul 15 14:49:48 rad-req -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 42 272
Jul 15 14:49:48 rad-resp <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 42 191
Jul 15 14:49:48 eap-req <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 12 107
Jul 15 14:49:48 eap-resp -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 12 43
Jul 15 14:49:48 rad-req -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 43 272
Jul 15 14:49:48 rad-accept <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62/10.10.0.46 43 306
Jul 15 14:49:48 eap-success <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 12 4
Jul 15 14:49:48 wpa2-key1 <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 - 117
Jul 15 14:49:48 wpa2-key2 -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 - 117
Jul 15 14:49:48 wpa2-key3 <- d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 - 151
Jul 15 14:49:48 wpa2-key4 -> d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 - 95
Jul 15 14:53:11 station-down * d0:23:db:7b:64:a7 d8:c7:c8:ac:30:62 - -
Jul 15 14:53:11 station-up * d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 - - wpa2 aes
Jul 15 14:53:11 eap-id-req <- d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 1 5
Jul 15 14:53:11 eap-id-resp -> d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 1 12 jtieman
Jul 15 14:53:11 rad-req -> d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 44 216
Jul 15 14:53:11 rad-resp <- d0:23:db:7b:64:a7 00:24:6c:29:0f:d3/10.10.0.46 44 90
Jul 15 14:53:11 eap-req <- d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 2 6
Jul 15 14:53:11 eap-resp -> d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 2 198
Jul 15 14:53:11 rad-req -> d0:23:db:7b:64:a7 00:24:6c:29:0f:d3/10.10.0.46 45 440
Jul 15 14:53:11 rad-resp <- d0:23:db:7b:64:a7 00:24:6c:29:0f:d3/10.10.0.46 45 239
Jul 15 14:53:11 eap-req <- d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 3 155
Jul 15 14:53:11 eap-resp -> d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 3 69
Jul 15 14:53:11 rad-req -> d0:23:db:7b:64:a7 00:24:6c:29:0f:d3/10.10.0.46 46 311
Jul 15 14:53:11 rad-resp <- d0:23:db:7b:64:a7 00:24:6c:29:0f:d3/10.10.0.46 46 191
Jul 15 14:53:11 eap-req <- d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 6 107
Jul 15 14:53:11 eap-resp -> d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 6 43
Jul 15 14:53:11 rad-req -> d0:23:db:7b:64:a7 00:24:6c:29:0f:d3/10.10.0.46 47 285
Jul 15 14:53:11 rad-accept <- d0:23:db:7b:64:a7 00:24:6c:29:0f:d3/10.10.0.46 47 306
Jul 15 14:53:11 eap-success <- d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 6 4
Jul 15 14:53:11 wpa2-key1 <- d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 - 117
Jul 15 14:53:11 wpa2-key2 -> d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 - 117
Jul 15 14:53:11 wpa2-key3 <- d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 - 151
Jul 15 14:53:11 wpa2-key4 -> d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 - 95
Jul 15 14:54:03 station-down * d0:23:db:7b:64:a7 00:24:6c:29:0f:d3 - -
Jul 15 14:54:03 station-up * d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 - - wpa2 aes
Jul 15 14:54:03 eap-id-req <- d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 1 5
Jul 15 14:54:03 eap-id-resp -> d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 1 12 jtieman
Jul 15 14:54:03 rad-req -> d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 48 216
Jul 15 14:54:03 rad-resp <- d0:23:db:7b:64:a7 00:24:6c:29:1b:d3/10.10.0.46 48 90
Jul 15 14:54:03 eap-req <- d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 2 6
Jul 15 14:54:03 eap-resp -> d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 2 198
Jul 15 14:54:03 rad-req -> d0:23:db:7b:64:a7 00:24:6c:29:1b:d3/10.10.0.46 49 440
Jul 15 14:54:03 rad-resp <- d0:23:db:7b:64:a7 00:24:6c:29:1b:d3/10.10.0.46 49 239
Jul 15 14:54:03 eap-req <- d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 3 155
Jul 15 14:54:03 eap-resp -> d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 3 69
Jul 15 14:54:03 rad-req -> d0:23:db:7b:64:a7 00:24:6c:29:1b:d3/10.10.0.46 50 311
Jul 15 14:54:03 rad-resp <- d0:23:db:7b:64:a7 00:24:6c:29:1b:d3/10.10.0.46 50 191
Jul 15 14:54:03 eap-req <- d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 6 107
Jul 15 14:54:03 eap-resp -> d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 6 43
Jul 15 14:54:03 rad-req -> d0:23:db:7b:64:a7 00:24:6c:29:1b:d3/10.10.0.46 51 285
Jul 15 14:54:03 rad-accept <- d0:23:db:7b:64:a7 00:24:6c:29:1b:d3/10.10.0.46 51 306
Jul 15 14:54:03 eap-success <- d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 6 4
Jul 15 14:54:03 wpa2-key1 <- d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 - 117
Jul 15 14:54:03 wpa2-key2 -> d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 - 117
Jul 15 14:54:03 wpa2-key3 <- d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 - 151
Jul 15 14:54:03 wpa2-key4 -> d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 - 95
Jul 15 14:54:29 station-down * d0:23:db:7b:64:a7 00:24:6c:29:1b:d3 - -

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