[Bug 98618] Re: Set domain and search entries correctly

Sven anders at anduras.de
Sat Mar 29 15:01:36 GMT 2008


Andrew Pollock schrieb:
> ObRelevance: I'm the Debian dhcp3 maintainer, and I've been extensively
> testing domain-search support in DHCP 3.1.x in Debian
> 
> The domain-search attribute is a new type, not a string, which is
> encoded differently on the wire.
> 
> Adding
> 
>   option dns-domain-search-list code 119 = string;
> 
> to dhcpd.conf and/or dhclient.conf will probably work fine if both the
> client and the server are the same pre-3.1.x version, but if the server
> is 3.1.x or some other server that supports the domain-search option
> correctly, it'll be sending it as the new domain list type, which will
> most probably get mangled by the client if understood at all.
> 
> I do not recommend hacking such functionality into pre-3.1.x versions of
> DHCP. I also do not consider the functionality to be production-ready
> yet in 3.1.0 (and 3.1.1 is not looking much better yet either).
> 

Hmm, I do not understand. I the RFC I found it's a string (see below).
Did I misinterpreted it?

And I'm using here a dhcp-3.0.4 server and a dhcp-3.0.6 client - without problems.
Furthermore I'm using MacOS-X which honour the flag and it's working correctly
too...

Where did you read that it's a new type? And what format?


>From the RFC3397:
-----------------
2.  Domain Search Option Format

   The code for this option is 119.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     119       |     Len       |         Searchstring...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                     Searchstring...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   In the above diagram, Searchstring is a string specifying the
   searchlist.  If the length of the searchlist exceeds the maximum
   permissible within a single option (255 octets), then multiple
   options MAY be used, as described in "Encoding Long Options in the
   Dynamic Host Configuration Protocol (DHCPv4)" [RFC3396].

Regards
 Sven Anders

-- 
 Sven Anders <anders at anduras.de>                 () Ascii Ribbon Campaign
                                                 /\ Support plain text e-mail
 ANDURAS service solutions AG
 Innstraße 71 - 94036 Passau - Germany
 Web: www.anduras.de - Tel: +49 (0)851-4 90 50-0 - Fax: +49 (0)851-4 90 50-55

Rechtsform: Aktiengesellschaft - Sitz: Passau - Amtsgericht Passau HRB 6032
Mitglieder des Vorstands: Sven Anders, Marcus Junker
Vorsitzender des Aufsichtsrats: Dr. Thomas Träger


** Attachment added: "anders.vcf"
   http://launchpadlibrarian.net/12964294/anders.vcf

** Attachment added: "signature.asc"
   http://launchpadlibrarian.net/12964295/signature.asc

-- 
Set domain and search entries correctly
https://bugs.launchpad.net/bugs/98618
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.



More information about the Ubuntu-server-bugs mailing list