cancel
Showing results for 
Search instead for 
Did you mean: 

Does anybody know what means "sta(at if=wifi0.1) is deauthenticated because of notification of driver" in client monitor of Hivemanager Classic V8.2r2?

Does anybody know what means "sta(at if=wifi0.1) is deauthenticated because of notification of driver" in client monitor of Hivemanager Classic V8.2r2?

AnonymousM
Valued Contributor II
Does anybody know what means "sta(at if=wifi0.1) is deauthenticated because of notification of driver" in client monitor of Hivemanager Classic V8.2r2?
1 ACCEPTED SOLUTION

dsouri
Contributor III

Hi Gunter,

 

Typically, given all other conditions are fair, the client device disconnected from the radio. To really know why, it's best to see more of what happened Before & After the deauthenticated log entry.

 

Is there an overall issue you are looking into, or just exploring the Client Monitor tool?

 

Happy to help, 

David Souri

HiveCommunity Moderator

View solution in original post

22 REPLIES 22

dparsons
Contributor

I am having the same issue. If you look in the log you will see "Tx assoc resp <reject> (status 17, pwr 10dBm)". This is an indication that the AP cannot take another connection due to the exhausting of AIDs on the AP. Cannot find any information on Aerohive's website if this is a known issue but Cisco had this same bug recently. I am opening a TAC case with Aerohive to see what they can find.

AnonymousM
Valued Contributor II

Hello David,

 

thank you for your answer. There are several users complaining because of sudden disconnects.

 

Here is an excerpt from client monitor:

 

10/31/2018 08:48:54 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (530)Rx auth <open> (frame 1, rssi -65dB)

10/31/2018 08:48:54 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (531)Tx auth <open> (frame 2, status 0, pwr 10dBm)

10/31/2018 08:48:54 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (532)Rx assoc req (rssi -65dB)

10/31/2018 08:48:54 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (533)Tx assoc resp <reject> (status 17, pwr 10dBm)

10/31/2018 08:50:59 AM 8883228D5210 C413E2934314 AP02-324-1-250 BASIC  (601)Sta(at if=wifi0.1) is de-authenticated because of notification of driver

10/31/2018 08:54:05 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (535)Sta(at if=wifi0.1) is de-authenticated because of notification of driver

10/31/2018 08:55:53 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (549)Rx auth <open> (frame 1, rssi -63dB)

10/31/2018 08:55:53 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (550)Tx auth <open> (frame 2, status 0, pwr 10dBm)

10/31/2018 08:55:54 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (551)Rx assoc req (rssi -63dB)

10/31/2018 08:55:54 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (552)Tx assoc resp <reject> (status 17, pwr 10dBm)

10/31/2018 08:58:54 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (554)Rx auth <open> (frame 1, rssi -64dB)

10/31/2018 08:58:54 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (555)Tx auth <open> (frame 2, status 0, pwr 10dBm)

10/31/2018 08:58:54 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (556)Rx assoc req (rssi -64dB)

10/31/2018 08:58:54 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (557)Tx assoc resp <reject> (status 17, pwr 10dBm)

10/31/2018 09:02:54 AM 8883228D5210 C413E2934314 AP02-324-1-250 BASIC  (633)Rx auth <open> (frame 1, rssi -59dB)

10/31/2018 09:02:54 AM 8883228D5210 C413E2934314 AP02-324-1-250 BASIC  (634)Tx auth <open> (frame 2, status 0, pwr 6dBm)

10/31/2018 09:02:54 AM 8883228D5210 C413E2934314 AP02-324-1-250 BASIC  (635)Rx assoc req (rssi -59dB)

10/31/2018 09:02:54 AM 8883228D5210 C413E2934314 AP02-324-1-250 BASIC  (636)Tx assoc resp <reject> (status 17, pwr 6dBm)

10/31/2018 09:04:07 AM 8883228D5210 C413E2939114 AP02-421-1-250 BASIC  (559)Sta(at if=wifi0.1) is de-authenticated because of notification of driver

 

For me this looks like an association request which becomes rejected by one AP and about one minute later the clients de-authenticates from another AP. That does not seem to make much sense.

dsouri
Contributor III

Hi Gunter,

 

Typically, given all other conditions are fair, the client device disconnected from the radio. To really know why, it's best to see more of what happened Before & After the deauthenticated log entry.

 

Is there an overall issue you are looking into, or just exploring the Client Monitor tool?

 

Happy to help, 

David Souri

HiveCommunity Moderator

GTM-P2G8KFN