Forum Discussion

VsUK's avatar
VsUK
Dialled in
3 months ago

Modem Mode Hub 3.0

I have Virgin with the Hub 3.0, as does my ex wife for the kids. Now, I set mine up as modem mode with the connection going into a good wifi router which gives me good speeds with long distance signal without any interference, which shares the connection using a PlugnPlay desktop switch & it all runs like a dream. So, my kids wanted the same so I set up the same system, hardware for the ex wife & all runs smoothly. 

Now, my ex brother in law wanted the same recently, so I ordered the same hardware & set it up exactly the same way on his Hub 3.0. The only problem is, I can only get internet if I connect the Hub 3.0 in modem mode directly into my laptop or into the desktop switch & into my laptop. I can not get it to work with the router. I've even been trouble shooting to the extreme. I took my 3rd party wifi router which works for me, connected it to his Hub 3.0 & nothing, same with the ex wife's router, nothing. 

I've put the Hub 3.0 back into normal mode & it works but it has its issues with reliability of wifi & the modem just bugging out requiring a power off/on. It's just the modem refuses to give any internet, it won't even let the routers know the IP or dns at all. But as soon as I unplug it from the router & into the laptop, we have internet. 

So, short of throwing the Hub 3.0 through the window, because its not mine or my window, what am I missing? I've tested all the LAN ports, all working. All cables working. All 3rd party routers working, even so far as testing the ex brother in law on mine & the ex wifes & it detects & functions as intended. So what am I missing? Could Virgin be blocking 3rd party routers out of spite or something or could it be a Hub 3.0 issue?

6 Replies

Sort By
  • Adduxi's avatar
    Adduxi
    Very Insightful Person
    3 months ago

    In modem mode the Hub only supports a single Ethernet cable and that cable needs to go to the 3rd party Router.  Any other connections, e.g. switch, need to be connected to the Router.  Reset the Router first and make sure it is set for DHCP.  Power off the Hub when in modem mode.  Connect the Router and switch it on.  After the Router has settled, power on the Hub.  The Router should now get a WAN IP. 

    • VsUK's avatar
      VsUK
      Dialled in
      3 months ago

      Hi, ty for the reply. Yes I'm aware of the 3 disabled ports 2,3 & 4 when you go into modem mode. And the switch isn't the issue, I've connected it directly to the 3rd party modem as well as via switch. If I plug the Hub 3.0 into the switch, then switch into my laptop it works. But not into the 3rd party router. 

      I've reset & powered off, testing everything I can think of for 6 hours. The router isn't the issue, because as I said, I plugged it without configuring into my hub 3.0 in modem mode & it works. I've plugged mine thats working into my ex bro in-laws & it doesn't detect the internet. I've set DHCP, dynamic IP which it is & it fails to detect. But it works if the Hub 3.0 isn't in modem mode. 

      • Cardiffman282's avatar
        Cardiffman282
        Wise owl
        3 months ago

        It sounds faulty. I assume you have pinhole reset the hub. Failing that either sling it out the window or suggest your ex bro in law complains to VM that the Hub is not fit for purpose. 

  • legacy1's avatar
    legacy1
    Alessandro Volta
    3 months ago

    The problem with TP link is they use DHCP Bootp flags Broadcast flag which VM may block in some areas which is not the a hub problem (unless ACL to do so) but VM DHCP server their are ways to test this if you can run Registry Editor on laptop

    go to

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{Your NIC key}

    add new Dword (32 bit) value

    DhcpConnForceBroadcastFlag set to 1

    DhcpConnEnableBcastFlagToggle set to 0

    reboot and try

     

  • legacy1's avatar
    legacy1
    Alessandro Volta
    3 months ago

    I fact its very likely VM have put a ACL on given hub in given areas for inbound block for Broadcast stopping TP link routers from working which is stupid there is nothing wrong  with DHCP Bootp flags Broadcast.