When adding a new repeater, if you enter the wrong password for one of the selected AP’s, the router will try to connect over and over trying to make a bridge, even though the password is wrong. Because of this, it becomes impossible to connect to the router via wifi.
If the saved repeater has for some reason changed its channel (Asus routers for example can scan for congestion and change their channel when needed automatically) then the same as above happens, the router tries to make a bridge and can’t because the AP is now on another channel, fails, and retries over and over blocking wifi.
The solution for the 2 problems above is to 1, fail and disable the AP if the password is wrong, so it does not try to connect many times. Second, on scan of AP’s, make sure the saved AP is on the same channel as before, if not, update the channel and THEN connect.
If the saved repeater has for some reason changed its channel … then the same as above happens, the router tries to make a bridge and can’t because the AP is now on another channel, fails, and retries over and over blocking wifi.
What worries me about this is what about corporate/hotel/etc. situations where there’s many AP with the same SSID spread among many channels; does this mean that once the AR-750 (et al.) have associated with a certain AP, they’re now bound to that AP, and won’t roam (in case of better signal strength or thruput, etc.)?
I think that is what would happen with the bug. At least from testing at home, changing the channel, the SSID even in the config “/etc/config/ssids” was stored with a fixed channel, and would not connect to any other.