Forum Discussion

clockworksatan's avatar
clockworksatan
Tuning in
7 months ago

Hub 5.0 DHCP Issues

I just upgraded to the Hub 5.0 on VM's 1gig connection.  I previously had the Hub 3.0 and had to switch it to modem mode as its WiFi was quite frankly rubbish, and I was hoping that the new Hub would be a vast improvement.  Initially, I was impressed with the WiFi speed (I even said 'wheee' when doing a speedtest), but when it came to me trying to assign a static IP to my NAS, I keep encountering an odd issue.  

When I go into the DHCP settings and select my NAS, it displays the following:

It doesn't matter what IP address I put in there; it always says that it's not a valid IP address.  I mean, wth?  Don't tell me that this shiny, modern router doesn't in fact have basic router functionality?  Anyway, I called VM this morning to see if they had any words of wisdom, but the rep on the other end of the phone was completely useless and didn't seem to have the slightest clue what I was talking about. 

From the posts I've seen on this already, I gather that there's no fix for this and I've not missed anything obvious?  I've got a feeling that I'm going to switching this new hub to modem only too, which is annoying as the router I've got isn't a WiFi 6 one.  

9 Replies

Sort By
  • Client62's avatar
    Client62
    Alessandro Volta
    7 months ago

    Hub 5 DHCP has always been as flaky as chocolate.

    Configure the NAS to a static IP outside of the DHCP range.

  • legacy1's avatar
    legacy1
    Alessandro Volta
    7 months ago

    For the best experience with VM get your own router with 1Gb ports and use hub in modem mode

  • Roger_Gooner's avatar
    Roger_Gooner
    Alessandro Volta
    7 months ago

    Use the dynamically assigned IP address, that's how I did it for my NAS (it's 192.168.0.17).

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

    You are not giving the NAS a static IP address doing it on the VM hubs, you are only giving it a ‘preferred’ IP address. You can only give a device a static IP address by doing it on the device. Preferred IP addresses allocated on a HUB or router are always wrongly called static addresses. If you give a device a ‘preferred’ IP address you get twice the amount of DHCP traffic as a static address on the device.

    • Roger_Gooner's avatar
      Roger_Gooner
      Alessandro Volta
      7 months ago

      I disagree. There is an initial DHCP negotiation process which occurs regardless of whether a NAS uses a static IP or a  DHCP-reserved IP. Subsequently if the NAS reconnects or if the lease needs renewal, some additional DHCP traffic will occur but this is trivial.

      For most people I recommend DHCP reservation as all IP assignments are in one place and, of course, many  devices such as mobile and IoT devices do not provide the means to statically set their IP addresses.

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

        For a ‘reserved’ DHCP, at least on my router, you get:

        DHCPDISCOVER
        DHCPOFFER
        DHCPREQUEST
        DHCPACK

        For a ‘static’ device you get:

        DHCPREQUEST
        DHCPACK

        I agreed most IoT WiFi devices do not provide facilities to have a ‘static’ IP address, but all Apple devices certainly allow it, I use it on all of mine.

    • clockworksatan's avatar
      clockworksatan
      Tuning in
      7 months ago

      I was indeed being a dummy and have updated my NAS settings so that it's properly set to a static IP and it's now working with my Hub 5.0.  Thank you for your help!

      • Akua_A's avatar
        Akua_A
        Icon for Forum Team rankForum Team
        7 months ago

        Hi clockworksatan 

        Welcome back to our community forums and sorry to hear you were having DHCP Issues. We are glad to see the community was able to help with this. Please do not hesitate to contact us if you need any further help.

        Thanks,