You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We did this before some of your more recent changes to interface binding. We may re-evaluate that later to see if we can switch back out of the custom interface code we use.
Regardless, we encountered in the field an issue that appears in the current code base. A DHCP client sets the Broadcast flag bit in a request, but a DHCP relay is used to forward the packet to our server. In this case, the reply code will generate a broadcast message instead of sending back to the giaddr field as per the spec.
The issue is around line 70 in server.go. To address the issue, we do this:
Thanks galthaus, I never thought of that particular use case for this library. Please have a look at the giaddr branch and and tell me what you think of conn/giaddr.go (untested).
We use parts of this library with a custom handler implementation for:
https://github.com/digitalrebar/provision
We did this before some of your more recent changes to interface binding. We may re-evaluate that later to see if we can switch back out of the custom interface code we use.
Regardless, we encountered in the field an issue that appears in the current code base. A DHCP client sets the Broadcast flag bit in a request, but a DHCP relay is used to forward the packet to our server. In this case, the reply code will generate a broadcast message instead of sending back to the giaddr field as per the spec.
The issue is around line 70 in server.go. To address the issue, we do this:
Hope this helps. Thanks for your work.
The text was updated successfully, but these errors were encountered: