WAN interface can fall back to LAN state only when link status changes. LAN interfaces get locked to LAN after 1h and then change only when link status changes.
So depending on what was going on when, they get “stuck”.
I find the same issue happens to my AC2 router since yesterday, it unable to turn on detect internet even after I tried to reboot the router. Some users from Vietnam also face the same issue.
Yes, best solution every time is to disable “detect internet”, it provides no useful function.
It is easy enough to maintain the WAN and LAN interface lists manually.
No it does not get back to correct state after a reboot. Oh I tried port 3000 and it worked, and I tried 30000 now and it also works. However, Internet detect is not working, no interface is set to internet anymore.
Yeah, I am only using it because for some reason I can’t make the router use a route with a distance higher than the main route. It will just ignore the interface completely. Even if I have it set in a routing table, with no other route. If the route on main has a distance that makes it not the active one then the routing table will be ignored and data will be sent over the main route somehow.
So in a frugal attempt to sort this out I have firewall rules that only nat data that is sent thru the interfaces that are part of the “internet” list.
I’m not sure the “internet” state part is working right either (at least after one test this AM). Basically I don’t see it’s going to “internet” state when it should. On a RB1100Ahx4 with v7.12rc1, that has a static public IP and very basic config for containers testing.
Now, /ip/cloud shows the correct public & seem to work… But detect internet does do “wan” detect, but not “internet”, as would be expected in my case. Now…if you don’t have a public IP…then whether it go to “internet” depend on upstream NATing…
My only use case for it is so Mikrotik App’s “Internet Status” screen shows up correctly to end-users using the iPhone app. And app show “wan” state as “limited availability” while “internet” state gets “available” displayed. Since the “detect internet” feature is so prominent in the app, I’ve been forced to deal with it & it’s always been problematic.