From owner-freebsd-questions@FreeBSD.ORG Tue Nov 19 14:49:20 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 94A3C1FC for ; Tue, 19 Nov 2013 14:49:20 +0000 (UTC) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id 6D537250F for ; Tue, 19 Nov 2013 14:49:20 +0000 (UTC) Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.41]) by be-well.ilk.org (Postfix) with ESMTP id D183333C22; Tue, 19 Nov 2013 09:49:14 -0500 (EST) Received: by lowell-desk.lan (Postfix, from userid 1147) id 38EB539848; Tue, 19 Nov 2013 09:49:12 -0500 (EST) From: Lowell Gilbert To: CeDeROM Subject: Re: bug in dhclient / dhclient.conf / dhcp-options parser? References: Date: Tue, 19 Nov 2013 09:49:12 -0500 In-Reply-To: (cederom@tlen.pl's message of "Tue, 19 Nov 2013 15:15:20 +0100") Message-ID: <441u2cih07.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: FreeBSD Questions Mailing List X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list Reply-To: FreeBSD Questions Mailing List List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Nov 2013 14:49:20 -0000 CeDeROM writes: > On Tue, Nov 19, 2013 at 3:09 PM, CeDeROM wrote: >> I have noticed that other options with names known to >> dhcp-options and decimal numbers above 100 are sent correctly, so >> maybe there is an error in the options number parser, or I do >> something wrong? > > I have just tested value 88 (example below 100) and it works > correctly, so parsing seems okay. Why some option numbers are treated > in a different way then? :-( See the manual ("man 5 dhcp-options"). Options which are not listed by name may be defined by the name option-nnn, where nnn is the decimal number of the option code. You can only specify options by number if the dhcp client doesn't know the syntax/semantics for that particular option.