Closed ForestJohnson closed 1 month ago
Please sign the commit. More details in: https://github.com/insomniacslk/dhcp/pull/516/checks?check_run_id=19055434699
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 73.06%. Comparing base (
c728f5d
) to head (91af758
). Report is 8 commits behind head on master.:exclamation: Current head 91af758 differs from pull request most recent head af24f57
Please upload reports for the commit af24f57 to get more accurate results.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
A DHCP server should probably always listen on
0.0.0.0
when we're working on it in development and testing.Why?
I believe normal DHCP requests are sent as broadcasts to
255.255.255.255
... I believe when its broadcasted, every single UDP packet regardless of where it ends up, will have255.255.255.255
as the destination address. And since255.255.255.255
!=127.0.0.1
, the UDP listener will ignore it.We can tell our UDP listener to listen on
255.255.255.255
but then it will ONLY receive these "normal" DHCP broadcast packets. If someone tries to send a datagram to it directly (on a specific IP like127.0.0.1
,192.168.69.1
etc) it wont be received.So i think
0.0.0.0
is appropriate here, considering that it's already being told to listen on a specific interface.