dhcpcd-discuss

On 10/03/2016 10:08, 3e2k2r+1qa9sew786hxo@xxxxxxxxxxxxxxxxx wrote:
> Thanks for the answer, Roy!
> 
> 
> On 08/03/2016 17:26, Roy Marples <roy_at_marples.name> wrote:
>> I suppose that the options should really behave like the others
>> .... off by default but specify them on the default in dhcpcd.conf
>> but that may cause problems for people upgrading....
> 
> 
> Well, the use case for disabling features seems to be really small.
> E.g. my use case is to make current dhcpcd binary-(packet-)compatible
> with older version. So I think the default behavior can be kept as it
> is now, i.e. on by default, off if requested - like e.g. "noarp".

Why do you need that?
A RFC2131 compliant DHCP server *should* ignore any options it doesn't
understand, and all the sent options are structured like any other.

OK, lets rock with a patch to allow them to be turned off via nooption.
Can you do that please and post here? I'm very time constrained right
now with my day job.

> // P.S. Sorry for using this strange mailbox in the list; I cannot
> use my e-mail provider because it isn't capable of subscribing to it
> - fails to handle "=" in the "To:". Next time will try to find better
> provider, with at least plain text formatting support...

No worries.
The most important thing is we can communicate :)

Roy