WinDivert appears to block DHCP traffic to 255.255.255.255

[schultetwin1]

Repro Steps:

1. Open up WireShark and filter on your primary interface for DHCP traffic
2. Run passthru.exe "udp and ((udp.DstPort == 67) or (udp.DstPort == 68))"
3. Run ipconfig /release
4. Notice the DHCP Release packet in WireShark
5. Run ipconfig /renew
6. Wait for the timeout. Notice no new DHCP packets are seen

I would expect the DHCP traffic to still be sent and show up in WireShark.

[johnnyd-78]

Confirm. I have OpenVPN server that push DNS to client, push gateway with options "bypass-dhcp block-local" and have "block-outside-dns" option in client config. When WinDivert in memory (after start and closing of GoodbyeDPI), after connect and VPN tunnel up - no access to pushed DNS (nslookup, tracert and ping don't work - timeout), windows changes net icon to globe... After 4-5 minutes tunnel renegs and access appears. After reboot and without WinDivert in memory VPN works fine with first seconds of tunnel up. OS - Windows 11 21H2