From owner-freebsd-questions@FreeBSD.ORG Wed Dec 18 10:00:30 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 A0FD19C3; Wed, 18 Dec 2013 10:00:30 +0000 (UTC) Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4B0791DA7; Wed, 18 Dec 2013 10:00:30 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id r5so5997986qcx.28 for ; Wed, 18 Dec 2013 02:00:29 -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:cc:content-type; bh=cXij2z2+Jvbt9oz8GhOHiHLqOUpVF0XvWXuDr+h0T38=; b=uUzPy6lgfD+wWtnMk/Bl4Rz0xb8E4jlUW9g9W6vCm7RZsifPc8L175mWNVo8xDXp5M XBM4QgPlKgus58GJsHugwltJhbyS3yKLp+xE7ycjNx5fTwzaR44cOY8dvtdiFI/nsDLI 8n1IVq88me4IjVZ+/UjRSPrh5XuVlxESgAaOmR+1qIiNPHFUfaXQRudQu36vfL0n6VPO jjuFpHNXKqrZh8ZkLkFw1h/ACJsGS+fLG1YUSLHMkakuSsc6SXhYHvT+ZWMpq3/bvgCD IABzw5A7JxMvpqfCs2KKa3qn8vJtg/5IkRfMefC7hdMWr5EoVTL65XZ5bgnv+/nFQ2Qz fJ8w== MIME-Version: 1.0 X-Received: by 10.224.67.137 with SMTP id r9mr51858563qai.8.1387360829294; Wed, 18 Dec 2013 02:00:29 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.229.151.73 with HTTP; Wed, 18 Dec 2013 02:00:29 -0800 (PST) Received: by 10.229.151.73 with HTTP; Wed, 18 Dec 2013 02:00:29 -0800 (PST) In-Reply-To: <52B1713D.5060203@bluerosetech.com> References: <52B1713D.5060203@bluerosetech.com> Date: Wed, 18 Dec 2013 11:00:29 +0100 X-Google-Sender-Auth: TlyH65wnE5Ne-L3bZhOv5TEwu2s Message-ID: Subject: Re: bug in dhclient / dhclient.conf / dhcp-options parser? From: CeDeROM To: Darren Pilgrim Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-net@freebsd.org, FreeBSD Questions Mailing List X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2013 10:00:30 -0000 Naah, "option-n" should work for all options aside ascii names that vary ascross implementations :-) Best regards, Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info On Dec 18, 2013 10:56 AM, "Darren Pilgrim" wrote: > On 11/19/2013 6:09 AM, CeDeROM wrote: > >> Hello :-) >> >> I need to send additional options with dhcp request, so I add "send" >> option for an interface in /etc/dhclient.conf, however options are >> non-standard and they use option value below 100 and they are not sent >> in dhcp request. 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? >> >> Here is my example /etc/dhclient.conf configuation: >> >> interface "em0"{ >> send option-060 "vendor"; <-- does not go out in dhcp request >> send option-077 "user"; <-- does not go out in dhcp request >> send option-123 "blah123"; <-- goes out in dhcp request >> send root-path "blahroot"; <-- goes out in dhcp request >> } >> >> Please advise, quick solution appreciated :-) >> > > The "option-n" options only work for unknown codes. Option codes 60 and > 77 are known as dhcp-class-identifier and user-class, respectively. Both > are formatted as ASCII text. >