HDR LAN(Wi-Fi) Settings Mysteriously Corrupted

[/df]

No doubt, but it could be a bad thing to do. The system runs one instance for each network interface. Let's see what leads the WLAN instance to become active.

 

[/df]

Also, get the settop binary to log itself: touch /mod/boot/debugtv.

Then /tmp/humaxtv.log may reveal something.

 

[Black Hole]

Does that need a reboot to take effect?

 

[/df]

Yes. (Well, it needs the S90settop script to run)

 

[Black Hole]

Address flipped to DHCP (and got allocated the wrong thing). A WebIF reboot re-asserted the settings from WebIF >> Settings >> Network Settings.

I went looking for my log and couldn't find it. So I went looking for my script, and both the script and the cron entry have disappeared! WTF? Oh yes, this:

If you remove the opkg-beta package in the näive belief this will allow the non-beta version of ir to be substituted, fix-flash-packages will now be unable to find the correct version of any* beta package (including, potentially, webif), and end up removing those beta packages without replacing them. Two of us have done this and ended up rebuilding our CFs from scratch (not including firmware update, of course). The only packages actually affected by this are ir and webif, and measures set out below can recover the situation without a complete rebuild.

 

[Black Hole]

Restored. Now to wait another aeon for something to inspect...

 

[Black Hole]

Here we are, more than 4 years later (really???), and no recurrence. No idea why, and the monitoring is still running.

Meanwhile, what brought me back to this thread, my supported user complained she was unable to connect to WebIF, so I talked her through checking the current IP address... which had changed. Then, when I was on site, I had a more detailed look and the setting had flipped from manual to DHCP. Sounds familiar.

What I've done in that case is simply adopt the new IP address, made it manual but if it flips back to DHCP it should receive the same address from the DHCP server.