Superhub Weird behaviour and wifi problems in the last few months

G4v1n · 04-11-2015, 15:37

I've been getting wifi dropouts at the rate of about 1 or so a week for the last couple of months. The wired network ports are fine but I find that when I try to make a wireless connection, it doesn't succeed (or even see the wifi network) even though things already on the wireless connection stay working .. at least, until I disconnect and then try to reconnect them at which point they also completely lose the wifi network.

Also, I'm seeing lots of activity on my network and wifi (LEDs on the Superhub flashing like crazy all the time), even when I'm not using it.

Seems to coincide with VM adding a 'Virgin Media' network on to my hub as part of their plan to roll out hotspots all over the country. Though even when I opted out on my account settings page and rebooted, the hotspot is still there coming from my Superhub.

Has anyone else been seeing this or is it likely just a case of the Superhub hardware getting flaky and me being paranoid?

EDIT: Also, should add that I'm seeing the green light blinking on my V+ box and it unable to connect to the VoD services frequently too. In both cases, the problem is solved (for an indeterminate amount of time) by rebooting the affected VM hardware.

jb66 · 04-11-2015, 15:40

There is a firmware bug on the hubs with "Vigin Media" showing as an SSID. I believe thats why they cancelled the rollout

G4v1n · 04-11-2015, 15:43

Quote:

Originally Posted by jb66

There is a firmware bug on the hubs with "Vigin Media" showing as an SSID. I believe thats why they cancelled the rollout

Gah! Any way I can get the firmware downgraded? I seem to be stuck with the 'Virgin Media' SSID co-existing on the same frequencies as my home WiFi network even though I've opted out.....

General Maximus · 04-11-2015, 16:41

Quote:

Originally Posted by G4v1n

Gah! Any way I can get the firmware downgraded?

that was done automatically weeks ago. If you look at the shub you should see:

Software Version V1.01.29 (for a shub2)

G4v1n · 05-11-2015, 09:48

Quote:

Originally Posted by General Maximus

that was done automatically weeks ago. If you look at the shub you should see:

Software Version V1.01.29 (for a shub2)

Yeah, that's what I see. I still have the 'Virgin Media' SSID active on the same band as my own 2.4GHz Wifi though and it's causing my old Samsung Tablet to throw a fit when trying to connect.

General Maximus · 05-11-2015, 13:15

I feel like a dick for saying it but it is the simplest way to fix it and avoid all future problems: put the shub in modem mode and buy a proper router

Stop It · 05-11-2015, 13:21

Or failing that, try a Factory Reset?

karma mechanic · 13-11-2015, 09:49

As of this morning I've now got the Virgin Media SSID on my SH2. It wasn't there yesterday, I would have noticed since I was trying to diagnose something else. The log shows that it rebooted yesterday evening. The SSID is on the same channel as my own SSID, although Wireless Analyzer and inSSIDer both show it as slightly differing strength and security settings.

The SH2 is running V2.01.03, no amount of reboots will shift it back to the earlier firmware. (It got V2.01.03 when I did a factory reset a while back - it seems my hub never gets the pushed firmware updates).

So, another factory reset required I think.

Stop It · 13-11-2015, 10:08

Quote:

Originally Posted by karma mechanic

As of this morning I've now got the Virgin Media SSID on my SH2. It wasn't there yesterday, I would have noticed since I was trying to diagnose something else. The log shows that it rebooted yesterday evening. The SSID is on the same channel as my own SSID, although Wireless Analyzer and inSSIDer both show it as slightly differing strength and security settings.

The SH2 is running V2.01.03, no amount of reboots will shift it back to the earlier firmware. (It got V2.01.03 when I did a factory reset a while back - it seems my hub never gets the pushed firmware updates).

So, another factory reset required I think.

I'd be calling VM for a replacement, just because that Firmware is an utter duffer.

karma mechanic · 13-11-2015, 10:16

Well, I just did a factory reset via the menu, and it ended up on V2.01.03 with a VM SSID.

So then I tried a pinhole reset and it reloaded V2.01.03, the VM SSID is still there. Could it be that V2.01.03 is now the default?

As it happens it isn't causing any problems at all for me and the range and speed is fine, I just wanted it back the way it was

I will keep an eye on it.