I posted a while ago about this.
I have a home hub 6 that appeared to lose settings overnight. Normally, on the hub, I change its IP, the admin password, network password etc - so, losing the settings means all connections (lan and wifi) stop.
It happened again last night - we had been watch TV via iPlayer, so I know the config was fine up until about 10pm. By 1am the config was 'lost' (my internet radio wasn't connecting and that alerted me) and had been reset to factory defaults. I have reset all the changes and it's working fine again .
But checking the log (which seems to only start at this entry - nothing before) I get what appears to be an error.
I haven't any log entries to compare this to - ie nothing for the previous days so I can check what happens around midnight. Is there a chance that a firmware upgrade is causing some form of issue?
Is it a hardware issue with the Hub6? If so, I think I should have received a new hub when I extended my contract recently (April I think), so can that be sent out?
can you post the hub stats instead of logs - technical log information
there is no longer a new hub provided when you renew your contract and this has been case for good few years. if you hub is faulty then you phone 150 and request a replacement
can you try quiet line test dial 17070 option 2 should be silent and best with corded phone
Is this what you meant by the stats?
as I posted the quiet line test is exactly that when you select option 2 it should be silent apart from the announcement - any noise whatsoever is a problem for broadband ( apart from maybe dull hum from cordless)
OK - if the hub losing config data may be down to a noisy line, isn't there a better 'automated' way for checking for noise on a line that doesn't rely on a 60+ year old's ears and potentially dodgy handsets?
Given that the issue has occurred twice and in both cases overnight when the hub is less active, is it possible that firmware upgrades or other such automated maintenance is potentially involved? This time, the hubs blue light was on - typically my config has the light being turned on at 7am and off at 6pm - so something had changed the config between 10pm (the last time the hub was 'actively' used) and 1am when the internet radio couldn't connect. And it seems from the logs that an update was applied about that date.