Almost all options like hw retries, delay, frame lifetime, etc are available when MT is acting as an AP, but when my MT is in client mode, it tends to be very pedantic about disconnecting from the AP whenever there is small period of loss. It will disconnect with “no beacons” and then fail to reconnect (to a non-MT ap) since the AP never saw the de-associate, so it doesn’t let it re-associate until it drops from data loss / timeout, making what would normally be a quick re-associate turn into a minute or more of connection loss. I find this also happens with my MT clients on MT APs too, the clients will disconnect claiming “no beacons” but the AP never sees them leave.
It would be really nice if there was an option to control how long it waited before dropping the connection during a period of loss, either in time or lost beacons or something. Non-MT clients stay connected just fine, so it does seem to be related to something perhaps over-sensitive in RouterOS.
Check for settings on your AP. Our non-MT APs timeout after a few seconds, not a minute.
On MT, check the Disconnect Timeout setting (in the wlan interface settings, make sure you’re in advanced mode), by default this is 3secs, you can increase this if you wish (but it’s not recommended)
This isn’t an issue with the AP I’m connecting to - it never disconnects me, it’s the MT de-associating when it gets “no beacons”. It then takes the AP some time to realize I’m gone. Unfortunately there doesn’t seem to be a way to speed up the disconnect timeout process on the APs I’m using (old generic 802.11b crap). The disconnect-timeout on the MT to MT connections isn’t needed as the MT is smart enough to realize the client is trying to re-associate without first de-associating and handles it properly. I just wish there was an equivalent of disconnect-timeout for AP Client mode, there are all these tweaks for AP mode but seemingly nothing to help control behaviour in AP Client mode.