Until now I've been using some non-OpenWrt routers and I've discovered a problem when using WISP mode. Apparently when the WWAN interface switches from one access point to another (same SSID), it doesn't automatically relaunch the DHCP client and, based on the restrictions set by the network administrators in one case, the packets sent to the new access point are marked as "orphans" and are dropped. I know this might not happen since this is very specific for this installation but I need a solution for this.
My idea was to replace our previous routers and use one that runs OpenWrt. So my question is, is this something that can be forced somehow in OpenWrt? Or to put it in a different way, is this mechanism enabled by default? (I'm talking about forcing the DHCP client of the WWAN interface to be restarted on every AP switch).
Such a behaviour is expected from all wireless clients in order to support roaming.
You can specify the BSSID so the client will not connect to another AP.
Another solution from the top of my head is to run watchcat to detect wan inactivity and restart the interface.
Maybe more complicated solution is to somehow detect the wifi reconnection in hotplug and trigger the DHCP.
I took a quick look at the watchcat script here and it looks quite simple. In general it does what I'd expect from an interface monitor but I'd add some retry mechanism to avoid unnecessary interface restarts. Since the code is there, I guess I can install the package and later modify the script manually through ssh (I'll do some tests before). In the end it only requires some minor changes in the function watchcat_monitor_network.
Ok, I finally received the router and after doing some tests with watchcat, there's no need to modify the script, the web frontend offers everything required to do what I wanted with the proper configuration, thx.