Forum Discussion

thestantons8's avatar
thestantons8
Tuning in
2 months ago
Solved

Hub 5 change DHCP range

Hello all,

Just upgraded from a Hub 3 (DHCP range 192.168.10.10 thru 192.168.10.250) to a Hub 5
My problem is I can't see where to change the penultimate digit of the DHCP range from 192.168.0.x to 192.168.10.x - reason being is I connect to different remote work VPNs and they are also using the 192.168.0.x range, which is causing conflicts.

Yet the DHCP 'Starting local address' only lets me set the final start digit:

 

Is there somewhere else I can change the prefix from 192.168.0.x to 192.168.10.x ?

Thanks

  • thestantons8's avatar
    thestantons8
    2 months ago

    "You can NOT now change the LAN DHCP range on any VM hubs, they are locked down. Your only option is to get your own router and run the hub in modem mode."

    Progress eh? ;)
    Thanks for the reply, shame we didn't know Virgin were removing features before we "upgraded". 
    So I need to spend £80 or so on something like an Archer AX55 Pro to get back the ability to change my local DHCP range. Marvellous, thanks VM.

10 Replies

  • jpeg1's avatar
    jpeg1
    Alessandro Volta
    2 months ago

    https://community.virginmedia.com/discussions/Wireless/hub-5--192-168-0-1--change-ip-range/5457151

  • thestantons8's avatar
    thestantons8
    Tuning in
    2 months ago

    "You can NOT now change the LAN DHCP range on any VM hubs, they are locked down. Your only option is to get your own router and run the hub in modem mode."

    Progress eh? ;)
    Thanks for the reply, shame we didn't know Virgin were removing features before we "upgraded". 
    So I need to spend £80 or so on something like an Archer AX55 Pro to get back the ability to change my local DHCP range. Marvellous, thanks VM.

  • legacy1's avatar
    legacy1
    Alessandro Volta
    2 months ago

    192.168.0.x is well known for years as being used on routers so I blame the VPN admin for using it however gets more people off the router mode thats junk anyway.

  • Client62's avatar
    Client62
    Alessandro Volta
    2 months ago

    A work LAN on any popular domestic IP range a very poor choice.

    What occurs when a Hub 5x is issued, lacking modem mode it is fixed on IP range 192.168.0.xxx

    • thestantons8's avatar
      thestantons8
      Tuning in
      30 days ago

      Some of these companies have used that default 192.168.0.x range for decades, I can't really expect them to change all of their setups including shortcuts, netmasks, permissions etc. just because 1 of their many employees / contractors (me!) has "upgraded" to a dumbed-down, more restrictive hub.
      I've bought a TP-link AX55/AX3000 router to plug into the thicko "Hub 5", hopefully that should make it as flexible as the old Hub 3 - and maybe even make it work better as it will only have the 1 job to do instead of handling DHCP, firewalls and multiple switches.
      With a bit of luck, the signal will be good enough to reach upstairs properly which the Hub 3 never did, hence an old ASUS RT56 is currently hard-wired into the loft, handling the kid's wireless devices :) 

      • legacy1's avatar
        legacy1
        Alessandro Volta
        30 days ago

        192.168.0.x range for more decades was used in routers before companies started to use VPN's 

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

    Don’t forget it makes it a lot simpler with your own equipment when you change broadband providers. Also VM hubs work much better in modem mode, their low powered CPUs have much less work to do.