dhcpcd-discuss

Hi Paul

On 02/07/2015 17:40, Walrath, Paul wrote:
> I did a test and found that ISC dhcpd 4.2.4 DHCP server did not look
> at the E bit in Option 81 that is sent from the client.  Dhcpcd sent
> Option 81 with the E bit set but dhcpd returned Option 81 with the
> fqdn still ASCII encoded.  I had to configure dhcpd using "option
> fqdn.encoding true" in order to get it to return the fqdn using RFC
> 1035 encoding.  It appears as though ASCII is its default encoding,
> at least for the fqdn response that it returns to the client.  RFC
> 4702 says that a server MUST use the same encoding as that used by
> the client, so I don't understand this result.  It appears as though
> ISC dhcpd is not in compliance with RFC 4702.

Could you share the fqdn part of your config? I can never get dhcpd to
send back any FQDN option.

But from the sounds of it, you are right that it does appear to be a bug
in dhcpd.

There are other areas where dhcpd/dhclient isn't entirely RFC compliant
so it doesn't come as any big surprise either.

Roy