Andrew Pollock schrieb:
> If you look at the source code, which is always a wonderful place to
> achieve enlightenment, in common/tables.c, in the comments, you'll see
> it talks about option names, formats and codes. In 3.1.0, they added a
> new option code, D, which is a domain list. This is different from the
> various string types that have already existed.
>
> I'm very surprised that a pre 3.1.0 DHCP server with a manually set DHCP
> option for domain-search is being correctly interpreted by MacOS X, but
> hey, if it works, and you can't wait for the 3.1 series to stabilise,
> knock yourself out. I guess you're only at risk of breaking people who
> try to use the option.
Ok, I archived enlightment! ;-)
As far as I understand (by taking a quick look at the code), they only
introduced a new type because the domain search list is compressed
using a special technique described in RFC1035. This technique uses
pointers to prior occurrences. In the RFC3397 using the techique is a
MUST, but because it only saves space it works without using it too.
In the configuration file and the resolv.conf file it's always a
string.
I will try to use the 3.1 release of the dhcp3-client and we will see,
if this solves my problems. Thanks for the hint!
Regards
Sven
--
Sven Anders <email address hidden> () 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
Andrew Pollock schrieb:
> If you look at the source code, which is always a wonderful place to
> achieve enlightenment, in common/tables.c, in the comments, you'll see
> it talks about option names, formats and codes. In 3.1.0, they added a
> new option code, D, which is a domain list. This is different from the
> various string types that have already existed.
>
> I'm very surprised that a pre 3.1.0 DHCP server with a manually set DHCP
> option for domain-search is being correctly interpreted by MacOS X, but
> hey, if it works, and you can't wait for the 3.1 series to stabilise,
> knock yourself out. I guess you're only at risk of breaking people who
> try to use the option.
Ok, I archived enlightment! ;-)
As far as I understand (by taking a quick look at the code), they only
introduced a new type because the domain search list is compressed
using a special technique described in RFC1035. This technique uses
pointers to prior occurrences. In the RFC3397 using the techique is a
MUST, but because it only saves space it works without using it too.
In the configuration file and the resolv.conf file it's always a
string.
I will try to use the 3.1 release of the dhcp3-client and we will see,
if this solves my problems. Thanks for the hint!
Regards
Sven
--
/\ Support plain text e-mail
Sven Anders <email address hidden> () Ascii Ribbon Campaign
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