Virgin media superhub - Should I grab a wireless router and set it to modem mode?

Associate
Joined
14 Feb 2015
Posts
474
Location
Scotland
So I am on the 50mb service with the superhub. I keep getting slow downs and my superhub keeps resetting itself from time to time which then enable default wireless SSID so nothing can connect.

Would getting a cheap wireless router and set the superhub to modem mode fix this?

Anyone with any experience have any ideas?
 
Possibly, possibly not.

First things first I'd contact VM and tell them it's duff and you want a new one.
 
So I am on the 50mb service with the superhub. I keep getting slow downs and my superhub keeps resetting itself from time to time which then enable default wireless SSID so nothing can connect.

Would getting a cheap wireless router and set the superhub to modem mode fix this?

Anyone with any experience have any ideas?
Setting it to modem mode and getting a wireless point didn't fix it for me. At first they wanted to charge me for the new version of the superhub but after going though 4 superhubs all of which kept resetting they gave me one of the new ones for free. That fixed all the problems.

EDIT: If you get a replacement hub use the new power supply. Sometimes the old power supply can be what is causing the resets. Try and talk them into upgrading the Superhub not replacing it for an old version.
 
Last edited:
Setting it to modem mode and getting a wireless point didn't fix it for me. At first they wanted to charge me for the new version of the superhub but after going though 4 superhubs all of which kept resetting they gave me one of the new ones for free. That fixed all the problems.

EDIT: If you get a replacement hub use the new power supply. Sometimes the old power supply can be what is causing the resets. Try and talk them into upgrading the Superhub not replacing it for an old version.

I have found it resets mostly when im downloading at full speed, i wonder if maybe i need an angineer out to have a look at my power levels also......

Might be worth a call
 
There's no point in spending money on anything until you've gone through VM to be honest.
 
Give Vermin a call, its probably the psu on the hub, I've had similar problems and they usually send out a new plug.

Although they are rubbish routers so if you wanted a stable network with a half decent wifi range, getting your own router is essential anyway.
 
Ok well an update for anyone with a similar question in the future.

I installed my old trusty Linksys WRT54GL (with Tomato firmware) alongside a gigabit switch, enabled modem mode on the VM superhub and damn my whole network is 100% stable and much faster.

Even wireless is faster, not sure how as the WRT54GL is a 10 year old router.

Overall the whole network is faster and even browsing seems to be snappier. Maybe my superhub was faulty or its just a piece of garbage......
 
Some more testing and I really cant believe how well this little WRT54GL is standing up, I would recommend anyone with the superhub to try this if you have spare equipment as I just cant believe the difference in browsing pages such as Reddit, no more waiting for things to load.
 
Ok I have a slight problem now (sorry for 3 posts in a row) but if anyone that uses the VM hub in modem mode could tell me if they can access it view the ip VM state (192.168.100.1) then i would be interested.

I cant seem to access it at all no matter what i do. Its not really a massive problem but its niggling me.
 
If the router and the Superhub are both on the same subnet I can't see it ever working. The router will see any address in that subnet as local traffic and it won't go out via the gateway to where the Superhub is connected.

I've always assumed that you usually left the router using it's default subnet (usually 192.168.0.0 or 192.168.1.0), and that the reason the Superhub's ip changes is to avoid a clash.

When I last had a Vigin connection they were still using dedicated modems so I could be missing something.
 
If the router and the Superhub are both on the same subnet I can't see it ever working. The router will see any address in that subnet as local traffic and it won't go out via the gateway to where the Superhub is connected.

I've always assumed that you usually left the router using it's default subnet (usually 192.168.0.0 or 192.168.1.0), and that the reason the Superhub's ip changes is to avoid a clash.

When I last had a Vigin connection they were still using dedicated modems so I could be missing something.

Actually i think that made me realise what i did, my preference has always been for 192.168.100.X instead of 192.168.0.X for my network so I just automatically assigned that which means I wont be able to see the superhub, no problem really as no options are available.

Makes sense now.
 
Back
Top Bottom