NetBSD Problem Report #52403
From www@NetBSD.org Fri Jul 14 17:28:07 2017
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (not verified))
by mollari.NetBSD.org (Postfix) with ESMTPS id E3A487A1AF
for <gnats-bugs@gnats.NetBSD.org>; Fri, 14 Jul 2017 17:28:07 +0000 (UTC)
Message-Id: <20170714172806.767947A213@mollari.NetBSD.org>
Date: Fri, 14 Jul 2017 17:28:06 +0000 (UTC)
From: m.viey@wanadoo.fr
Reply-To: m.viey@wanadoo.fr
To: gnats-bugs@NetBSD.org
Subject: dhclient program doesn't send dhcp-client-identifier set in /etc/dhclient.conf
X-Send-Pr-Version: www-1.0
>Number: 52403
>Category: bin
>Synopsis: dhclient program doesn't send dhcp-client-identifier set in /etc/dhclient.conf
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: bin-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jul 14 17:30:01 +0000 2017
>Closed-Date: Sun Dec 23 01:44:11 +0000 2018
>Last-Modified: Sun Dec 23 01:44:11 +0000 2018
>Originator: Mickaël Viey
>Release: 7.0.2
>Organization:
>Environment:
NetBSD 7.0.2 (GENERIC.201610210724Z) amd64
>Description:
Hi,
I have a router One access One50 on this I try to configure a DHCP IP binding for my NetBSD.
This router has two means to declare a binding (from documentation):
"To configure a manual binding, first enter in DHCP configuration mode:
CLI(configure)> ip dhcp pool <pool-name>
To create a manual binding between IP address and hardware address, use the following command:
CLI(dhcp-config)> host <ip-address>
CLI(dhcp-config)> hardware-address <MAC-address> ethernet
The MAC address is in a format such as: '00:80:DE:AD:BE:EF'. Following the above-referenced
commands, one can also set other DHCP options associated with the host; client name, hostname, etc.
Alternatively, a binding may be declared without using the ‘hardware-address ...’ command if the client-
identifier command is used:
CLI(dhcp-config)> host <ip-address>
CLI(dhcp-config)> client-identifier <string>
To remove the manual binding or an option in a manual binding, use the 'no' form of the corresponding
command."
Unfortunately, NetBSD send a client-identifier which is not understood by the router. Because the client identifier take the precedence to the mac address if I want get a static IP from the router from NetBSD I must configure the BSD dhcp client for it doesn't send this identifier. But whatever I try to do with the configuration file /etc/dhclient.conf the router always receive a bytes sequence in place of client identifier, and another IP than expected is attribued.
Here is my last try /etc/dhclient.conf:
"
send dhcp-client-identifier "\0";
request ;
timeout 30;
retry 60;
select-timeout 5;
script "/sbin/dhclient-script":
lease {
interface "re0";
}
"
I try many combination:
send dhcp-client-identifier "dk-17";
Try to remove the line. Anyway the behaviour it the same I get this when I get binding configuration in the router:
mika-ftth>sh ip dhcp binding
IP address Hardware address Client identifier Expire in Type
192.168.15.3 00:25:22:59:a0:88 Y�� 23:54:30 Automatic
192.168.15.1 00:25:22:59:a0:88 - - Manual
192.168.15.2 78:a3:51:26:4c:17 - 23:31:20 Manual
mika-ftth>
192.168.15.1 it's the IP I want to get, and 192.168.15.3 the IP I actually get with the client identifier like this: Y��.
------------------------------------
The configuration of the router is bellow:
Building configuration...
Current configuration:
[...]
interface FastEthernet 0/0
no ip address
[...]
description * FTTH DIALER *
exit
interface FastEthernet 0/1
bridge-group 123
exit
interface FastEthernet 0/2
bridge-group 123
exit
interface FastEthernet 0/3
ip address 192.168.23.253 255.255.255.0
description backup
ip nat inside overload
exit
interface Bvi 123
ip address 192.168.15.254 255.255.255.0
bridge-group 123
exit
virtual-template ppp 2
[...]
ip dhcp pool Private
dns-server 195.5.209.150 194.79.128.150
default-router 192.168.15.254
network range 192.168.15.1 192.168.15.10
exit
ip dhcp pool rt1
default-router 192.168.15.254
dns-server 195.5.209.150 194.79.128.150
host 192.168.15.2
hardware-address 78:A3:51:26:4C:17 ethernet
exit
ip dhcp pool dk17
dns-server 195.5.209.150 194.79.128.150
default-router 192.168.15.254
host 192.168.15.1
hardware-address 00:25:22:59:A0:88 ethernet
exit
[...]
end
---------------------------
Here the log from the router for a DHCP request from NetBSD:
00:18:31.261 #NOTIFY# IF: FastEthernet 0/2 is DOWN
00:18:33.461 #NOTIFY# IF: FastEthernet 0/2 is UP
00:18:39.661 #NOTIFY# IF: FastEthernet 0/2 is DOWN
00:18:41.861 #NOTIFY# IF: FastEthernet 0/2 is UP
00:18:46.394 DHCPS: receive DHCPREQUEST for 192.168.15.3 from 0x00:25:22:59:a0:88
00:18:46.394 DHCPS: send DHCPACK on 192.168.15.3 to 0x00:25:22:59:a0:88
00:18:46.394 DHCPS: 192.168.15.3 assigned to client "0:0xff2259a08800010001203a470000252259a088" for 24:00:00
00:24:33.461 #NOTIFY# IF: FastEthernet 0/2 is DOWN
00:24:35.661 #NOTIFY# IF: FastEthernet 0/2 is UP
00:24:41.861 #NOTIFY# IF: FastEthernet 0/2 is DOWN
00:24:44.061 #NOTIFY# IF: FastEthernet 0/2 is UP
00:24:44.632 DHCPS: receive DHCPREQUEST for 192.168.15.3 from 0x00:25:22:59:a0:88
00:24:44.633 DHCPS: send DHCPACK on 192.168.15.3 to 0x00:25:22:59:a0:88
00:24:44.633 DHCPS: 192.168.15.3 assigned to client "0:0xff2259a08800010001203a470000252259a088" for 24:00:00
the client identifier 0:0xff2259a08800010001203a470000252259a088 seems to be very long and I think it's a part of the problem. If I compare with the transaction from another dhcp request from another device (a router on openwrt)this identifier is shorter:
mika-ftth>debug ip dhcp
mika-ftth>monitor trace
mika-ftth>00:44:28.443 DHCPS: receive DHCPDISCOVER from 0x78:a3:51:26:4c:17
00:44:28.443 DHCPS: arp checking, send ARP for 192.168.15.2 to Bvi 123
00:44:28.940 DHCPS: 192.168.15.2 is available
00:44:28.940 DHCPS: send DHCPOFFER on 192.168.15.2 to 0x78:a3:51:26:4c:17
00:44:28.960 DHCPS: receive DHCPREQUEST for 192.168.15.2 from 0x78:a3:51:26:4c:17
00:44:28.960 DHCPS: send DHCPACK on 192.168.15.2 to 0x78:a3:51:26:4c:17
00:44:28.960 DHCPS: 192.168.15.2 assigned to client "1:0x78a351264c17" for 24:00:00
This another router get the expected IP address counter to NetBSD. (we see it in "sh ip dhcp binding" output above)
Here the OS version of the router One Access:
mika-ftth>sh version
Software version : ONEOS10-ADVIP_11N-V4.3R6E19
Software created on : 13/03/13 18:48:55
mika-ftth>
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
From: Valery Ushakov <uwe@stderr.spb.ru>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
set in /etc/dhclient.conf
Date: Sat, 15 Jul 2017 14:40:28 +0300
On Fri, Jul 14, 2017 at 17:30:01 +0000, m.viey@wanadoo.fr wrote:
> the client identifier 0:0xff2259a08800010001203a470000252259a088
> seems to be very long and I think it's a part of the problem. If I
> compare with the transaction from another dhcp request from another
> device (a router on openwrt)this identifier is shorter:
Stupid question: are you sure you are using dhclient?
NetBSD by default uses dhcpcd(8) now. You need to make specific
configuration steps to use dhclient(8). The client id you see is
RFC4361 DUID id, which is what dhcpcd(8) uses by default.
-uwe
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
set in /etc/dhclient.conf
Date: Sat, 15 Jul 2017 13:41:39 +0200
On Fri, Jul 14, 2017 at 05:30:01PM +0000, m.viey@wanadoo.fr wrote:
> Unfortunately, NetBSD send a client-identifier which is not understood by the router. Because the client identifier take the precedence to the mac address if I want get a static IP from the router from NetBSD I must configure the BSD dhcp client for it doesn't send this identifier. But whatever I try to do with the configuration file /etc/dhclient.conf the router always receive a bytes sequence in place of client identifier, and another IP than expected is attribued.
>
> Here is my last try /etc/dhclient.conf:
Stupid question: are you sure you are using dhclient?
Default DHCP client in netbsd-7 is dhcpcd(8), but if you explicitly
configured dhcpclient, it should work too.
Martin
From: Mickael Viey <m.viey@wanadoo.fr>
To: gnats-bugs@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc:
Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
set in /etc/dhclient.conf
Date: Sat, 15 Jul 2017 14:32:27 +0200
I looked into /etc/rc.conf and It appears that is not dhcplient which is
set but dhcpd.
I set dhclient=YES and remove dcpd from /etc/rc.conf and remove dhcpcd
file from rc.d.
So now I get anoher problem dhcpclient doesn't get IP a boot time, but
get an ip when I run /etc/rc.d/dhclient start .
How can I do for run dhclient request at boot time ?
Le 15/07/2017 à 13:45, Martin Husemann a écrit :
> The following reply was made to PR bin/52403; it has been noted by GNATS.
>
> From: Martin Husemann <martin@duskware.de>
> To: gnats-bugs@NetBSD.org
> Cc:
> Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
> set in /etc/dhclient.conf
> Date: Sat, 15 Jul 2017 13:41:39 +0200
>
> On Fri, Jul 14, 2017 at 05:30:01PM +0000, m.viey@wanadoo.fr wrote:
> > Unfortunately, NetBSD send a client-identifier which is not understood by the router. Because the client identifier take the precedence to the mac address if I want get a static IP from the router from NetBSD I must configure the BSD dhcp client for it doesn't send this identifier. But whatever I try to do with the configuration file /etc/dhclient.conf the router always receive a bytes sequence in place of client identifier, and another IP than expected is attribued.
> >
> > Here is my last try /etc/dhclient.conf:
>
> Stupid question: are you sure you are using dhclient?
>
> Default DHCP client in netbsd-7 is dhcpcd(8), but if you explicitly
> configured dhcpclient, it should work too.
>
> Martin
>
From: christos@zoulas.com (Christos Zoulas)
To: gnats-bugs@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc:
Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier set in /etc/dhclient.conf
Date: Sat, 15 Jul 2017 08:40:06 -0400
On Jul 14, 5:30pm, m.viey@wanadoo.fr (m.viey@wanadoo.fr) wrote:
-- Subject: bin/52403: dhclient program doesn't send dhcp-client-identifier s
| send dhcp-client-identifier "\0";
The example in the dhclient.conf man page shows the client identifier to
be entered like an array of hex bytes:
send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
christos
From: Valery Ushakov <uwe@stderr.spb.ru>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
set in /etc/dhclient.conf
Date: Sat, 15 Jul 2017 15:54:48 +0300
On Sat, Jul 15, 2017 at 12:45:00 +0000, Christos Zoulas wrote:
> On Jul 14, 5:30pm, m.viey@wanadoo.fr (m.viey@wanadoo.fr) wrote:
> -- Subject: bin/52403: dhclient program doesn't send dhcp-client-identifier s
>
> | send dhcp-client-identifier "\0";
>
> The example in the dhclient.conf man page shows the client identifier to
> be entered like an array of hex bytes:
>
> send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
dhcp-options(5) is the authoritative reference for that and it shows
both, using client identifier as an example, incidentally:
The string data type specifies either an NVT ASCII string enclosed in
double quotes, or a series of octets specified in hexadecimal,
separated by colons. For example:
option dhcp-client-identifier "CLIENT-FOO";
or
option dhcp-client-identifier 43:4c:49:45:54:2d:46:4f:4f;
-uwe
From: Mickael Viey <m.viey@wanadoo.fr>
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
set in /etc/dhclient.conf
Date: Sat, 15 Jul 2017 15:02:24 +0200
This is a multi-part message in MIME format.
--------------5DB9378AD4275D1640E98FF7
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
yes it's right, but in the example here
https://www.netbsd.org/docs/network/dhcp.html#configure-dhcp not. My
origin problem it was oneOS don't understood non ascii character for
identifier. dhcpcd seems to send hardware addres when it requests.
Anyway I succeed to work with dhclient and send an ascii identifier to
the server. At now I have a probleme with ntp but I think it comes from
my dhclient configuration. I'll keep you informed
Le 15/07/2017 à 14:45, Christos Zoulas a écrit :
> The following reply was made to PR bin/52403; it has been noted by GNATS.
>
> From: christos@zoulas.com (Christos Zoulas)
> To: gnats-bugs@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
> Cc:
> Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier set in /etc/dhclient.conf
> Date: Sat, 15 Jul 2017 08:40:06 -0400
>
> On Jul 14, 5:30pm, m.viey@wanadoo.fr (m.viey@wanadoo.fr) wrote:
> -- Subject: bin/52403: dhclient program doesn't send dhcp-client-identifier s
>
> | send dhcp-client-identifier "\0";
>
> The example in the dhclient.conf man page shows the client identifier to
> be entered like an array of hex bytes:
>
> send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
>
> christos
>
--------------5DB9378AD4275D1640E98FF7
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>yes it's right, but in the example here
<a class="moz-txt-link-freetext" href="https://www.netbsd.org/docs/network/dhcp.html#configure-dhcp">https://www.netbsd.org/docs/network/dhcp.html#configure-dhcp</a> not.
My origin problem it was oneOS don't understood non ascii
character for identifier. dhcpcd seems to send hardware addres
when it requests. Anyway I succeed to work with dhclient and send
an ascii identifier to the server. At now I have a probleme with
ntp but I think it comes from my dhclient configuration. <span
id="result_box" class="short_text" lang="en"><span class="">I'll
keep you informed</span></span></p>
<br>
<div class="moz-cite-prefix">Le 15/07/2017 Ã 14:45, Christos Zoulas
a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:20170715124500.E708D7A237@mollari.NetBSD.org">
<pre wrap="">The following reply was made to PR bin/52403; it has been noted by GNATS.
From: <a class="moz-txt-link-abbreviated" href="mailto:christos@zoulas.com">christos@zoulas.com</a> (Christos Zoulas)
To: <a class="moz-txt-link-abbreviated" href="mailto:gnats-bugs@NetBSD.org">gnats-bugs@NetBSD.org</a>, <a class="moz-txt-link-abbreviated" href="mailto:gnats-admin@netbsd.org">gnats-admin@netbsd.org</a>, <a class="moz-txt-link-abbreviated" href="mailto:netbsd-bugs@netbsd.org">netbsd-bugs@netbsd.org</a>
Cc:
Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier set in /etc/dhclient.conf
Date: Sat, 15 Jul 2017 08:40:06 -0400
On Jul 14, 5:30pm, <a class="moz-txt-link-abbreviated" href="mailto:m.viey@wanadoo.fr">m.viey@wanadoo.fr</a> (<a class="moz-txt-link-abbreviated" href="mailto:m.viey@wanadoo.fr">m.viey@wanadoo.fr</a>) wrote:
-- Subject: bin/52403: dhclient program doesn't send dhcp-client-identifier s
| send dhcp-client-identifier "\0";
The example in the dhclient.conf man page shows the client identifier to
be entered like an array of hex bytes:
send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
christos
</pre>
</blockquote>
<br>
</body>
</html>
--------------5DB9378AD4275D1640E98FF7--
From: Mickael Viey <m.viey@wanadoo.fr>
To: gnats-bugs@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc:
Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
set in /etc/dhclient.conf
Date: Sat, 15 Jul 2017 15:04:48 +0200
Yes it works now I get jut a problem at boot time: dhclient doesn't
request address aumatically and I must run it after.
Le 15/07/2017 à 14:55, Valery Ushakov a écrit :
> The following reply was made to PR bin/52403; it has been noted by GNATS.
>
> From: Valery Ushakov <uwe@stderr.spb.ru>
> To: gnats-bugs@NetBSD.org
> Cc:
> Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
> set in /etc/dhclient.conf
> Date: Sat, 15 Jul 2017 15:54:48 +0300
>
> On Sat, Jul 15, 2017 at 12:45:00 +0000, Christos Zoulas wrote:
>
> > On Jul 14, 5:30pm, m.viey@wanadoo.fr (m.viey@wanadoo.fr) wrote:
> > -- Subject: bin/52403: dhclient program doesn't send dhcp-client-identifier s
> >
> > | send dhcp-client-identifier "\0";
> >
> > The example in the dhclient.conf man page shows the client identifier to
> > be entered like an array of hex bytes:
> >
> > send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
>
> dhcp-options(5) is the authoritative reference for that and it shows
> both, using client identifier as an example, incidentally:
>
> The string data type specifies either an NVT ASCII string enclosed in
> double quotes, or a series of octets specified in hexadecimal,
> separated by colons. For example:
> option dhcp-client-identifier "CLIENT-FOO";
> or
> option dhcp-client-identifier 43:4c:49:45:54:2d:46:4f:4f;
>
> -uwe
>
From: Mickael Viey <m.viey@wanadoo.fr>
To: gnats-bugs@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc:
Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
set in /etc/dhclient.conf
Date: Sat, 15 Jul 2017 15:44:23 +0200
The dhcpclient works correctly now. I succeed to send an identifier to
DHCP server.
But now I have a problem dhclient run at boot time but doesn't get any
information from the DHCP server which log nothing during BSD boot.
So ntpdate send an error when booting because there is not
domain-name-servers set in resolv.conf.
However if i run the rc.d script after boot I get an address, see the
request in router monitoring. Bellow some transaction done just after a
boot:
dk17# ifconfig
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities=3f00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx>
capabilities=3f00<UDP4CSUM_Rx,UDP4CSUM_Tx>
enabled=0
ec_capabilities=3<VLAN_MTU,VLAN_HWTAGGING>
ec_enabled=0
address: 00:25:22:59:a0:88
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
inet6 fe80::225:22ff:fe59:a088%re0 prefixlen 64 scopeid 0x1
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
dk17# cat /etc/resolv.conf
# Generated by resolvconf
dk17# /etc/rc.d/dhclient start
Starting dhclient.
dk17# ifconfig
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities=3f00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx>
capabilities=3f00<UDP4CSUM_Rx,UDP4CSUM_Tx>
enabled=0
ec_capabilities=3<VLAN_MTU,VLAN_HWTAGGING>
ec_enabled=0
address: 00:25:22:59:a0:88
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 192.168.15.1 netmask 0xffffff00 broadcast 192.168.15.255
inet6 fe80::225:22ff:fe59:a088%re0 prefixlen 64 scopeid 0x1
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
dk17# cat /etc/resolv.conf
# Generated by resolvconf
nameserver 195.5.209.150
nameserver 194.79.128.150
dk17# /etc/rc.d/ntpdate start
Setting date via ntp.
dk17# cat /etc/dhclient.conf
send dhcp-client-identifier "dk17";
request subnet-mask, broadcast-address, routers, domain-name-servers;
timeout 60;
retry 60;
select-timeout 5;
script "/sbin/dhclient-script";
lease {
interface "re0";
}
dk17#
Any idea ?
Le 15/07/2017 à 15:05, Mickael Viey a écrit :
> The following reply was made to PR bin/52403; it has been noted by GNATS.
>
> From: Mickael Viey <m.viey@wanadoo.fr>
> To: gnats-bugs@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
> Cc:
> Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
> set in /etc/dhclient.conf
> Date: Sat, 15 Jul 2017 15:04:48 +0200
>
> Yes it works now I get jut a problem at boot time: dhclient doesn't
> request address aumatically and I must run it after.
>
>
> Le 15/07/2017 à 14:55, Valery Ushakov a écrit :
> > The following reply was made to PR bin/52403; it has been noted by GNATS.
> >
> > From: Valery Ushakov <uwe@stderr.spb.ru>
> > To: gnats-bugs@NetBSD.org
> > Cc:
> > Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
> > set in /etc/dhclient.conf
> > Date: Sat, 15 Jul 2017 15:54:48 +0300
> >
> > On Sat, Jul 15, 2017 at 12:45:00 +0000, Christos Zoulas wrote:
> >
> > > On Jul 14, 5:30pm, m.viey@wanadoo.fr (m.viey@wanadoo.fr) wrote:
> > > -- Subject: bin/52403: dhclient program doesn't send dhcp-client-identifier s
> > >
> > > | send dhcp-client-identifier "\0";
> > >
> > > The example in the dhclient.conf man page shows the client identifier to
> > > be entered like an array of hex bytes:
> > >
> > > send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
> >
> > dhcp-options(5) is the authoritative reference for that and it shows
> > both, using client identifier as an example, incidentally:
> >
> > The string data type specifies either an NVT ASCII string enclosed in
> > double quotes, or a series of octets specified in hexadecimal,
> > separated by colons. For example:
> > option dhcp-client-identifier "CLIENT-FOO";
> > or
> > option dhcp-client-identifier 43:4c:49:45:54:2d:46:4f:4f;
> >
> > -uwe
> >
>
From: Mickael Viey <m.viey@wanadoo.fr>
To: gnats-bugs@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
Cc:
Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
set in /etc/dhclient.conf
Date: Sat, 15 Jul 2017 16:25:45 +0200
So I return in dhcpcd set clientid in dhcpcd.conf and all works fine
now. You can close this PR. Dhclient has not the behavior indicated in
https://www.netbsd.org/docs/network/dhcp.html#configure-dhcp however.
Perhaps this article may be updated for dhcpcd instead dhclient which
this is confusing.
Thx all
Le 15/07/2017 à 15:45, Mickael Viey a écrit :
> The following reply was made to PR bin/52403; it has been noted by GNATS.
>
> From: Mickael Viey <m.viey@wanadoo.fr>
> To: gnats-bugs@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
> Cc:
> Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
> set in /etc/dhclient.conf
> Date: Sat, 15 Jul 2017 15:44:23 +0200
>
> The dhcpclient works correctly now. I succeed to send an identifier to
> DHCP server.
>
>
> But now I have a problem dhclient run at boot time but doesn't get any
> information from the DHCP server which log nothing during BSD boot.
>
> So ntpdate send an error when booting because there is not
> domain-name-servers set in resolv.conf.
>
> However if i run the rc.d script after boot I get an address, see the
> request in router monitoring. Bellow some transaction done just after a
> boot:
>
>
> dk17# ifconfig
> re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> capabilities=3f00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx>
> capabilities=3f00<UDP4CSUM_Rx,UDP4CSUM_Tx>
> enabled=0
> ec_capabilities=3<VLAN_MTU,VLAN_HWTAGGING>
> ec_enabled=0
> address: 00:25:22:59:a0:88
> media: Ethernet autoselect (100baseTX full-duplex)
> status: active
> inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
> inet6 fe80::225:22ff:fe59:a088%re0 prefixlen 64 scopeid 0x1
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
> inet 127.0.0.1 netmask 0xff000000
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
> dk17# cat /etc/resolv.conf
> # Generated by resolvconf
> dk17# /etc/rc.d/dhclient start
> Starting dhclient.
> dk17# ifconfig
> re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> capabilities=3f00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx>
> capabilities=3f00<UDP4CSUM_Rx,UDP4CSUM_Tx>
> enabled=0
> ec_capabilities=3<VLAN_MTU,VLAN_HWTAGGING>
> ec_enabled=0
> address: 00:25:22:59:a0:88
> media: Ethernet autoselect (100baseTX full-duplex)
> status: active
> inet 192.168.15.1 netmask 0xffffff00 broadcast 192.168.15.255
> inet6 fe80::225:22ff:fe59:a088%re0 prefixlen 64 scopeid 0x1
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
> inet 127.0.0.1 netmask 0xff000000
> inet6 ::1 prefixlen 128
> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
> dk17# cat /etc/resolv.conf
> # Generated by resolvconf
> nameserver 195.5.209.150
> nameserver 194.79.128.150
> dk17# /etc/rc.d/ntpdate start
> Setting date via ntp.
> dk17# cat /etc/dhclient.conf
> send dhcp-client-identifier "dk17";
>
> request subnet-mask, broadcast-address, routers, domain-name-servers;
>
> timeout 60;
> retry 60;
> select-timeout 5;
>
> script "/sbin/dhclient-script";
>
> lease {
> interface "re0";
> }
> dk17#
>
>
> Any idea ?
>
>
>
> Le 15/07/2017 à 15:05, Mickael Viey a écrit :
> > The following reply was made to PR bin/52403; it has been noted by GNATS.
> >
> > From: Mickael Viey <m.viey@wanadoo.fr>
> > To: gnats-bugs@NetBSD.org, gnats-admin@netbsd.org, netbsd-bugs@netbsd.org
> > Cc:
> > Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
> > set in /etc/dhclient.conf
> > Date: Sat, 15 Jul 2017 15:04:48 +0200
> >
> > Yes it works now I get jut a problem at boot time: dhclient doesn't
> > request address aumatically and I must run it after.
> >
> >
> > Le 15/07/2017 à 14:55, Valery Ushakov a écrit :
> > > The following reply was made to PR bin/52403; it has been noted by GNATS.
> > >
> > > From: Valery Ushakov <uwe@stderr.spb.ru>
> > > To: gnats-bugs@NetBSD.org
> > > Cc:
> > > Subject: Re: bin/52403: dhclient program doesn't send dhcp-client-identifier
> > > set in /etc/dhclient.conf
> > > Date: Sat, 15 Jul 2017 15:54:48 +0300
> > >
> > > On Sat, Jul 15, 2017 at 12:45:00 +0000, Christos Zoulas wrote:
> > >
> > > > On Jul 14, 5:30pm, m.viey@wanadoo.fr (m.viey@wanadoo.fr) wrote:
> > > > -- Subject: bin/52403: dhclient program doesn't send dhcp-client-identifier s
> > > >
> > > > | send dhcp-client-identifier "\0";
> > > >
> > > > The example in the dhclient.conf man page shows the client identifier to
> > > > be entered like an array of hex bytes:
> > > >
> > > > send dhcp-client-identifier 1:0:a0:24:ab:fb:9c;
> > >
> > > dhcp-options(5) is the authoritative reference for that and it shows
> > > both, using client identifier as an example, incidentally:
> > >
> > > The string data type specifies either an NVT ASCII string enclosed in
> > > double quotes, or a series of octets specified in hexadecimal,
> > > separated by colons. For example:
> > > option dhcp-client-identifier "CLIENT-FOO";
> > > or
> > > option dhcp-client-identifier 43:4c:49:45:54:2d:46:4f:4f;
> > >
> > > -uwe
> > >
> >
>
State-Changed-From-To: open->closed
State-Changed-By: gutteridge@NetBSD.org
State-Changed-When: Sun, 23 Dec 2018 01:44:11 +0000
State-Changed-Why:
Submitter indicates this can be closed, and maya@ updated the web docs.
Thanks for the PR!
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.43 2018/01/16 07:36:43 maya Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home