The following reply was made to PR bin/52403; it has been noted by GNATS.
From: Mickael Viey <m.viey%wanadoo.fr@localhost>
To: gnats-bugs%NetBSD.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
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@localhost>
> To: gnats-bugs%NetBSD.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
> 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@localhost>
> > To: gnats-bugs%NetBSD.org@localhost
> > 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@localhost (m.viey%wanadoo.fr@localhost) 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
> >
>