Thanks for the explanation, though in my setup, the ping check times out even though there s connectivity to the internet. I end D up changing the ping check to my ISP's DNS servers ( only 5 hopes away and not about 30 with google.de/meteobridge.comSnapper wrote: ↑Sat Feb 02, 2019 10:33 amOk, done some further investigation on this.
In normal events, the 5 minute check will check connectivity and if the ping check fails, it restarts the networking stack.
This will recreate the provisioning SSID as it brings up ra0.
I confirmed this by blocking pings through my gateway.
Actually this is good behaviour - if there are connectivity issues, then I would want the provisioning SSID to be restored in case there are other issues.
The 30 minute no-ssid.sh event will take it back down again next time it runs though.
In normal events, the 5 minute check passes the ping check and the provisioning SSID does not get restored.
I now don't get the time outs. Only issue is, if the Nano is rebooted the test5m.sh is reverted back to its default state and then I get constant timeouts and connectivity resets all the time.