Re: if_addrflags6: Can't assign requested address

[Masanobu SAITOH <msaitoh%execsw.org@localhost>]

On 2018/08/12 0:11, Roy Marples wrote:
> Hi
>
> On 08/08/2018 03:13, Masanobu SAITOH wrote:
> >   Hi.
> >
> >   While testing netbsd-7, I've noticed dhcpcd put the following
> > message:
> >
> > > Configuring network interfaces: wm0wm0: if_addrflags6: Can't assign requested address
> > > wm0: if_addrflags6: Can't assign requested address
> > > wm0: if_addrflags6: Can't assign requested address
> > > wm0: if_addrflags6: Can't assign requested address
> >
> >   Can we ignore this message, or is it a real problem?
> >
> > /etc/dhcpcd.conf is the default.
>
> I just got back and cannot replicate this issue with the latest netbsd-7 sources which ship with dhcpcd-7.0.7.
>
> I use a XEN DOMU for testing. Can you provide more information please?

In /etc/rc.conf:
ip6mode=autohost
ifconfig_wm2=dhcp
dhcpcd_flags="-d"

No /etc/ifconfig.wm2.

When boot:

> Starting network.
> Hostname: amd64-n7.execsw.org
> IPv6 mode: autoconfigured host
> Configuring network interfaces: wm2dhcpcd-7.0.7 starting
> wm2: executing `/libexec/dhcpcd-run-hooks' PREINIT
> wm2: executing `/libexec/dhcpcd-run-hooks' CARRIER
> DUID 00:01:00:01:1c:4b:d9:02:00:26:55:57:20:ac
> wm2: IAID 90:82:9b:a4
> wm2: adding address fe80::1392:4012:56d8:a7a2
> wm2: pltime infinity, vltime infinity
> wm2: delaying IPv6 router solicitation for 0.5 seconds
> wm2: delaying IPv4 for 0.9 seconds
> wm2: carrier lost
> wm2: executing `/libexec/dhcpcd-run-hooks' NOCARRIER
> wm2: deleting address fe80::1392:4012:56d8:a7a2
> wm2: carrier acquired
> wm2: executing `/libexec/dhcpcd-run-hooks' CARRIER
> wm2: IAID 90:82:9b:a4
> wm2: adding address fe80::1392:4012:56d8:a7a2
> wm2: pltime infinity, vltime infinity
> wm2: delaying IPv6 router solicitation for 0.9 seconds
> wm2: delaying IPv4 for 0.2 seconds
> wm2: carrier lost
> wm2: executing `/libexec/dhcpcd-run-hooks' NOCARRIER
> wm2: deleting address fe80::1392:4012:56d8:a7a2
> wm2: if_addrflags6: Can't assign requested address
> wm2: if_addrflags6: Can't assign requested address
> wm2: if_addrflags6: Can't assign requested address
> wm2: if_addrflags6: Can't assign requested address
> wm2: carrier acquired
> wm2: executing `/libexec/dhcpcd-run-hooks' CARRIER
> wm2: IAID 90:82:9b:a4
> wm2: adding address fe80::1392:4012:56d8:a7a2
> wm2: pltime infinity, vltime infinity
> wm2: delaying IPv6 router solicitation for 0.4 seconds
> wm2: delaying IPv4 for 0.2 seconds
> wm2: reading lease `/var/db/dhcpcd/wm2.lease'
> wm2: rebinding lease of 192.168.0.178
> wm2: sending REQUEST (xid 0x63705096), next in 4.4 seconds
> wm2: acknowledged 192.168.0.178 from 192.168.0.2
> wm2: probing address 192.168.0.178/24
> wm2: probing for 192.168.0.178
> wm2: ARP probing 192.168.0.178 (1 of 3), next in 1.6 seconds
> wm2: soliciting an IPv6 router
> wm2: delaying Router Solicitation for LL address
> wm2: sending Router Solicitation
> wm2: ARP probing 192.168.0.178 (2 of 3), next in 1.8 seconds
> wm2: ARP probing 192.168.0.178 (3 of 3), next in 2.0 seconds
> wm2: sending Router Solicitation
> wm2: DAD completed for 192.168.0.178
> wm2: leased 192.168.0.178 for 43200 seconds
> wm2: renew in 21600 seconds, rebind in 37800 seconds
> wm2: writing lease `/var/db/dhcpcd/wm2.lease'
> wm2: adding IP address 192.168.0.178/24 broadcast 192.168.0.255
> wm2: adding route to 192.168.0.0/24
> wm2: adding default route via 192.168.0.2
> wm2: ARP announcing 192.168.0.178 (1 of 2), next in 2.0 seconds
> wm2: executing `/libexec/dhcpcd-run-hooks' BOUND
> forking to background
> forked to background, child pid 250
> .
> Adding interface aliases:.
> Waiting for DAD completion for statically configured addresses...

Does this log help for you?


> Roy


--
-----------------------------------------------
                SAITOH Masanobu (msaitoh%execsw.org@localhost
                                 msaitoh%netbsd.org@localhost)