Hi,
I have lot of smart home devices and when they are on mikrotik WiFi, they are still getting disconnected every 20mins, but when on TP-Link WiFi, they working normal. On Mikrotik log a getting this meeeages:
XX:XX:XX:XX:XX:XX@wlan1: disconnected, received deauth: sending station leaving (8)
OR
XX:XX:XX:XX:XX:XX@wlan1: disconnected, received disassoc: sending station leaving (8)
after few second it connect back, with this message:
XX:XX:XX:XX:XX:XX@wlan1: connected, signal strength -51
A config export in cases like this is pretty useless.
You’d have to capture the actual wireless traffic and see what makes the station send deauth/disassoc.
Or, at least enable wireless debug logging and see if there’s anything relevant in there when it happens.
See: https://wiki.mikrotik.com/wiki/Manual:Wireless_Debug_Logs
check all details in the wireless Registration table while connected
But in this case it is a client device decision. It will be hard to tell from the AP data why the client decided to go. Timed logging over multiple incidents may learn something from the exact timing.
Yes, not even surprised. The 802.11 wifi standard is complex and has many options and extensions.
Not even talking about the wifi4 (n), 5(ac) or 6 (ax)
Other additions are like 802.11k r and v, about fast roaming. Some Apple devices need them just to have a stable connection.
There is also WMM, almost always activated by default
There is QBSS with additional channel load information , appearance sometimes linked to enabling WMM
There is the lowest broadcast rate (basic rate), and supported rates.
There is group-key renewal, and DHCP renewal
etc etc etc … a lot of options broadcasted in the beacon.
And the client decides on all this.
If you know that QBSS is missing with Mikrotik, and MT does not support 802.11k r/v, and even WMM is not always enabled.
And that users reading this forum experiment with basic rates settings
It happens quite often that the client prefers other brands before Mikrotik.
So if your device is associated to a MT AP, chances are that it will roam to any other brand, as soon as one comes into reach.
There is much less probability a device will roam from another brand to MT.
Other brands have less parameters to set. The system have been tested to operate in the largest possible set of situations.
MT has many parameters to set. Some default values are far from ideal for some environments, and quite some “enhancements” are just missing.
So tuning with MT is a must. The tuning is very static (no auto adjust) so it is mostly valid for one type of client in a specific range.
If the many “disconnects” happen with other brands … you are lost. If it happens with MT you must analyze and tune more.
Makes me wonder: do you actually see any problems with those devices when connected to Mikrotik AP? Some reasons for disconnects, listed in post by @bpwl, will happen on other vendor’s APs as well … but those APs might not issue any log entry for such behaviour as it might be considered normal.
I have problem only with Mikrotik AP, I know it bcs smart devices on mikrotik every 5-10mins are not responding, but on TP-link always responding, I see it trough app and when i use voice commands…
only this repeating:
wlan1: XX:XX:XX:XX:XX:XX attempts to associate
wlan1: XX:XX:XX:XX:XX:XX not in local ACL, by default accept
XX:XX:XX:XX:XX:XX@wlan1: connected, signal strength -60
XX:XX:XX:XX:XX:XX@wlan1: disconnected, received disassoc: sending station leaving (8)
XX:XX:XX:XX:XX:XX@wlan1: connected, signal strength -60
XX:XX:XX:XX:XX:XX@wlan1: disconnected, received disassoc: sending station leaving (8)
Timing between the 2 please, is this 2 sec or 20 min ?
Other check is “Uptime” and “Last activity”.
Uptime: to know how long the connection is valid
Last activity: is to be live monitored. e.g. smartphones in rest make this count up to something like 20 sec , and then restart counting (they go to sleep for 20 sec). Some do drop the signal strength with 20 dB, some others stay on level.
.
.
So if your device is associated to a MT AP, chances are that it will roam to any other brand, as soon as one comes into reach.
.
Please turn off the TP-link while testing, or remove that SSID from the known networks in the devices.
.
time between disconnect and connect is about 2min, and connect between disconnect 5min.
Uptime is around 20hours, last activity is about 10-20s to restart
Please turn off the TP-link while testing, or remove that SSID from the known networks in the devices.
Also I tired turn off all nearby AP other brands, but no changes, still disconnecting
time between disconnect and connect is about 2min, and connect between disconnect 5min.
Uptime is around 20hours, last activity is about 10-20s to restart
Interesting info …
They come back after 2 min. Quite a long time if they wanted to continue.
Connect for 5 min. Any related setting, like DHCP lease time ? (Enable Logging DHCP) Default DHCP lease time is 10 min, lease renewal is after 5 min. If this fails you have disconnect.
Uptime connection 20 hours ??? (Or uptime RouterOS?) How can this be that value for the wifi connection?
Sleepy devices! IOT with transmits every 10-20 sec ??? There is no access-list rule that checks signal strength with “allowed out of range” time ??? Heh not seen in the config.
DHCP renewal has been mentioned several times already! MT has a low 10 min default value for lease time-out. (other brands probably 24h)
As I have been saying, the home wifi bozos at MT should have hired BPWL to ensure a viable WIFI setup and performance from the firmware and better documentation.
