dhcpcd-discuss

Hi Paul

On 02/07/2015 03:44, Walrath, Paul wrote:
> dhcpcd –U eth0 shows the following:
> 
> fqdn_flags=’0’
> 
> fqdn_rcode1=’0’
> 
> fqdn_rcode2=’0’
> 
> but fqdn_fqdn is not listed.

The option is fqdn, not fqdn_fqdn :)

A flags of 0 means that the E bit is not set.
This means the server is sending ASCII text instead of a RFC1035
compressed domain name.

The usage of ASCII text has been deprecated.
When dhcpcd got it's new option parsing code, the one thing it lost was
the ability to decode the FQDN option based on the encoding flag - now
it only accepts RFC1035 domain names. This should be fine as the server
MUST encode according to the client as noted in RFC4702 section 2.1.
dhcpcd itself will always enable the encoding option.

I've added some commentary to the FQDN option in dhcp-definitions.conf
to describe this.

Roy