topic Re: 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? in Aerohive Migrated Content

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 — Wed, 31 Oct 2018 17:55:58 GMT

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?

Re: 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?

dsouri — Wed, 31 Oct 2018 21:23:51 GMT

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

Re: 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 — Thu, 01 Nov 2018 17:15:14 GMT

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.

Re: 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?

dparsons — Wed, 23 Jan 2019 04:00:09 GMT

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.

Re: 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?

torsten_schoene — Tue, 26 Mar 2019 18:54:32 GMT

I have same error. Do you have a solution?

Re: 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?

luciano — Fri, 12 Apr 2019 01:01:19 GMT

Hello

I'm with the same error, does anyone know the solution to the problem?

Re: 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?

dparsons — Fri, 12 Apr 2019 01:14:10 GMT

First to clarify are you getting the "Tx assoc resp <reject> (status 17, pwr 10dBm)" or just (601)Sta(at if=wifi0.1) is de-authenticated because of notification of driver?

If you have the reject statement then you can default your radio profiles to make it go away. What is happening is in my case there are settings in my custom radio profiles that are preventing clients from connecting by design. Things like 802.1b clients, clients connecting at 12 Meg, ETC. If you are blocking any clients using settings in the custom radio profile you will have reject entries in your logs.

If there are no reject statements and just the "de-authenticated because of notification of driver" this is a normal entry that will always be there. Wireless clients are like customers at a store, you cannot prevent them from leaving the store whenever they want. And can't always control what store they want to go to.

Re: 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?

luciano — Fri, 12 Apr 2019 01:28:09 GMT

I have several devices that previously connected and now do not connect anymore, I put a device of these on the client monitor to see and one of them gave the log like this one below. as for the blocking of clients with technology b we made the block previously but it did not give problem in devices, an example was the device monitored that it was technology n and nevertheless connects only after a certain time insisting much.

4/09/2019 07:13:38 PM 34BB2645969C 885BDDCAD394 AH-TI DETAIL (116)Rx <broadcast> probe req (rssi -39dB)

04/09/2019 07:13:39 PM 34BB2645969C 885BDDCBE014 AH-301 DETAIL (37)Rx <broadcast> probe req (rssi -73dB)

04/09/2019 07:13:39 PM 34BB2645969C 885BDDCAD614 AH-NPF BASIC (71)Rx auth <open> (frame 1, rssi -63dB)

04/09/2019 07:13:39 PM 34BB2645969C 885BDDCAD614 AH-NPF BASIC (72)Tx auth <open> (frame 2, status 0, pwr 10dBm)

04/09/2019 07:13:39 PM 34BB2645969C 885BDDCAD614 AH-NPF BASIC (73)Rx assoc req (rssi -63dB)

04/09/2019 07:13:39 PM 34BB2645969C 885BDDCAD614 AH-NPF BASIC (74)Tx assoc resp <reject> (status 17, pwr 10dBm)

04/09/2019 07:13:48 PM 34BB2645969C 885BDDCAA254 AH-400 DETAIL (1035)Rx <broadcast> probe req (rssi -83dB)

04/09/2019 07:13:48 PM 34BB2645969C 885BDDCA9514 AH-LAB07 DETAIL (89)Rx <broadcast> probe req (rssi -77dB)

04/09/2019 07:13:48 PM 34BB2645969C 885BDDCA9514 AH-LAB07 DETAIL (90)Rx <broadcast> probe req (rssi -75dB)

04/09/2019 07:13:48 PM 34BB2645969C 885BDDCAD614 AH-NPF DETAIL (75)Rx <broadcast> probe req (rssi -61dB)

04/09/2019 07:13:48 PM 34BB2645969C 885BDDCAD614 AH-NPF DETAIL (76)Rx <broadcast> probe req (rssi -62dB)

04/09/2019 07:13:48 PM 34BB2645969C 885BDDCAD394 AH-TI DETAIL (117)Rx <broadcast> probe req (rssi -46dB)

04/09/2019 07:13:48 PM 34BB2645969C 885BDDCAD394 AH-TI DETAIL (118)Rx <broadcast> probe req (rssi -43dB)

04/09/2019 07:13:48 PM 34BB2645969C 885BDDCAD394 AH-TI DETAIL (119)Rx <broadcast> probe req (rssi -43dB)

