Hi,I have a couple of devices which I'd like to use a static IP address.I went to the DHCP page and added a rule for one but when I went to reserve the second I get an error..."Sorry! There was an error while updating your settings. Please try again a bit later".I have tried a bit later and also switched the Hub off for a while but I still get the same error. I tried phone support but that was a joke. The chap at the other end clearly had no idea what I was talking about and his advice was to try later.I know I can apply a static IP individually to my device within it's own settings but I'd would prefer to do it this way for future use. Any ideas?Thanks

It is much better to set the Static IPs on each of the devices i.e. via the device's settings screen or web management page.Use the IP range 192.168.0.2 to 192.168.0.9 - extend this if needed by moving the DHCP start point to say 192.168.0.30Using a "Reserved IP" is not quite the same as the devices remain dependent on the VM Hub's DHCP server working correctly. Also when the VM Hub is Factory Reset or replaced all Reserved IPs are lost.

Reserved IP addresses are NOT static IP addresses. You can only set static IP addresses in a device. Reserved IP addresses as most people seem to believe as being static are not totally static and can in certain instances can be reused by the DHCP server.

I concede it’s unlikely to happen for VM home users, but deep down in the DHCP specs it say if the pool in exhausted and there are reserved addresses that are currently not used then they will be used for the new request. I saw this when I was working in a school after I retired. We had a Microsoft domain controller and backup that were both running DHCP servers, you can do sort of mirroring with Microsoft DHCP servers, as normally it’s exceedingly bad to run two DHCP servers.Thinking about it, if a user cut the pool down to a very small size, then it could happen on a VM connection. I use all static address in my setup with a DHCP pool size of 10, although my router does allow reserved IP addresses outside of the pool.

Are the reserved IP's inside the DHCP scope?

You are on the right path and I really don't recommend static addresses for residential users. The DHCP reservation range is 192.168.0.10 to 192.168.0.245, and you should reserve your IP address within this range. By reserving an IP address within the hub's settings, you centralise your network management. The hub's DHCP server is smart enough to 'earmark' these addresses, so it won't dynamically assign them to other devices and cause a conflict.Let's say your devices have dynamic addresses of 192.168.0.11 and 192.168.0.12, and this is the easiest way to proceed. You find the MAC addresses and enter the MAC address and 192.168.0.11 for the first device and click Add rule. This should work and you do the same for the other device with its MAC address and 192.168.0.12.The most reliable way to get your devices reconnected is to turn them off, switch the hub off at the wall socket, wait two minutes and switch back on. Once the hub has fully rebooted (takes some minutes to get a solid white light), switch the devices back on and they will be forced to send a "DHCP Request". The hub will respond with the newly reserved IP addresses.

Unable to reserve an IP address on Hub 5 | Virgin Media Community

17 Replies

Replies have been turned off for this discussion

Adduxi
Very Insightful Person
1 month ago
Are the reserved IP's inside the DHCP scope?
Client62
Alessandro Volta
1 month ago
It is much better to set the Static IPs on each of the devices
i.e. via the device's settings screen or web management page.

Use the IP range 192.168.0.2 to 192.168.0.9 - extend this if needed by moving the DHCP start point to say 192.168.0.30

