Hub 4 in Modem Mode: IP address conundrum

[tb46uk]

Hi, I am struggling to identify my Hub 4's IP address.  The network is set up with the Hub in Modem mode.  The third-party router, however, has claimed 192.168.100.1 for itself, and it consistently answers its HTTP call.  I tried 192.168.0.1, and any obvious variation by the Hub is quiet.  The network is quite stable, and the Hub is working fine.

I looked into the router's WAN details, but it is not obvious what Hub's IP address is in its current state.  I even tried connecting the computer with the modem via ethernet in case it forced it to respond to the usual IP call, but I am getting nothing.

There must be a way of knowing what the Hub's IP address is in its current state, right:? Please help if you know.

Thanks

[Client62]

In Modem mode any VM Hub will have its menu at 192.168.100.1

If this clashes with the IP of your router, it suggests your router has not taken a DHCP IP from the VM Hub.

Any chance your router is set in Access Point mode ?

[tb46uk]

Thank you.

No, I reconfirmed the router is not in AP mode.  It serves as the DHCP assignor for LAN and WAN.  Any chance it has taken over and assigned an IP to the modem itself? Would that be precedented?

...It is very strange no?

The Hub is in sold green light.  They seem to be working well together, I just do not know how to access the Hub.  192.168.100.1 is proudly answered by the third party router. 

[jpeg1]

You need to set your own router to something other than 192.168.100.1.

[Adduxi]

I would suggest a pinhole reset on the Hub 4, set it back into Modem mode and confirm.  Then power off the Hub 4.

Reset the Router and make sure it is setup as DHCP (Automatic IP) and switch it off.  Then connect the Hub and Router with a Cat 6 cable. Switch on the Router and leave it to settle, maybe 10 mins or so.  Only then, switch on the Hub and let it settle as well. 

Your Router should get a WAN IP, and it's LAN IP address should be one of the common one's, e.g. 192.168.1.1

The Hub should be accessible at 192.168.100.1 

[Tudor]

"It serves as the DHCP assignor for LAN and WAN" It should be a DHCP server for the LAN and a DHCP client for the LAN. It must not be a DHCP server for both.

[legacy1]

what own router do you have?

[tb46uk]

 Hi, I am reluctant to reset the system as it works fine.  I wanted to find out what is the IP address of the VM Hub as its expected IP call as the modem is being used by the router itself.  If, in the future, I need to reset the network, I will be sure to follow your advice.  Thank you.

[BrownSauce]

Strictly speaking ‘modem mode’ is a bit of a misnomer, it’s better described as ‘bridge mode’ ie it bridges the DOCSIS cable connection to your own router’s WAN interface. In this state, the hub doesn’t really have an IP address as such, what it does, is request a public address from VM’s DHCP servers and passes that on to your own router.*

So your own router gets a WAN IP address of say, 87.x.y.z, and a trusted (LAN) address of, well whatever you configure it to be - often they are 192.168.x.1, where x is usually 1 or 0, but can sometimes be something like 10.0.1.1, if you can tell us what model of own router you have, we can probably be of further help.

The 192.168.100.1 address is NOT ever the hub’s address in modem mode, rather it is a ‘management address’, ie an address on which the built in web server is listening on and can respond. In normal circumstances, if you try to go to this address from a PC on your local network, the PC will recognise that this address is not part of your local subnet and pass the request ‘upstream’, the hub recognises it as an address it knows and responds with the web interface.

In your case, it does sound as if, for some reason 192.168.100.1 is on your local subnet, hence the message gets responded to by your own router and doesn’t get passed up. Like I said, there is no other hub address, in this situation, it won’t be possible to access the hub’s web interface unless you reconfigure the LAN-side network addressing to not use this subnet; which may be more trouble that it’s worth!

[tb46uk]

Thank you for the explanation.  The router is by QNAP (@legacy1 had also asked).  

So, would it be possible for the router to assign an IP to the virgin Modem / bridge? Currently it is as if the VM Hub is a non-entity in the QNAP network topology.  Yet all connected devices get assigned an IP, right? Might the router have assigned the VM Hub with an IP? Why can't i see in the topology that ahead of the router there is this bridge or modem? If i did not know my set up  and only relied on the schematics of the dashboard of the router, it is standing directly in front of the internet.

Does the Hub cease all logging activity once in modem mode? I have always found its logs quite useful when it was run as the router and would like to accesss these again if possible.  Also, i wanted to be able to monitor any cable signal issues and stay on top of any firmware updates.  These are some of the reasons that i started trying to get to its dashboard in the first place.

I must say, however that i used to have never ending problems before, with the Hub as router or with the Hub in modem mode and Netgear or Linksys various routers. This pairing now has been the most solid tried in the last three years or longer.  

So what is the social paradigm we can extrapolate from this situation? Do we learn from this, that the secret to a succesful working partnership is not collaboration but total dominance by one party that ends up taking over and denying the other partty its very own identity...!!! (lol)  

😃

Thanks

Thanks