Hello,
I have installed some hap ac2 with AP and virtual APs.
Today I have found that one of the devices that connects to one of the virtual APs is getting banned:
I have tried disabling temporaly the interface and enabling again, but the device keeps “banned”.
Where is this ban list stored?
Later I have tried unselecting the option “Default authenticate” and including all expected devices in the list, but the logs keep informing me that it is banned.
EDIT: This hap ac2 has installed routerOS 6.47 (not 6.44.1) and has been running great for months
No idea where to find the “banned list”, nor how long it remains active (30 sec? 1 min ? …)
You get in the banned list because of the repeated previous error.
Unfortunately “unspecified(1)= undefined reason” is not very helpful in knowing how to avoid the error. (Linux wifi reason codes can be found on-line, one specified “E.G. no SSID given”)
Eliminate the error and you will not return to the banned list.
“Forget” the known network on the client device before retrying.
Thanks, after trying different solutions all morning with this issue I restarted the client and the error disappeared (it is an esp8266 board, will check it the following weeks if the error appears again)
After a week de device has failed again.
Is there any setting in the Mikrotik that can be changed to minimize those errors? (hw retries, disconnect timeout, …?)
The device had been working with this same router for over a year without any glitch.
Same reason in the LOG “unspecified(1)” ?
Question is, is it the MKT, or the esp8266 that fails in the connection process ? Or is it triggered by other RF signals?
Are there frequent disconnects? In Registration check: Uptime, TX rate (xxxMbps-yyMHz/nS/.GI) , the TX/RX CCQ and the ratio (TX frames/ TX HW frames).
Based on that you can try to either eliminate the disconnect cause or strengthen the connection persistence.
Root cause is a failing (re-)connection. Disconnects should not be a problem unless too frequent.(They are usually reason 3 or 8 (8 =station leaving AP for roaming))
Indeed, same reason (unspecified(1)).
Thanks, I will try and check your advice.
I suspect there has been some external interference, because it has failed 7 days later.
I just saw here a lot of unspecified(1) errors, because someone used the wrong password for a WPA2/EAP/AES-ccm (Radius) protected SSID.
When also enabling tkip (not recommended for high speed) the error changes to “802.1x authentication failed”.
