[Bug 98618] Re: Set domain and search entries correctly
No +1's, no more comments, and purportedly at least one person saw it as fixed in Jaunty. Closing as Fix Released. ** Changed in: dhcp3 (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in Ubuntu. https://bugs.launchpad.net/bugs/98618 Title: Set domain and search entries correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/98618/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 98618] Re: Set domain and search entries correctly
No +1's, no more comments, and purportedly at least one person saw it as fixed in Jaunty. Closing as Fix Released. ** Changed in: dhcp3 (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/98618 Title: Set domain and search entries correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/98618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98618] Re: Set domain and search entries correctly
It works for me in the following configuration: DHCP Server 3.1.1 on Intrepid Client with NetworkManager 0.7.1 on Jaunty -- 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 98618] Re: Set domain and search entries correctly
It works for me in the following configuration: DHCP Server 3.1.1 on Intrepid Client with NetworkManager 0.7.1 on Jaunty -- Set domain and search entries correctly https://bugs.launchpad.net/bugs/98618 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98618] Re: Set domain and search entries correctly
Is this bug still an issue in jaunty, which has dhcp3 3.1.1? -- 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 98618] Re: Set domain and search entries correctly
Is this bug still an issue in jaunty, which has dhcp3 3.1.1? -- Set domain and search entries correctly https://bugs.launchpad.net/bugs/98618 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98618] Re: Set domain and search entries correctly
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 PROTECTED] () 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/13417473/anders.vcf ** Attachment added: signature.asc http://launchpadlibrarian.net/13417474/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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 98618] Re: Set domain and search entries correctly
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 PROTECTED] () 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/13417473/anders.vcf ** Attachment added: signature.asc http://launchpadlibrarian.net/13417474/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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98618] Re: Set domain and search entries correctly
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. -- Set domain and search entries correctly https://bugs.launchpad.net/bugs/98618 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98618] Re: Set domain and search entries correctly
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 [EMAIL PROTECTED] () 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98618] Re: Set domain and search entries correctly
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). -- 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 98618] Re: Set domain and search entries correctly
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). -- Set domain and search entries correctly https://bugs.launchpad.net/bugs/98618 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98618] Re: Set domain and search entries correctly
** Changed in: dhcp3 (Ubuntu) Importance: Undecided = Medium Status: Unconfirmed = Confirmed -- Set domain and search entries correctly https://bugs.launchpad.net/bugs/98618 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98618] Re: Set domain and search entries correctly
Hmm, defining a new option in dhclient.conf looks a bit weird -- shouldn't this go into the actual code? -- Set domain and search entries correctly https://bugs.launchpad.net/bugs/98618 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98618] Re: Set domain and search entries correctly
This is the patch to correct the problem. ** Attachment added: Patch to solve the problem http://librarian.launchpad.net/7043479/dhclient-script.patch -- Set domain and search entries correctly https://launchpad.net/bugs/98618 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
