Fix Proxmox EVE-NG IP Issue
Budget: $8 – $15 USD
My EVE-NG lab, running inside Proxmox, suddenly stopped receiving addresses from my internal router’s DHCP pool. The VM is attached to a bridged interface and previously picked up an IP in the correct range without problems. Nothing in the network layout has changed and I have already restarted the Proxmox host, double-checked the EVE-NG adapter settings, and reviewed the router configuration, yet the bridge no longer passes DHCP traffic.
I want the environment back to the point where EVE-NG instances reliably obtain an IP from the router and are reachable on the LAN. Diagnosis should cover the Proxmox bridge, the underlying Linux network stack, and any EVE-NG specifics (vrf, cloud interfaces, tap devices, etc.). If the fix involves updating bridge parameters, VLAN tagging, firewall rules, or re-creating virtual NICs, please implement it and explain the reasoning.
Deliverables:
• Restored DHCP connectivity to the EVE-NG VM through the bridged interface.
• A concise report of the root cause and the exact configuration changes made so I can repeat them if needed.
I will provide console access to the Proxmox host and router GUI/CLI as required. Once the VM consistently receives an IP from the router, pings the default gateway, and survives a host reboot, the task will be considered complete.
I want the environment back to the point where EVE-NG instances reliably obtain an IP from the router and are reachable on the LAN. Diagnosis should cover the Proxmox bridge, the underlying Linux network stack, and any EVE-NG specifics (vrf, cloud interfaces, tap devices, etc.). If the fix involves updating bridge parameters, VLAN tagging, firewall rules, or re-creating virtual NICs, please implement it and explain the reasoning.
Deliverables:
• Restored DHCP connectivity to the EVE-NG VM through the bridged interface.
• A concise report of the root cause and the exact configuration changes made so I can repeat them if needed.
I will provide console access to the Proxmox host and router GUI/CLI as required. Once the VM consistently receives an IP from the router, pings the default gateway, and survives a host reboot, the task will be considered complete.