From owner-freebsd-questions@FreeBSD.ORG Wed Nov 20 10:03:48 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 28D5E6B6 for ; Wed, 20 Nov 2013 10:03:48 +0000 (UTC) Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 042DF2D38 for ; Wed, 20 Nov 2013 10:03:47 +0000 (UTC) Received: by mail-pa0-f52.google.com with SMTP id ld10so5129715pab.25 for ; Wed, 20 Nov 2013 02:03:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=qSWlA2lR6Vp2pXYSyq2sOrSQbz0fD1Lq8PPLMvWd9Ag=; b=wUE//3COYRM5CjUJWVg/NXshfClHCT828YgoQaqZTjqRnwdFIrG/Ch7aNf0ceDBrCc iueUZOi+tz3V97DquLiunGh1Mt/iz1gHIGXJdz1/wgz7xcDkhozUvCILdp2yQ+rC6Ndl 6Pw64v2rgW6lAkXMcJC858p4sghFp/i6v2CLlg9kgYWHxHJRtMOzU4SgQS6LW6Xsihla COKkR1DZijvZ1d+ed7C4NKHa6wscbmzdIZnIgYRzBf7cTP2df0yyGLUP4PQoD1LZp1Y7 /NAvy63THis6xf18Y2Cx+qvbMQces1Jgg12/sNvtJesWPX7ZOGnFc+7LLekJWTkLlpoL R6Fw== MIME-Version: 1.0 X-Received: by 10.68.218.68 with SMTP id pe4mr464470pbc.181.1384941826618; Wed, 20 Nov 2013 02:03:46 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.68.191.6 with HTTP; Wed, 20 Nov 2013 02:03:46 -0800 (PST) In-Reply-To: <4438msj6z6.fsf@be-well.ilk.org> References: <441u2cih07.fsf@lowell-desk.lan> <44vbzogr7g.fsf@lowell-desk.lan> <4438msj6z6.fsf@be-well.ilk.org> Date: Wed, 20 Nov 2013 11:03:46 +0100 X-Google-Sender-Auth: Y8H1zV907gloohfhRgs7kiUBsOY Message-ID: Subject: Re: bug in dhclient / dhclient.conf / dhcp-options parser? From: CeDeROM To: FreeBSD Questions Mailing List Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Nov 2013 10:03:48 -0000 On Wed, Nov 20, 2013 at 12:40 AM, Lowell Gilbert wrote: > CeDeROM writes: > >> I guess this option-nnn thing should work for all values no matter >> what are the names in some table :-) > > The ISC folks seem to agree, as they've changed their code base to do > so. There are huge structural differences in the internals, though, so > it's not just a matter of porting a fix. > >> I have used isc-42-dhcp-client and it works with the names, but it >> would be nice to have it working in the base as well :-) > > I think my earlier message had enough detail to put out a Problem Report > for the issue. If you prefer, I could come up with a patch for the > actual fix, but if I did that, I would spend enough time to check *all* > of the options to see which other ones might be missing, so I wouldn't > come up with a PR immediately. What I mean and stated above, the parsing option-nnn should work no matter what options are missing - option names should be addition to the option-nnn numbers kind of text alias - this would be simple functional and effective solution without messed code I guess..? :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info