Forum Discussion

samosa's avatar
samosa
Superfast
3 days ago

DHCP reservation not assigning the ip reserved to device.

I am running an OPNsense virtual machine instance on Proxmox. Initially, I used the network ports in passthrough mode, but I am trying to virtualise them.

Previously, the physical MAC address had a reserved IP of .100, which worked for months. After the change, I updated the reservation on the Hub 5 to use the new virtual MAC address generated by the Proxmox VM bridge. This is where the issue began.

Upon booting, the OPNsense WAN interface receives an IP address ending in .220 instead of the reserved .100. I have tried:

  • Power cycling the Hub 5 modem (leaving it off for 5 minutes).
  • Restarting OPNsense.
  • Generating and using a new virtual MAC address for the VM.

i've also tried shut down OPNsense, changed its virtual MAC address to one the Hub had never seen before, and reserved .100 for that new MAC in the Hub's settings. However, when I booted OPNsense, the Hub still assigned it a different DHCP address from the range.

If I set a static IP within OPNsense, it retains the DHCP-assigned address and merely creates an alias for the static one. There seems to be no way to force the Hub to assign the reserved .100 address.

Has anyone experienced a situation where a reserved IP is not correctly assigned to its designated MAC address, or am i doing something incorrect?

3 Replies

  • Tudor's avatar
    Tudor
    Very Insightful Person
    3 days ago

    I advise everyone to not use reserved addresses in VM hubs. If you want a fixed address for a device, just give it one on the device. Also, why are you not using modem mode?

    • samosa's avatar
      samosa
      Superfast
      3 days ago

      As i've got some devices that are a ball ache to move across (lazy).  i'll have another look at static method.
       

  • legacy1's avatar
    legacy1
    Alessandro Volta
    3 days ago

    Get a better router use hub in modem mode.