topic Re: WAP 371 deauthenticate client in Wireless

WAP 371 deauthenticate client

DavideZanichelli31808 — Mon, 05 Jul 2021 18:26:48 GMT

Good evening, I have two wap 371 in single point setup, and in the log file I have many of this message:

Log Message from AP 192.168.0.245

TIME Priority Process Id Message

========================================================================

Dec 17 2019 17:38:35 3 hostapd[16425] trying to deauthenticate to station 74:70:fd:1f:58:56, but not authenticated

Re: WAP 371 deauthenticate client

pieterh — Mon, 23 Dec 2019 14:26:34 GMT

first reaction is : expected behavior

the client is associated/authenticated by AP1 end for some reason communicates with AP2 where it is not authenticated (yet).

this only disappears on an integrated infrastructure where the AP's work together

either with a dedicated controller or with a common ME infrastructure where one of the AP's takes the controller function.

Re: WAP 371 deauthenticate client

DavideZanichelli31808 — Tue, 07 Jan 2020 16:09:01 GMT

Good morning, my access point work togheter in single point setup mode. I look that one of two access point is cluster controller. Why they don't work fine? Thanks

Re: WAP 371 deauthenticate client

DavideZanichelli31808 — Fri, 14 Feb 2020 14:08:54 GMT

why no one can help me?

Re: WAP 371 deauthenticate client

pieterh — Fri, 14 Feb 2020 15:33:00 GMT

found multiple posts like this one

it suggests it is an incompatibility between client and AP

connectivity can be improved by disabling MFP or PMF (depending on software version)