dhcp Server issues

And this is what tcdump see's in my PVE host when filtered as you suggested. I can see my test laptop etc.
 

Attachments

  • Screenshot 2025-07-26 at 19.18.34.png
    Screenshot 2025-07-26 at 19.18.34.png
    641.6 KB · Views: 1
Hi,

You need to filter on ports 67 AND 68 in wireshark (capture all, stop, and filter after capture).
And at the same time do it on the host when forcing client to request IP via DHCP, and post both results (in code tag preferably).

And make sure you have nothing that can block the request inside Windows (like a bad firewall rule or firewall in public profile).

EDIT :
Or else you can provide pcap files if you're not sur.
Code:
tcpdump -i {INTERFACE} port 67 or port 68 -vv -w mypcapfile.pcap

And the result of :
Code:
pve-firewall status && pvesh get /nodes/{node}/firewall/options

Best regards,
 
Last edited:
Ok. Though I can’t see how it will help. BTW as part of troubleshooting I disabled windows server firewall so it can’t be that, and I tested with an iPhone on Ethernet which also didn’t work, so it’s nothing on the client pc.

I’ll post requested details shortly, but I think we need to focus on why Proxmox isn’t letting the ports through
 
Hi,

I’ll post requested details shortly, but I think we need to focus on why Proxmox isn’t letting the ports through.
Well, it's a bridge so unless a firewall is activated on proxmox (or something was installed on the host), nothing should filter packet since bridge only forwards and nothing more.

I quote what a proxmox staff said :
the bridge configuration has nothing to do with DHCP for VMs. The bridge basically forwards everything that arrives on one port to all the other ports, so the bridge doesn't really know what it has to forward, it just forwards it.
Cf : https://forum.proxmox.com/threads/dhcp-on-vm.152401/#post-691180

Best regards,
 
  • Like
Reactions: MCal27
Hi,


Well, it's a bridge so unless a firewall is activated on proxmox (or something was installed on the host), nothing should filter packet since bridge only forwards and nothing more.

I quote what a proxmox staff said :

Cf : https://forum.proxmox.com/threads/dhcp-on-vm.152401/#post-691180

Best regards,
That’s my understanding too and my Proxmox 7/Server 2016 system works perfectly! It’s definitely not windows server as I tried with both vm’s on each of the two Proxmox hosts and also with a pfsense VM. I can access its login page fine but again DHCP doesn’t function on that (yes I disabled dhcp server service on windows server).
 
ok this is interesting. I added rules to proxmox firewall after turning it on, and I know get this. the server is offering dhcp, but the discover is still not happy. I again switched off the proxmox firewall and I still get the same. It's like simply adding the rules to the firewall helped abit. I used both port 67 and 68
 

Attachments

  • Screenshot 2025-07-26 at 20.56.16.png
    Screenshot 2025-07-26 at 20.56.16.png
    849 KB · Views: 0