04/09/2019 07:13:48 PM 34BB2645969C 885BDDCAD394 AH-TI DETAIL (120)Rx <broadcast> probe req (rssi -45dB)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCBE014 AH-301 DETAIL (38)Rx <broadcast> probe req (rssi -82dB)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCBE014 AH-301 DETAIL (39)Rx <broadcast> probe req (rssi -81dB)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCA9514 AH-LAB07 DETAIL (91)Rx <broadcast> probe req (rssi -86dB)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCA9514 AH-LAB07 DETAIL (92)Rx <broadcast> probe req (rssi -81dB)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCA9514 AH-LAB07 DETAIL (93)Rx <broadcast> probe req (rssi -71dB)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD614 AH-NPF DETAIL (77)Rx <broadcast> probe req (rssi -64dB)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD614 AH-NPF DETAIL (78)Rx <broadcast> probe req (rssi -90dB)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD394 AH-TI DETAIL (121)Rx <broadcast> probe req (rssi -37dB)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD394 AH-TI DETAIL (122)Rx <broadcast> probe req (rssi -42dB)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD394 AH-TI DETAIL (123)Rx <specific> probe req (rssi -78dB)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD394 AH-TI INFO (124)Suppress stopped by high density, reason: safety-net timeout

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD394 AH-TI BASIC (125)Tx probe resp (pwr 10dBm)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD394 AH-TI BASIC (126)Tx probe resp (pwr 10dBm)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD394 AH-TI BASIC (127)Rx auth <open> (frame 1, rssi -57dB)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD394 AH-TI BASIC (128)Tx auth <open> (frame 2, status 0, pwr 10dBm)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD394 AH-TI BASIC (129)Rx assoc req (rssi -59dB)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD394 AH-TI BASIC (130)Tx assoc resp <accept> (status 0, pwr 10dBm)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD394 AH-TI INFO (131)IEEE802.1X auth is starting (at if=wifi0.1)

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD394 AH-TI DETAIL (132)Send message to RADIUS Server(10.110.0.74): code=1 (Access-Request) identifier=61 length=230, User-Name=004169 Called-Station-Id=88-5B-DD-CA-D3-94:WLAN_UNIARP Calling-Station-Id=34-BB-26-45-96-9C NAS-IP-Address=10.100.0.131

04/09/2019 07:13:49 PM 34BB2645969C 885BDDCAD394 AH-TI DETAIL (133)Receive message from RADIUS Server: code=11 (Access-Challenge) identifier=61 length=90

Re: 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?

dparsons — Fri, 12 Apr 2019 02:13:14 GMT

If you wish to confirm you can set your radios to default profiles but I don't think your issue is with the reject as it is too far up in the log and the 802.1X auth is starting. It would not get that far if there was a radio issue. I would suggest looking at the radius logs and see what errors are showing up there. I normally filter out the probe request as it cleans up the logs and makes it easier to see issues as well as lessens the length of the post her.

Do you get any additional logs from the radius server or does it just start over?

Re: 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?

luciano — Fri, 12 Apr 2019 02:34:41 GMT

in the radius we do not have any error, in the client monitor it simply restarts the reconnection, for the users, in the devices it appears as authentication error, and the device starts again to try the reconnection, this began after we made some changes due to a In some places, the channels have been manually changed from aps, the configuration has been made for the users to work in 10 dBm in 2.4 and also for a balance of frequency usage 5 of 80% in it and 20% in 2.4

Re: 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?

dparsons — Fri, 12 Apr 2019 02:55:24 GMT

Do the logs in the radius server show any entries for User-Name=004169 ? And what are you using for a radius server?

Re: 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?

luciano — Fri, 12 Apr 2019 03:03:15 GMT

I did not find any log in radius that he refused the connection to the only entry that there was from the moment the device connected. I am using a radius nps windows server

Re: 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?

dparsons — Fri, 12 Apr 2019 03:04:08 GMT

I was afraid of that. Is the network card in the device an Intel and is it a Dell?

Re: 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?

luciano — Fri, 12 Apr 2019 03:06:20 GMT

sorry but which device if it is from the server it is a virtual machine and the client device is an android phone in this case.

Re: 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?

luciano — Fri, 12 Apr 2019 03:08:34 GMT

one thing I noticed was that the devices that connect at 5 GHz it does not have this problem. but the ones that connect in 2.4 have this problem. for example here in TI we have some devices most connect in 5 GHz in AC and we have no problem of this type already 2 devices that we have here that are 2.4 GHz suffer repeatedly drops and connection failures

Re: 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?

dparsons — Fri, 12 Apr 2019 03:17:49 GMT

Okay good. We had/have an issue with some Intel wireless adapters in Dell laptops that have bad drivers that give the same results.

I would recommend cloning the default radio profiles for 2.4. Then apply that to an AP to test against. If the device can then connect, next change one setting at a time in the profile and test again. There are several settings that can break clients such as "Enable VHT" on the 2.4. If you have this enable try just turning it off, it was breaking my cell phones. By making one change at a time you should be able to determine which setting or settings are causing the issue.

Re: 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?

luciano — Fri, 12 Apr 2019 03:22:07 GMT

I took a look here to activate vht this disabled ja. a question about balancing can cause some problem like this? being configured this way?

Re: 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?

dparsons — Fri, 12 Apr 2019 03:30:45 GMT

I am using it with no issue.

Re: 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?

dparsons — Fri, 12 Apr 2019 03:37:20 GMT

However you are forcing the ratio I am only encouraging the client to use 5. Since you are forcing the ratio if the ration exceeds 20% then the client would not be able to connect. What is the current ratio at? Unless there is a need to force it I would recommend only encouraging it.

Here is my environment. We are a community college with a peak of 1000 students online during the day.

Re: 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?

luciano — Fri, 12 Apr 2019 03:47:16 GMT

we are also a community university with about 700 simutaneous accesses, in my case this change to force the devices to connect in 5 GHz was faulted about 15 days approximately and the reason that started this connection problem.

I made the change so that the AP will encourage the connection at 5 GHz and no longer force it. I also did the activation of the Enable client load balancing among neighboring hive members. for APs.