SuperHub2 modem mode
I am a (relatively) techie person, although my job isn't working with networking kit in an IT environment, and I have a SuperHub2. I dearly dearly dearly wish that I could have just kept my little dinky VM modem with my own router, but VM tell me that they "aren't compatible with speeds higher than 20Mbps" for some reason. I can't work out whether that's just the party line their helldesk folks have been told to spin (surely they're all DOCSIS3.0 compatible?) or whether there is some technical element of truth to it... I'd be interested if anyone knows the truth.
Onto the 'Super' Hub 2. Modem mode on mine simply refuses to work correctly. When it was installed, once it had been proven to be working correctly "as-is", the first thing I did was flick it into modem mode to use my D-Link DIR645 with it... and nothing. The 'modem' wasn't assigning a WAN IP address to the router. I found this odd, as the router itself had been functioning perfectly fine an hour beforehand with my old dinky VM modem:
- Tried swapping cables, just in case. Nothing.
- Tried plugging the 'modem' directly into a machine to see if the machine would get an IP address... it timed out and assigned itself a 169.xxx IP address. Obviously: nothing.
- Reset the Hub at least five times while trying various things. Nothing.
- Tried various combinations of cables, networks cards, boxes, machines and both router and 'modem' settings. Nothing.
- Hit the VM forums for some support, and got the usual nonsense from their 'Technical' support people (i.e. power cycle it; do a software reset etc. - all the stuff I'd told them I'd already done.)
Eventually decided to run the SuperHub2 as a router for a week and try again. Still nothing, although some random software update turned up in the logs, but wasn't installed as the security hash was for the wrong bit of kit. At this point I start wondering if I've maybe just been unfortunate and got a bit of kit borked from the factory - I suppose these things can happen now and then.
Got fed up, phoned VM Helldesk - who were surprisingly sanguine about the entire affair. Explained what I'd done, and was told immediately that they'd replace the unit - I didn't even have to power cycle the damned thing while I was on the phone.
Engineer turned up and replaced the unit and had basically the same problems again. (Full disclosure - it did, on first turning modem mode on, give the router an IP address, but then it seemed to pull down some kind of software update which borked it again.)
The engineer, bless him, was very helpful and tried all sorts of things while I was there, but we eventually ran out of time - and to be fair to him, it worked flawlessly (for small values of 'flawless') when in router mode. He seemed to think it could be some form of incompatibility between the Netgear SuperHub and the D-Link router. Not sure what to think about that - I know in the bad old days this could happen between different manufacturers, but one would hope that the various firmware IP stacks would have been able to talk to each other over an apparently standard protocol by now!
So, the upshot is I'm currently sat using the SuperHub as VM intend - as a router. As it seems to work well at my house and I can get a decent signal from it in every room, I'm tempted to just leave it as-is. Might give it another go once the new firmware update comes out, but it's annoying. My only other consideration is whether to hit eBay and buy an old Cisco router / VPN tunneller so I can route a lot of my traffic through a VPN so I don't get hit with throttling for having the temerity to use my 'unlimited' internet connection to stream video using the TorrentStream protocol.
Anyone on here got any thoughts or similar stories of woe? If anyone has any potential solutions I'd be interested to hear them.