One of my modems has been behaving oddly for a long time. I feel certain that I have unintentionally mucked up its configuration with unwise medical experiments without noticing the effects.
I cannot get it to connect with TCP, or http, with a web browser going to port 80 or 443. It just either sits there for a while before timing out and failing or fails fairly quickly. I am not sure exactly what the protocol sequence is yet as I have not yet got around to capturing a conversation.
I can however telnet to it. It works fine as a modem too.
It is successfully running the latest ‘johnson’ modified firmware, which provides a second http server (stats server) on port 8000. Connecting to the port 8000 http server works fine. I can get a time graph of SNRM, plus all the usual stats reports.
Anyway, I’m wondering about how best to recover it.
I can’t use the web UI to reload a backup config.
I tried to work out how to reload the config using the CLI. I logged in as supervisor, entered the required magic incantation, cfgupdate or whatever it is, but I get rather odd messages after it has swallowed the supplied config XML file, so I am not sure if I am somehow doing things wrong. It seems to just stop eating XML when it gets the closing element, as if it is intelligently parsing the whole thing supplied on the fly, as opposed to requiring the whole file to be delivered first, with a mechanism to define the length or provide a delimiter/terminator marker, and then looking at the content and processing it afterwards. I say this because I tried supplying various control characters after the file content was supplied into the CLI but realised that I did not need to do anything: the messages just come up after all the XML has been entered.
I’m not sure if it is even sufficient to replace the xml config anyway. If I could get it to load up a new config using the web UI, which of course I can’t, or could work out how to do the same thing with the CLI would I possibly need to do more in order to restore sanity?
So, the question: Ideally I would just completely nuke the entire thing and put a known config into it and also a known software image too just in case something went wrong with a previous software installation attempt perhaps.
* Q: What’s the easiest way of nuking it completely? (Would need some very precise clear nuking instructions to give to Mrs Weaver.)
Factory-state reset, starting up into a firmware image-loader state.
Apologies for such a basic question, but I am currently pretty incapacitated most of the time by the pain drugs that I am on. I have been unconscious for more days that not over the last week,