cancel
Showing results for 
Search instead for 
Did you mean: 

Help accessing modem mode

Mangraviti
Joining in

I'm sick and tired of this modem and I can't find a straight answer to my question.

I run my Hub 3 in modem mode and I have a proper router to do all my networking and VPN.

The VM Hub is said to be on 192.168.100.1.

My router is on 192.168.100.2. It has a range from 100.1 to 100.254.

How in the name of god can I access the modem?

192.168.100.1 simply won't respond.

And if your answer is to set the Hub to router mode, don't bother answering my question.

Does anyone actually know how to do this?

Thanks in advance

 

1 ACCEPTED SOLUTION

Accepted Solutions

FlockWallpaper
On our wavelength

No, contrary to popular belief the hub isn’t on 192.168.100.1 when in modem mode, better described as ‘bridge mode’, that’s the internal web server interface address.

 In bridge mode, the VM hub, ‘passes on’ a public address to your own router’s WAN interface, so you need to set that to be DHCP, or dynamically assigned or however they phrase it for your model. What you set for the LAN-side address is irrelevant really.

See where this Helpful Answer was posted

13 REPLIES 13

asim18
Fibre optic

Try setting your router to 192.168.0.1 instead of 192.168.100.2. Keep range from 192.168.0.10 to 192.168.0.200. This will keep some range free for static IPs if you ever need in future.

If you set your router to 192.168.100.2 with a range from 192.168.100.1 to .254, it will mean your router's DHCP server will possibly create conflicts with the Hub3 at 192.168.100.1

 

Tried that. It doesn't work. I set it to 100.2 HOPING that I would be able to access the modem.

asim18
Fibre optic

Have you tried pinging 192.168.100.1 from a command prompt or terminal?

On some web browsers you need to type the full url "http://192.168.100.1/" otherwise it just searches google for 192.168.100.1.

 

If you are able to ping the Hub's IP, it suggests the Hub is reachable from your network. It points to an issue with the Hub itself.

jpeg1
Alessandro Volta

Set your own router to 192.168.1.1, and DHCP range from 192.168.1.10 upwards.  Many routers already default to 192.168.1.1. 

You can then access the VM Hub and your own router independently. 

- jpeg1
My name is NOT Alessandro. That's just a tag Virginmedia sticks on some contributors. Please ignore it.

FlockWallpaper
On our wavelength

No, contrary to popular belief the hub isn’t on 192.168.100.1 when in modem mode, better described as ‘bridge mode’, that’s the internal web server interface address.

 In bridge mode, the VM hub, ‘passes on’ a public address to your own router’s WAN interface, so you need to set that to be DHCP, or dynamically assigned or however they phrase it for your model. What you set for the LAN-side address is irrelevant really.

Tudor
Very Insightful Person
Very Insightful Person

Ou cannot use the 192.168.100.0/24 subnet for your LAN. This is because when the VM hub starts up its uses very IP addresses in this range. I have previously traced it and seen these addresses.


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2

legacy1
Alessandro Volta

What (not hub) own router are you trying to setup?

Your own router should not use 192.168.100.0/24 on LAN the routers WAN to the hub will get a temp 192.168.100.x then you get one WAN IP if your LAN is 192.168.100.0/24 you will not route past your router

---------------------------------------------------------------

Ping is inaccessible. JUst tried it

This never worked. It was the setup till yesterday. I changed to 100.2 hoping that it`d work.