[Starlingx-discuss] DHCP Related Patches

Saul Wold sgw at linux.intel.com
Fri Oct 5 00:42:01 UTC 2018

On 10/04/2018 03:01 PM, Saul Wold wrote:
> HI Brent,
> There are currently 6 DHCP related patches specifically to the client code.
> We have already determined that 2 of those patches the NSUPDATE 
> protection could be removed, 2 seem to be StarlingX spceific but 
> replaced with a enter-hook scripts provided in another patch. 1 is a 
> backport
> dhclient-disable-NSUPDATE.patch
> support-disable-nsupdate.patch
>   - Remove these 2
> dhclient-handle-wrs-install-uuid.patch
> dhclient-dhcp6-wrs-install-uuid.patch
>   - Can these be removed as the functionality is now added via the 
> dhclient-enter-hooks script?
> dhclient-ipv6-bind-to-interface.patch
>   - This is a backport, which will be available when CentOS updates to 
> the newer version.
MY bad, I was looking at the wrong code base, this is still a valid 
patch and seems to move where the bind to interface happens from after
the bind to before the bind, again if this is a bug, was it reported 
anywhere to Redhat or Upstream on the DHCP list/bug system?


> dhclient-ipv6-conditionally-set-hostname.patch
>   - Can this be moved to the dhclient-enter-hooks?
> dhclient-restrict-interfaces-to-command-line.patch
>   - This seems to be adding functionality, in order to restrict the 
> dhclient to only be active on one interface. There is no commit message 
> for this one, or is there a way to refactor this?  Is this a bug in 
> dhclient?  Was it ever filled or commented on in the DHCP mailing list?
> Thanks
>     Sau!
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

More information about the Starlingx-discuss mailing list