Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: Weaver on July 15, 2018, 06:33:45 AM
-
One of my modems is sulking after I abused it in some way. I did something or other to it and managed to make DNS within the modem work for the first time ever. I don't know how I did it though. I was also trying to set default gateway IPv4 and IPv6 addresses for the LAN interface. Also I tried to get IPv6 fully configured, as it says it has IPv6 capabilities and was showing a valid mac-derived feff link-local IPv6 address on one of the interfaces. I got DNS working by [somehiw] setting a DNS server entry in the modem to point to an IPv4 addresses of my router, a Firebrick. I should be able to also get DNS working in the modem using link-local IPv6 only.
But anyway, at some point the http server stopped working. It still talks to the internet as normal. Telnet works. I rebooted it using the appropriate command in telnet, but that did not fix it. Telnet still works.
Is there a way of recovering it without the nuisance of having to reset back to factory settings?
I have the config backed up of course. I don't have a TFTP app on my ipad, otherwise I believe I could push a replacement config into the modem using TFTP initiated from a Telnet command?
I know I can wipe the device and so forth, but that means a lot of messing around as once it is reset, 192.168.1.1 will not work unless I either temporarily reconfigure the router or ask my poor wife to start swapping cables about twice, which will get me into trouble. So I was hoping there is some slick trick I can use from Telnet.
-
Oh dear. As a fellow scientist, I have to say that you seem to have forgotten the one basic principle for any experiment . . . Change one variable at a time. Hence N variables implies, at least, the minimum of N separate experiments.
I have one suggestion that you could try --
Power down the VMG1312-B10A and leave it in that state for, say, five minutes. Then power it back on.
-
You are of course quite right. In this case, I had no chance though, because there was nothing to tell me that I had actually wrecked the http server at some point by poking around in the CLI. I was just so pleased that I managed to get it perform DNS lookups successfully itself for the first time, goodness knows exactly how.
I have several spares, so the 80%-bricked one is labelled and in the ZyXEL spares cupboard waiting for the next lightning strike. But I really need to sort it out somehow well before that day, otherwise I am bound to simply forget about that job on my list.
-
Our very own Johnson has very kindly inspected the modem and it seems it recovered on its own. What a fool I am. :-[ I should of course have checked what the effect of an extended period deprived of power might do. He is a hero. And what is worse, Burakkucat told me to do this, but I was in such a fuddle that I got confused. So praise due to Burakkucat too.