Using a "Reserved IP" is not quite the same as the devices remain dependent on the VM Hub's DHCP server working correctly.
Also when the VM Hub is Factory Reset or replaced all Reserved IPs are lost.
Roger_Gooner
Alessandro Volta
1 month ago
You are on the right path and I really don't recommend static addresses for residential users. The DHCP reservation range is 192.168.0.10 to 192.168.0.245, and you should reserve your IP address within this range. By reserving an IP address within the hub's settings, you centralise your network management. The hub's DHCP server is smart enough to 'earmark' these addresses, so it won't dynamically assign them to other devices and cause a conflict.
Let's say your devices have dynamic addresses of 192.168.0.11 and 192.168.0.12, and this is the easiest way to proceed. You find the MAC addresses and enter the MAC address and 192.168.0.11 for the first device and click Add rule. This should work and you do the same for the other device with its MAC address and 192.168.0.12.
The most reliable way to get your devices reconnected is to turn them off, switch the hub off at the wall socket, wait two minutes and switch back on. Once the hub has fully rebooted (takes some minutes to get a solid white light), switch the devices back on and they will be forced to send a "DHCP Request". The hub will respond with the newly reserved IP addresses.
Adduxi
Very Insightful Person
1 month ago
Hmm, I’ve lots of Reserved IP’s in use, as well as a few static ones. Don’t use a VM router though, but I wouldn’t recommend one way against the other as far as IP issuing. I also keep my DHCP scope as small as possible.
Yorky46
Tuning in
1 month ago
Thanks for all the replies.
I can confirm the IP's are within the range of the IP scope. The HUB has assigned the IP address and I'm just trying to keep it static so I can access the device through routes without having to be concerned that the IP address may have changed.
I'm using the Hub to add a rule and it worked perfectly for the first device but, when I try to do the exact same thing with the second device, it throws up an error.
It's more of an annoyance than anything else and I may just end up assigning the IP through the device itself.
thanks again
- Adduxi
  Very Insightful Person
  1 month ago
  Just one thing to try. Add the IP addresses in numerical rising order, from memory a good while ago, there was an issue when things had to be done in numerical order, or it wouldn't work. I think it may have been port forwarding though?
  Also try setting the DHCP scope much smaller, e.g. x.x.x.100 to x.x.x.150 Maybe worth a try?
- Muhammod_I
  Forum Team
  1 month ago
  Thanks for reaching out to us with this Yorky46 and I'm sorry that you're having a difficult time with this.
  
  Can I ask if you've tried the steps provided by our forum members and had any luck?
  
  If you need any further support after this, please don't hesitate to reach out.
  
  We're more than happy to help 🙂
Roger_Gooner
Alessandro Volta
1 month ago
The hub's Active Lease Table hasn't cleared down, so note the second device's MAC address and IP address, turn off the the second device, reboot the hub and reserve the same IP address for the second device.
Tudor
Very Insightful Person
1 month ago
Reserved IP addresses are NOT static IP addresses. You can only set static IP addresses in a device. Reserved IP addresses as most people seem to believe as being static are not totally static and can in certain instances can be reused by the DHCP server.
- Adduxi
  Very Insightful Person
  1 month ago
  Tudor Sorry, but enlighten me please. I always thought Reserved IP's couldn't be reused and were tied to a MAC address?
  - Tudor
    Very Insightful Person
    1 month ago
    I concede it’s unlikely to happen for VM home users, but deep down in the DHCP specs it say if the pool in exhausted and there are reserved addresses that are currently not used then they will be used for the new request. I saw this when I was working in a school after I retired. We had a Microsoft domain controller and backup that were both running DHCP servers, you can do sort of mirroring with Microsoft DHCP servers, as normally it’s exceedingly bad to run two DHCP servers.
    Thinking about it, if a user cut the pool down to a very small size, then it could happen on a VM connection. I use all static address in my setup with a DHCP pool size of 10, although my router does allow reserved IP addresses outside of the pool.
Roger_Gooner
Alessandro Volta
1 month ago
Valid point Tudor, and static addreses can only be set for a fraction of devices in a typical home - another reason why I don't recommend trying to use them. And as for setting them: always outside the DHCP reservation range.
- Adduxi
  Very Insightful Person
  1 month ago
  Yes, my statics are usually on switches, AP's etc. and as you say, outside the DHCP scope.
- Tudor
  Very Insightful Person
  1 month ago
  I do not use many old type IoT devices, replaced most with Waveshare 8 channel Ethernet Relay modules Modbus TCP protocol and PoE. I have written some C code to drive them. Have 4 in use.
legacy1
Alessandro Volta
1 month ago
Put simply the hub settings are not well tested and they don't to be you just need modem mode and your own router.