WISP Bug

[SySOPik]

Hello everyone. I noticed the following bug on the latest firmware, in WISP reserve (on demand) mode: it does not connect to the access point launched from a mobile phone. If you reboot the router, it connects immediately without changing the settings.

For example, if the main Internet disconnect, the router switches to reserve WISP, if it is active wi-fi network. If you launch the access point later, the router does not see it or does not want to connect for quite a long time. 

Maybe there are any ideas on how to do it without rebooting the router?

[Padavan]

Hi.

We need more info:

• device model
• syslog - before reboot (WISP can not connected)
• syslog - after reboot (when WISP done)

[SySOPik]

Hello. I will try to make logs if the problem occurs again. Unfortunately, I could not do it now, since all the routers are located remotely, and workers in remote locations are not specialists. Most often, KN-‎1111‎ and KN-‎1311 are used.‎
P.S. I was inattentive, i found the timeout settings in the WISP mode (on demand mode), set it to 30 seconds, I will see if anything changes.

Edited July 17 by SySOPik

[Padavan]

Yes, new FW support timeout, because WISP share one radio resource with AP. WISP perform a site-survey during connection and AP usability is degraded.

[SySOPik]

The situation repeated itself. The main PPPoE Internet dropped out. Remote workers started an access point on the phone to sharing the Internet. The connection did not occur for more than 10 minutes, although the timeout settings are set to 60 seconds. I managed to connect in a roundabout way and save the log when there is no Internet and after turning off and on the Wireless ISP switch (without rebooting the router, since turning off and on the point menu item solved conecting).

PS. I don’t understand how to attach logs so that only developers can see them. I am attaching the logs in the message, and they are visible to everyone.

Edited July 19 by SySOPik