Superhub : Multiple Subnets with Virgin Superhub?

[tbennett300]

Hi



Does anyone know whether it's possible for the Virgin Media superhub to allow traffic from inside the home network that does not originate from the 192.168.0.0 range, or any range other than teh one the superhub itself is located on? At home I have a server on the 192.168.0.0/24 network that is multihomed, having a second interface on 192.168.1.0/24. This box is a Windows Hyper-V server that acts as an internal router for the virtual machines it hosts, where the virtual machines typically sit on the 192.168.1.0 network. This used to work just fine on my old router, which was a non-Virgin Netgear router (which connected to cable via the Virgin modem) but it won't work now, since having the superhub installed.


I read an article somewhere that seemed to suggest that the 192.168.1.0 subnet would not be allowed because it's reserved for one of the guest networks on the SuperHub. In that case, whould it just be a relatively simple fix by changing my network from 192.168.1.0/24 to, say, 192.168.10.0/24, or whatever else?



Failing that, the only easy way I can see (in theory) is to plug my old router back into the network and plug the Hyper-V server into it, and have all internet traffic flow through that, NAT'd out onto the 192.168.0.0 network and out through the Superhub. Unless there's an easier way?



Thanks
....

[pip08456]

Originally Posted by tbennett300

Hi



Does anyone know whether it's possible for the Virgin Media superhub to allow traffic from inside the home network that does not originate from the 192.168.0.0 range, or any range other than teh one the superhub itself is located on? At home I have a server on the 192.168.0.0/24 network that is multihomed, having a second interface on 192.168.1.0/24. This box is a Windows Hyper-V server that acts as an internal router for the virtual machines it hosts, where the virtual machines typically sit on the 192.168.1.0 network. This used to work just fine on my old router, which was a non-Virgin Netgear router (which connected to cable via the Virgin modem) but it won't work now, since having the superhub installed.


I read an article somewhere that seemed to suggest that the 192.168.1.0 subnet would not be allowed because it's reserved for one of the guest networks on the SuperHub. In that case, whould it just be a relatively simple fix by changing my network from 192.168.1.0/24 to, say, 192.168.10.0/24, or whatever else?



Failing that, the only easy way I can see (in theory) is to plug my old router back into the network and plug the Hyper-V server into it, and have all internet traffic flow through that, NAT'd out onto the 192.168.0.0 network and out through the Superhub. Unless there's an easier way?



Thanks
....

That should work.

[tbennett300]

Thanks for the reply.

Tried changing the source IP just after posting (used a 10.0.0.0 address) but unfortunately that didn't work. Will try the old router idea and feed back the results.

Thanks

[tbennett300]

OK, using my old router and NAT'ing the traffic out through it onto the 192.168.0.0 network then via the Superhub worked and I can now access the internet through other subnets, provided they all go through my old Netgear router first. What a ballache. Virgin need to sort that out for advanced users.

[Ignitionnet]

The Superhub isn't for advanced users. The upcoming modem mode will allow you to use your own router behind it and will have it just bridging. That's about the best you'll get, the odds of having support for multiple subnets, VLANs, etc, in the Superhub are nil.

To be fair though that's probably for the best given the problems with the basic functionality.