I ran into a very strange and nasty problem this evening with a USG 100. It's installed in a remote location a thousand miles away and it has a UPS on it and one of those iboot gadgets that will cycle the power if it can't ping an address for 30 minutes.
There was a storm and the power went out, which isn't all that unusual as this unit is in southern Florida where it storms a lot. However, this time something odd happened to the router. I think the UPS never ran fully down, even though the internet connection went down (I suspect because the ISP's equipment lost power at the pole), but when it came back up I could login to the router, very slowly, and it wouldn't bring up any screens, just the blue background with "loading" on it. I tried getting in with an ssh session and it too was slow, and then it said "Not connected to ZySH daemon". I wasn't able to issue a reboot command, I wasn't able to do anything with the web gui, all the VPNs where down, and the port forwarding wasn't working so I couldn't get into anything behind the router. However, outgoing connections were working because my Nest thermostat at the site was still giving updates to it's server, and that also meant that the iboot was still able to ping it's address, so it wasn't going to reboot the router.
I finally got in through a back door because the ssh session would allow me to telnet into something on the local LAN, even though it wouldn't allow me to reboot the router or interact with the CLI. I used that to start an openvpn session outward, and from that session I got in and was able to bring up the iboot web page from within the local lan and manually power cycle the router. However, when it came back up it was more responsive, but the web interface main page still put up a little box that said it couldn't connect to the -2 Zysh daemon, or something like that. Fortunately the maintenance screen came up and after downloading and checking the configuration files and comparing them to a backup copy to make sure they weren't corrupt (they weren't), the only thing left to do was to re-upload the firmware remotely and hope that it would come back up afterward.
It all worked, and it did come back up, but this sort of shakes my confidence in Zywall's products for the firmware to get corrupted to the point that it has to be reloaded, especially when this thing was behind a UPS where it shouldn't have been subject to a brown out or a surge.
I'm curious if anyone else has had trouble with the USG or the 110 series with this kind of problem. I have lots of these deployed in customer locations and I've never had something like this happen before. BTW I'm running firmware version 3.30(AQQ.4), and that was the version I reinstalled.
↧