RobTheNetworkGuy  Freshman Member

Excellent work! This is much better than my brute force Web UI approach. I'll give a try and reports back.

Fwiw, I made this, and it works to remotely reboot the device from a cron job. It uses the web interface via a headless browser, so it's a bit of a heavyweight and fragile way to do it. But it works for me for now:

My Zyxel modem has been in this state since this morning. Neither of those reconfiguration commands seems to do the trick for me. For turning the APN back to manual you also have to specify --AP_APN <apn> I'm afraid to try the reboot commands at this time as I don't want to reset the whole configuration. I noticed on the…

Fwiw I have not noticed the TCP connection staying up, but it sounds plausible. However, my modem is currently working. I have not seen this problem for over a week, now. I'm sure it will happen again soon.

I raised ticket #363627

SN = S210Z30017009 FW version = V1.00(ABSQ.4)C0

cfg cellwan_mapn edit --Index 1 --AP_Enable 0 to disconnect This worked. The GUI now shows "connection down" under cellular info and in other places. However: cfg cellwan_mapn edit --Index 1 --AP_Enable 1 to reconnect This has had no effect. If I do cfg cellwan_mapn get I can see a table showing that the APN is indeed now…

Why can't I quote just part of a post? Anyway, "Note: if you use pfSense to detect the issue with gateway monitoring, obviously it will disable the route to the router and you cannot manage it anymore... bad idea ;-)" Good point. So I got around it by adding a static route to the admin interface address on the Zyxel. Now…

I wonder if there is a way to do this with a CLI. If so, it could be scripted (at least until a proper fix is made).

Thanks for that insight, MatteP99. I will look out for it. I am back here because it happened again and I did not find out until my wife called me to complain that there is no internet. All this effort and expense to set up failover and this happens… It is my fault that I did not notice the email a few days ago warning me…

9:02 -- I still can not ping the Zyxel modem or access its web interface. However I do seem to be able to ping the monitor address (the DNS server I access via the modem). Tracepath confirms that packets to that address are routed via the Zyxel. I will do more investigation later.

A minor update to this: I changed the monitor address to be a DNS server from my mobile ISP and configured a static route so that these packets are always routed via the Zyxel modem. Eight days later at 7.25am my pfSense router emailed me to say the Zyxel was offline. Unfortunately I can neither ping it nor access the web…

The diagnostic *page* worked just fine. But the pings were not getting responses. I remember that the cellular information made the connection *look* healthy, but there may well have been a clue that something was wrong. Unfortunately I did not record the full contents of the pages before I just tried rebooting. If it…