Help accessing modem mode

[Mangraviti]

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

[Mangraviti]

It is currently set to 100.2 (my Asus router) and the connection is working fine. It was previously 192.168.1.1 and I couldn't access the modem by typing 192.168.100.1. I then changed it today hoping that it would work.

[legacy1]

If your subnet is 255.255.255.0 and not 255.255.0.0 your LAN being 192.168.1.0/24 will be fine just reboot the hub 

or its possible your router don't like the DEAD MAC when the hub replies  so test with a PC to the hub in modem mode and reboot

[jpeg1]

For the 12 years I've been using VM Hubs with a router on 198.162.1.1, I've never have any difficulty accessing the VM Hub in either mode (usually modem mode for obvious reasons).  

The only issue is that after changing the VM Hub mode it's necessary to reboot the router.  If it's relevant, I use DrayTek routers.

[Adduxi]

Strange.  I've been using modem mode since the SH2 and never had any trouble reaching the Hub's console address.  Worked on Hub 3 and now Hub 5.  Router on 192.168.1.1  Hub on 192.168.100.1

[dinkybluebug]

Im experiencing the same problem... turned on Modem only mode.... network is all working.  My new router is on 192.168.1.1  but the modem cant be access on 192.168.100.1

any suggestions?

[legacy1]

Test with Edge as other browsers may block HTTP back a year ago I had to tell Edge to make a exception for 192.168.100.1  

Or VM have broken access to 192.168.100.1 by firmware on their new hubs and you must ARP to it high end routers allow this by Virtual interface or you can config a PC with IP 192.168.100.77 subnet 255.255.255.0 and connect to hub directly to get to 192.168.100.1

[dinkybluebug]

Thanks @legacy1

Can you break down this advice a little more with a few  more steps?  (thanks in advance)  Im not a complete technical laggard but I wouldnt know where to start with this advice?

- "you must ARP to it high end routers allow this by Virtual interface or you can config a PC with IP 192.168.100.77 subnet 255.255.255.0 and connect to hub directly to get to 192.168.100.1"

[legacy1]

try here

How to Assign a Static IP Address in Windows 10 or Windows 11 (howtogeek.com)

no gateway needed

likely VM broke 192.168.100.1 for modem mode maybe they think if we can't access it they can't, well we all know thats not true.   

[dinkybluebug]

Thanks for this - what is the significance of an IP address of 192.168.100.77  ?

[legacy1]

because 192.168.100.77 is on the same subnet as 192.168.100.1 so when your PC is connect to the hub in modem mode you will ARP to the hub

Note this  should not be needed as when your router gets a WAN IP when your LAN tries to go to 192.168.100.1 it will go to its gateway then your router will go the VM gateway at which point the hub should see your going to it and reply but clearly something is wrong with the hub to do this unless your router blocks it but likely a problem with the hub.