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]

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]

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?

[luciano]

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

[dparsons]

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.

[luciano]

Hello

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

[torsten_schoene]

I have same error. Do you have a solution?