70M Is SH2 v1.01.29 supposed to have Virgin Media SSIDs?

karma mechanic · 11-05-2016, 10:24

Today I was using InSSIDer for something else and I noticed the 'Virgin Media' SSID that is the exact counterpart to my own 2.4 GHz SSID. Knowing that this was caused by the ill-fated V2.01.03 firmware I have just done a pinhole reset. (Yes, my SH2 doesn't seem to get any updates any other way, ever since the original trial).

This time it did load v1.01.29... I've double-checked.

But I'm still seeing an SSID of 'Virgin Media' that matches my own one in InSSIDer. Same channels, same strength, same rate, the MAC address ends with D3 instead of D0. The VM one is WPA2-Enterprise instead of WPA2-Personal.

So this looks exactly like the behaviour when I was still running v2.01.03 earlier today, but the device info clearly shows v1.01.29. Is this normal, have they changed it, am I going mad?

DJSADERS · 11-05-2016, 19:09

Sounds like the Wi-Fi sharing trial in the Thames Valley network... havent heard about it for a while

karma mechanic · 11-05-2016, 19:34

Yes, mine was stuck on v2.01.03 where they added the hotspot SSIDs. I tried to get it back onto the 'normal' firmware back in November: http://www.cableforum.co.uk/board/35807685-post10.html
...but for some reason it would only reload the version with the hotspots.

Today I tired of this and managed to get it back to v1.01.29 - hooray! But it still looks like this:

My normal SSIDs are 'Vulcan' and 'Vulcan_5G', on 13+9 and 44+48 from the SH2. (The other Vulcan one on 1+5 is from a separate router at the other end of the house).

13+9 also has the Virgin Media SSID that I was trying to get rid of...

General Maximus · 12-05-2016, 08:13

the other way around it is to log into myvirginmedia and opt out of the wifi sharing.

karma mechanic · 12-05-2016, 09:58

Quote:

Originally Posted by General Maximus

the other way around it is to log into myvirginmedia and opt out of the wifi sharing.

Well spotted - I forgot that was still an option. I did it first thing and have since done another power cycle of the SH2, still got the unwanted SSID. I can think of two reasons for that: they aren't updating the config with that because it isn't in use, or maybe it just takes time... (Ok, three reasons, maybe that config isn't pushed to v1.01.29. Mine was restored from a backup file after the pinhole reset).

BTW, the odd SSID that I was actually trying to track down on ch 36 turned out to be the Amazon Fire TV box, it has an AP for the wireless remote.

Kushan · 12-05-2016, 10:59

Quote:

Originally Posted by karma mechanic

BTW, the odd SSID that I was actually trying to track down on ch 36 turned out to be the Amazon Fire TV box, it has an AP for the wireless remote.

Why didn't they just use bluetooth, or the existing Wifi network, like sane people?

karma mechanic · 12-05-2016, 11:37

Quote:

Originally Posted by Kushan

Why didn't they just use bluetooth, or the existing Wifi network, like sane people?

Good point. The SSID is hidden from most things, but inSSIDer sometimes shows it as DIRECT-xx-FireTV-xxxxx.

More on WiFi Direct:
http://www.howtogeek.com/178691/htg-...-does-it-work/

Kushan · 12-05-2016, 16:11

Ahh Wifi direct is a bit different, that makes more sense.