[Dibbler] dibbler-server an debian-armel

Rommel Laranjo rslaranjo at gmail.com
Sat Aug 16 04:24:41 CEST 2008

On Fri, Aug 15, 2008 at 4:50 PM, Christian Andersen <lists at milindur.de> wrote:
> Hallo,
>> According to RFC4704 (FQDN), section 4.2 domain names must be coded as
>> specified in RFC3315, section 8. RFC3315 in section 8 states that
>> domain
>> encoding must be stored in a compressed form as explained in section
>> 3.1
>> of RFC1035. And here's the corresponding part of that RFC:
>> Each label is represented as a one octet length field followed by that
>> number of octets.
>> Microsoft just puts domain name and terminates it with 0.
>> That is *wrong*.
> I looked at this issue again and tried Windows Vista with wide-dhcpv6-server
> (works on my device).
> Vista sends Solicit- and Request-message with wrong encoded FQDN field.
> wide-dhcpv6-server answers with Advertise- and Reply-message. I configured
> the server to send a Domain search list to the client.

the fqdn option sent by vista to wide dhcpv6 server was simply ignored
cause wide
doesn't support processing of fqdn sent by the client yet.

maybe this is why wide dhcpv6 server can inter act with vista.

This domain list is
> encoded correctly (in compliance with RFC). But Vista misinterprets this and
> splits the domain into its label parts and uses each label as domain.
> Example:
> Domain Search List in Advertise/Reply:
> * sub.domain.de
> Vista interprets this as:
> * sub
> * domain
> * de
> The result is quite funny. I can enter "ping t-online" and get responses
> from "t-online.de".
> I do not think that this option in DHCPv6 was meant to work this way.
> Regards,
> Christian
> _______________________________________________
> http://klub.com.pl/cgi-bin/mailman/listinfo/dibbler

More information about the Dibbler mailing list