Sky remotely rebooting routers

[MagicBoy]

For some reason around 0130 this morning my Sky Q Hub decided to restart itself, and I'm not sure why.

I'm a little unhappy as I sim race online, and I was driving with 12 hours into a 24 hour endurance race completed when it suddenly dropped and restarted, which has also screwed my other team mates over. It's the second time the connection dropped in 24 hours, having also gone down around 10am without a reboot.

Here's the log :
Jan 1 00:00:08 syslog: BusyBox v1.17.2
Jan 1 00:00:08 syslog: plc0 (Int switch port: 4) (Logical Port: 4) Link UP 100 mbps full duplex
Jan 1 00:00:08 syslog: [ 6.897000] eth1 (Int switch port: 6) (Logical Port: 6) Link UP 1000 mbps full duplex
Jan 1 00:00:08 syslog: [ 8.941000] eth1 (Int switch port: 6) (Logical Port: 6) Link DOWN.
Jan 1 00:00:13 syslog: [ 13.033000] eth1 (Int switch port: 6) (Logical Port: 6) Link UP 1000 mbps full duplex
Jan 1 00:00:20 syslog: [ 20.129000] Line 0: xDSL G.994 training
Jan 1 00:00:24 syslog: [ 24.133000] Line 0: ADSL link down
Jan 1 00:00:26 syslog: [ 26.237000] eth1 (Int switch port: 6) (Logical Port: 6) Link DOWN.
Jan 1 00:00:30 syslog: [ 30.270000] eth1 (Int switch port: 6) (Logical Port: 6) Link UP 1000 mbps full duplex
Jan 1 00:00:49 syslog: sky dhcpc client (v0.0.1) started
Jan 1 00:00:51 syslog: [ 51.145000] Line 0: xDSL G.994 training
Jan 1 00:01:06 syslog: [ 66.149000] Line 0: VDSL G.993 started
Jan 1 00:01:18 syslog: [ 78.396000] Line 0: VDSL2 link up, Bearer 0, us=9999, ds=40000
Jan 1 00:01:18 syslog: [ 78.401000] Line 0: VDSL2 link up, Bearer 1, us=0, ds=0
Jan 1 00:01:56 syslog: ptm0.1 - WAN link UP.
Jan 1 00:01:56 syslog: Received valid DHCP lease from server. Connection UP.
Jan 1 00:01:56 syslog: Connection Up. SNO/MAC/IP/SWVER: [<redacted>/<redacted>/<redacted>/1.9f.1769.R]
Jan 1 00:01:57 syslog: Send out NTP request to ntp1.isp.sky.com
Jan 1 00:01:57 syslog: Time has been set from ntp1.isp.sky.com
Aug 7 01:37:48 syslog: Received NTP Sync Reply from ntp1.isp.sky.com

Any ideas before I phone Sky and express my displeasure?

[Isitme]

When the connection drops it should not reboot the router, unless it is also updating the firmware. Did your firmware change?

You can express your annoyance to Sky, but I doubt if it will do much good unless it is a regular occurrence, which could indicate a line fault.

[MagicBoy]

Firmware version in the log excerpt above. The Q hub isn't listed on their firmware help page, so I couldn't check it. I've got a hunch they did as the existing log got wiped out.

[speedyrite]

Look here for firmware versions for all Sky routers: http://www.skyuser.co.uk/forum/sky-r...-firmware.html

1.9f.1769.R looks to be even newer than the version rolling out!

Q1: Are you sure that's correct?
Q2: Any idea what it was *before* each of the two previous reboots?

[MagicBoy]

A1: Yes. Here's a screen grab.


A2: Sorry, don't know. If I thought it was firmware I'd have kept track of the version numbers.

[Isitme]

I think that's the answer. Your firmware has been updated overnight. Sky usually do this in the early hours when there is less chance of the connection being used. It's just unfortunate that you were using the connection at the time. The previous drop at 10am would be a simple temporary disconnection which would not cause a reboot..

Maybe other users of your router could have a look and see if their FW has been updated?

[Mystic Eddy]

My Q Hub (or Hub 3.0 as Sky insisted on calling it as I don't have Sky Q) updated last week to the 1769 firmware; so it looks like they're being done in batches.