dhcpcd-discuss

Hi Paul

On 02/07/2015 17:05, Walrath, Paul wrote:
> I discovered the cause of the issue.  If the E flag is set Option 81,
> dhcpcd sets new_fqdn with the fqdn value.  The E flag being set
> indicates that the fqdn value is encoded in the canonical wire format
> specified in RFC 1035 Section 3.1.  The E flag being cleared indicates
> that the fqdn value is  ASCII encoded.  Dhcpcd must be requiring that
> the value be in RFC 1035 format.  The E flag is specified in Section 2.1
> of RFC 4702.  I think this clears up the issue.  I don’t see a need
> right now for dhcpcd to support the ASCII encoding.

He, we sent our emails at the same time :)

You're absolutely spot on by the way.
Even though no code change was required, I did add some more error
handling in this area and some commentary so it's certainly not wasted time.

Roy