Forum Discussion

tb46uk's avatar
tb46uk
On our wavelength
2 years ago

Hub 4 in Modem Mode: IP address conundrum

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's avatar
    Client62
    Alessandro Volta
    2 years ago

    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's avatar
      tb46uk
      On our wavelength
      2 years ago

      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's avatar
    jpeg1
    Alessandro Volta
    2 years ago

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

  • Adduxi's avatar
    Adduxi
    Very Insightful Person
    2 years ago

    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 

    • tb46uk's avatar
      tb46uk
      On our wavelength
      2 years ago

       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's avatar
        BrownSauce
        On our wavelength
        2 years ago

        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!

  • Tudor's avatar
    Tudor
    Very Insightful Person
    2 years ago

    "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.

  • Client62's avatar
    Client62
    Alessandro Volta
    2 years ago

    The IP of the VM Hub menu can not be changed from 192.168.100.1 in modem mode.

    However the IP of the Router menu can be changed., so change it to 192.168.100.xxx and resolve the IP clash.

  • sekhonp's avatar
    sekhonp
    Tuning in
    5 months ago

    For accessing the Hub 4 in modem mode via a browser, I have found you need to ensure the URL is HTTP rather than HTTPS. So http://192.168.100.1/ rather than https://192.168.100.1/ . If you just type in the IP address in the browser address bar, the browser may default to the HTTPS address, resulting in a "This site can’t be reached"/ERR_CONNECTION_REFUSED error.

  • frostinel's avatar
    frostinel
    Joining in
    31 days ago

    Try just restarting the router, no reset then try 192.168.0.1 - this sometimes remediates it for me, but not needing to mess with it as its already in modem mode, i dont bother to manage the router in any way

    Also, you can do a full reset as someone said here before and then config it back to modem mode. Mine had major issue at some point and no reset would work to remediate the issue (internet was also down) until i contacted support.