No lease for 11 hours from last night?

[needmoreTCAM]

Model: SR203

Firmware Version: 7.02.0501.R

DSL Firmware Version: A2pvfbH043p1.d26u

Events are ordered chronologically ->

2023 03/20 02:21:58 syslog: No lease renewal received
2023-              02:21:59 syslog: ptm0.1 - WAN link DOWN.
2023-              02:21:59 syslog: DHCP lease expired from server. Connection DOWN.
2023-              02:22:25 syslog: Voice IP Connection Down
2023-              02:22:25 syslog: WAN IPV6 DOWN
2023-              02:22:28 syslog: Voice Disconnected
2023-              02:28:57 syslog: Administrator login successful from IP: 192.168.1.4

tshark capture shows DNS redirecting to a 10.10.x.x? Failsafe?

Power unplugged for 5 mins, power back on

Router boots but is in its pre NTP mode and all 1970's, dhcp daemon starts but does nothing, no NTP query sent.

2023 03/20 12:37:15 syslog: Received NTP Sync Reply from ntp1.isp.sky.com

Only this morning when I rebooted it again did I make the queries it needed, which is obivously not acceptable from any ISP. Downtime from the Sky WAN int has been little over 11 hours.

This is combined with previous router issues when I set the thing up, that I emailed sky about. The router wouldn't accept my gateway changes (I use x.x.1.1 not x.x.0.1) and the bloody thing kept rebooting itself BACK into its x.x.0.1 default... all my Layer two and Layer three onward uses x.x.1.1 and this caused me a right headache, sky support wouldn't help me because my mother hadnt setup a password. So I had to fix it myself, which only makes me think it could be an EEPROM or other silicon problem, its reminiscent of forgetting to copy running-config startup-config on Cisco devices.

Nonetheless, some help on this would be appreciated. 11 hours downtime and only back up with intervention is not acceptable... I do have LTE support, but my point still stands.

also your filter blocks timestamps as phone numbers.

73

[Chrisee]

@needmoreTCAM loss of connection at 02.30 is not unusual as both Sky and Openreach do network maintainance overnight, update firmware etc.  However generally the system comes back online before 5.30 am or so. Not sure why yours did not so keep an eye on it if it repeats it could be a dodgy hub. The time reset is normal after a restart when it returns to a standard unix start date until it gets a time setting from the time server.

Loss of service in the early morning hours though is as unavoidable as overnight road works etc. Doesn't happen frequently but cn continue for a week or so if an upgrade is ongoing. 

[needmoreTCAM]

I know, this doesn't help. The issue is pretty clear as a faulty hub, if I wasn't bound by the AUP I would take it apart and probe it.

But alas, consumer rights were dead years ago.

[jamesn123]

@needmoreTCAM 

11hrs downtime is acceptable within your agreed contract SLA of 3-5 working day fix time from Openreach.