dhcpcd: re1: DHCPv6 REPLY: iana not found

[Rhialto]

Since yesterday I have a new arrangemet wrt my IPv6 connection, and I'm
trying to use dhcpcd to manage the addresses tat are assigned to me from
my provider (xs4all.nl). They do native IPv6 via Fritz!Box modems and
(V)VDSL.

Little schematic:

.--------. .-----------. .------.
| xs4all +------+ Fritz!Box +-----re1+ Main +re0---- local network
`--------' `-----------' `------'

So I thought I'd use the example give in the manual page,
dhcpcd.conf(5):

noipv6rs # disable routing solicitation
denyinterfaces eth2 # Don't touch eth2 at all
interface eth0
ipv6rs # enable routing solicitation get the
# default IPv6 route
ia_na 1 # request an IPv6 address
ia_pd 2 eth1/0 # get a /64 and assign it to eth1

This didn't work at all! And when it did things, it did them wrong.
(Of course I adjusted for my interfaces).

It took me a while to realise that this is a devilishly deceptive
example. dhcpcd does not allow end-of-line comments!

That surely should be made clearer in the manual, closer to the example,
and not just the line near the start "Blank lines and lines starting
with # are ignored.".

Now that I've come past this hurdle, after some time (about 40 minutes),
I get syslog messages like in the subject:

Feb 4 20:51:48 murthe dhcpcd[10390]: re1: DHCPv6 REPLY: iana not found

Around the same time, ifconfig shows my IPv6 address has gone
deprecated.

Any idea what's wrong?

This is what gets logged when I restart dhcpcd manually,
and it includes another one of those "iana not found" messages:

Feb 4 20:57:17 murthe dhcpcd[1617]: version 6.7.1 starting
Feb 4 20:57:17 murthe dhcpcd[1617]: DUID xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Feb 4 20:57:17 murthe dhcpcd[1617]: re0: IAID xxxxxxxxxxx
Feb 4 20:57:17 murthe dhcpcd[1617]: re1: IAID xxxxxxxxxxx
Feb 4 20:57:17 murthe dhcpcd[1617]: re1: IAID xxxxxxxxxxx
Feb 4 20:57:17 murthe dhcpcd[1617]: re1: IAID xxxxxxxxxxx
Feb 4 20:57:17 murthe dhcpcd[1617]: re1: creating pseudo interface to handle Prefix Delegation
Feb 4 20:57:17 murthe dhcpcd[1617]: re1: confirming prior DHCPv6 lease
Feb 4 20:57:17 murthe dhcpcd[1617]: re1: rebinding prior DHCPv6 lease
Feb 4 20:57:18 murthe dhcpcd[1617]: re1: rebinding lease of 192.168.178.20
Feb 4 20:57:18 murthe dhcpcd[1617]: re1: changing host route to 192.168.178.20 via 127.0.0.1
Feb 4 20:57:18 murthe dhcpcd[1617]: re1: changing route to 192.168.178.0/24
Feb 4 20:57:18 murthe dhcpcd[1617]: re1: changing default route via 192.168.178.1
Feb 4 20:57:18 murthe dhcpcd[1617]: forked to background, child pid 11370
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: removing default route via 192.168.178.1
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: DHCPv6 REPLY: iana not found
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: soliciting a DHCPv6 lease
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: soliciting an IPv6 router
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::xxxxxxxxxxxeee:a54b
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: adding address 2001:984:4b2a:1:xxxxxxxxxxx871:2a5c/64
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: adding address 2001:984:4b2a:1:xxxxxxxxxxxd00:3aa4/64
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: adding route to 2001:984:4b2a:1::/64
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: adding default route via fe80::xxxxxxxxxxxeee:a54b
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: REPLY6 received from fe80::xxxxxxxxxxxeee:a54b
Feb 4 20:57:18 murthe dhcpcd[11370]: re0: adding address 2001:xxxxxxxxxxx::1/64
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: renew in 1800 seconds, rebind in 2880 seconds
Feb 4 20:57:18 murthe dhcpcd[11370]: re0: adding route to 2001:xxxxxxxxxxx::/64
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: REPLY6 received from fe80::xxxxxxxxxxxeee:a54b
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: adding address 2001:984:4b2a:xxxxxxxxxxxfe1f:968e/128
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: renew in 1800 seconds, rebind in 2880 seconds
Feb 4 21:05:18 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::xxxxxxxxxxxeee:a54b
Feb 4 21:13:57 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::xxxxxxxxxxxeee:a54b


-Olaf.

[Rhialto]

And dhcpcd has been doing more weird things.
It looks like it has been adding network addresses for hosts I've
connected to my own interface!

re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities=3f80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx>
capabilities=3f80<UDP4CSUM_Rx,UDP4CSUM_Tx>
enabled=0
ec_capabilities=3<VLAN_MTU,VLAN_HWTAGGING>
ec_enabled=0
address: 00:e0:4c:1f:96:8e
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 192.168.178.20 netmask 0xffffff00 broadcast 192.168.178.255
inet6 fe80::2e0:4cff:fe1f:968e%re1 prefixlen 64 scopeid 0x2
inet6 2001:984:4b2a:1:1d38:3900:5871:2a5c prefixlen 64
inet6 2001:984:4b2a:1:9130:93cf:ad00:3aa4 prefixlen 64 temporary
inet6 2001:984:4b2a:1:2e0:4cff:fe1f:968e prefixlen 128
inet6 2001:888:0:3:587a:8297:386c:f47c prefixlen 64 deprecated
inet6 2001:43f8:1f4:100:6d37:3044:5b16:1f44 prefixlen 64 deprecated
inet6 2001:4168:3:0:f4fc:2643:f50f:aecc prefixlen 64 deprecated
inet6 2001:41d0:2:55c2:1b1a:32fb:3380:bc1f prefixlen 64 deprecated
inet6 2a00:1158:3:0:d989:9409:2294:c346 prefixlen 64 deprecated
-> inet6 2001:888:0:1:c37e:ee5d:d756:5b14 prefixlen 64 deprecated
inet6 2001:770:400:1d:b4e6:eda:da13:d21a prefixlen 64 deprecated
inet6 2001:41d0:8:da47:87ab:d00e:df1f:f5ef prefixlen 64 deprecated
inet6 2001:738:0:850:e4f4:2182:9f40:e664 prefixlen 64 deprecated
inet6 2001:43f8:1f5:100:740a:2e97:217e:3d52 prefixlen 64 deprecated
inet6 2001:67c:1360:8c01:dc84:9807:dd5b:9e81 prefixlen 64 deprecated
inet6 2001:7b8:3:37:d02f:1397:d74a:9eed prefixlen 64 deprecated
inet6 2001:67c:1562:0:f479:47f6:6446:b16 prefixlen 64 deprecated
inet6 2001:67c:1560:8001:b80a:a3c6:f2a8:b8f8 prefixlen 64 deprecated
inet6 2a03:7900:2:0:7c9f:2ae6:856e:b74b prefixlen 64 deprecated
inet6 2a03:b0c0:2:d0:b6f:a01e:3a46:f81f prefixlen 64 deprecated
inet6 2001:9e0:408:0:6dd8:9d48:fbd4:12c2 prefixlen 64 deprecated
inet6 2001:980:130b:1:b049:536e:8db6:9526 prefixlen 64 deprecated

shell.xs4all.nl has IPv6 address 2001:888:0:1::9

Why???? Is it the Fritz!Box sending out stupid messages, or is it dhcpcd?

-Olaf.

[Roy Marples]

Hi Rhialto

Post by Rhialto
Since yesterday I have a new arrangemet wrt my IPv6 connection, and I'm
trying to use dhcpcd to manage the addresses tat are assigned to me from
my provider (xs4all.nl). They do native IPv6 via Fritz!Box modems and
(V)VDSL.
.--------. .-----------. .------.
| xs4all +------+ Fritz!Box +-----re1+ Main +re0---- local network
`--------' `-----------' `------'
So I thought I'd use the example give in the manual page,
noipv6rs # disable routing solicitation
denyinterfaces eth2 # Don't touch eth2 at all
interface eth0
ipv6rs # enable routing solicitation get the
# default IPv6 route
ia_na 1 # request an IPv6 address
ia_pd 2 eth1/0 # get a /64 and assign it to eth1
This didn't work at all! And when it did things, it did them wrong.
(Of course I adjusted for my interfaces).
It took me a while to realise that this is a devilishly deceptive
example. dhcpcd does not allow end-of-line comments!
That surely should be made clearer in the manual, closer to the example,
and not just the line near the start "Blank lines and lines starting
with # are ignored.".

Heh, that's a fair cop!
I'll get that fixed.

Post by Rhialto
Now that I've come past this hurdle, after some time (about 40 minutes),
Feb 4 20:51:48 murthe dhcpcd[10390]: re1: DHCPv6 REPLY: iana not found

That message is from the DHCPv6 server.

Post by Rhialto
Around the same time, ifconfig shows my IPv6 address has gone
deprecated.
Any idea what's wrong?

The kernel markes the address as deprecated when the preferred lifetime
expires but the valid lifetime is still ticking.

Post by Rhialto
This is what gets logged when I restart dhcpcd manually,
Feb 4 20:57:17 murthe dhcpcd[1617]: version 6.7.1 starting
Feb 4 20:57:17 murthe dhcpcd[1617]: DUID xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Feb 4 20:57:17 murthe dhcpcd[1617]: re0: IAID xxxxxxxxxxx
Feb 4 20:57:17 murthe dhcpcd[1617]: re1: IAID xxxxxxxxxxx
Feb 4 20:57:17 murthe dhcpcd[1617]: re1: IAID xxxxxxxxxxx
Feb 4 20:57:17 murthe dhcpcd[1617]: re1: IAID xxxxxxxxxxx
Feb 4 20:57:17 murthe dhcpcd[1617]: re1: creating pseudo interface to handle Prefix Delegation
Feb 4 20:57:17 murthe dhcpcd[1617]: re1: confirming prior DHCPv6 lease
Feb 4 20:57:17 murthe dhcpcd[1617]: re1: rebinding prior DHCPv6 lease
Feb 4 20:57:18 murthe dhcpcd[1617]: re1: rebinding lease of 192.168.178.20
Feb 4 20:57:18 murthe dhcpcd[1617]: re1: changing host route to 192.168.178.20 via 127.0.0.1
Feb 4 20:57:18 murthe dhcpcd[1617]: re1: changing route to 192.168.178.0/24
Feb 4 20:57:18 murthe dhcpcd[1617]: re1: changing default route via 192.168.178.1
Feb 4 20:57:18 murthe dhcpcd[1617]: forked to background, child pid 11370
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: removing default route via 192.168.178.1
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: DHCPv6 REPLY: iana not found
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: soliciting a DHCPv6 lease
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: soliciting an IPv6 router
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::xxxxxxxxxxxeee:a54b
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: adding address 2001:984:4b2a:1:xxxxxxxxxxx871:2a5c/64
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: adding address 2001:984:4b2a:1:xxxxxxxxxxxd00:3aa4/64
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: adding route to 2001:984:4b2a:1::/64
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: adding default route via fe80::xxxxxxxxxxxeee:a54b
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: REPLY6 received from fe80::xxxxxxxxxxxeee:a54b
Feb 4 20:57:18 murthe dhcpcd[11370]: re0: adding address 2001:xxxxxxxxxxx::1/64
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: renew in 1800 seconds, rebind in 2880 seconds
Feb 4 20:57:18 murthe dhcpcd[11370]: re0: adding route to 2001:xxxxxxxxxxx::/64
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: REPLY6 received from fe80::xxxxxxxxxxxeee:a54b
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: adding address 2001:984:4b2a:xxxxxxxxxxxfe1f:968e/128
Feb 4 20:57:18 murthe dhcpcd[11370]: re1: renew in 1800 seconds, rebind in 2880 seconds
Feb 4 21:05:18 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::xxxxxxxxxxxeee:a54b
Feb 4 21:13:57 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::xxxxxxxxxxxeee:a54b

I don't see dhcpcd doing anything wrong there.
Why not add the -d option to the commandline or add the debug directive
to dhcpcd.conf?

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Rhialto]

Post by Roy Marples

Post by Rhialto
Feb 4 20:51:48 murthe dhcpcd[10390]: re1: DHCPv6 REPLY: iana not found

That message is from the DHCPv6 server.

So I guess I'll have to go to AVM, the maker of the Fritz!Box, probably.
Could it refer to some option that dhcpcd is sending, or failing to
send? I see these few references to iana in the dhcpcd source:

dhcp-common.c:vivso_find(uint32_t iana_en, const void *arg)
dhcp-common.c: if (opt->option == iana_en)
dhcp-common.c: if (opt->option == iana_en)

(I didn't look at that in context yet so this may be barking up the
wrong tree.)

(There seem some other weird things with the Fritz!Box and IPv6 so it
may well be its problem!)

Post by Roy Marples
The kernel markes the address as deprecated when the preferred lifetime
expires but the valid lifetime is still ticking.

Makes sense. But is it possible to simply ignore the lifetime and set
the addresses as fixed? Because in practice they are supposed to be,
with this ISP.

Post by Roy Marples
I don't see dhcpcd doing anything wrong there.
Why not add the -d option to the commandline or add the debug directive
to dhcpcd.conf?

I'll do that when I am free to experiment a bit more.

Post by Roy Marples
Roy

-Olaf.

[Martin Husemann]

Post by Rhialto
(There seem some other weird things with the Fritz!Box and IPv6 so it
may well be its problem!)

FWIW, I use a Fritz!Box and a IPv4/IPv6 setup as well and have not seen
any problems.

Martin

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Rhialto]

Post by Martin Husemann

Post by Rhialto
(There seem some other weird things with the Fritz!Box and IPv6 so it
may well be its problem!)

FWIW, I use a Fritz!Box and a IPv4/IPv6 setup as well and have not seen
any problems.

My issue is specifically that despite having set up my Main machine
in Permit Access -> IPv6 as "Open firewall completely for this device in
the home network", sometimes it decides to block connections anyway.

In one case it may have been when the main IPv6 address was deprecated,
but in another it did block it after a reboot and only some fiddling
there with turning it off and on again, or changing the name (which had
mysteriously changed into "fritz"), or something else which I cannot
reconstruct, made it allow it again.

Post by Martin Husemann
Martin

-Olaf.

[Roy Marples]

Post by Roy Marples

Post by Rhialto
So I thought I'd use the example give in the manual page,
noipv6rs # disable routing solicitation
denyinterfaces eth2 # Don't touch eth2 at all
interface eth0
ipv6rs # enable routing solicitation get the
# default IPv6 route
ia_na 1 # request an IPv6 address
ia_pd 2 eth1/0 # get a /64 and assign it to eth1
This didn't work at all! And when it did things, it did them wrong.
(Of course I adjusted for my interfaces).
It took me a while to realise that this is a devilishly deceptive
example. dhcpcd does not allow end-of-line comments!
That surely should be made clearer in the manual, closer to the example,
and not just the line near the start "Blank lines and lines starting
with # are ignored.".

Heh, that's a fair cop!
I'll get that fixed.

Fixed here:
http://roy.marples.name/projects/dhcpcd/vpatch?from=3791f0d433c8b3612f4fdcc95dbdf24f8401b2c9&to=6b6ca396e47617d040ff7423fe461d25d05346ba

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Roy Marples]

Post by Rhialto

Post by Roy Marples

Post by Rhialto
Feb 4 20:51:48 murthe dhcpcd[10390]: re1: DHCPv6 REPLY: iana not found

That message is from the DHCPv6 server.

So I guess I'll have to go to AVM, the maker of the Fritz!Box, probably.
Could it refer to some option that dhcpcd is sending, or failing to
dhcp-common.c:vivso_find(uint32_t iana_en, const void *arg)
dhcp-common.c: if (opt->option == iana_en)
dhcp-common.c: if (opt->option == iana_en)
(I didn't look at that in context yet so this may be barking up the
wrong tree.)

It's perfectly possible.
dhcpcd encodes a vendor class option in each DHCPv6 message.
dhcpcd has an iana enterprise number of 40712:
https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers

The real question is why the Fritz! box is trying to do anything with
that field at all - it's there just for informative purposes.

Post by Rhialto
(There seem some other weird things with the Fritz!Box and IPv6 so it
may well be its problem!)

Post by Roy Marples
The kernel markes the address as deprecated when the preferred lifetime
expires but the valid lifetime is still ticking.

Makes sense. But is it possible to simply ignore the lifetime and set
the addresses as fixed? Because in practice they are supposed to be,
with this ISP.

So maybe the ISP should note they have an infinite lifetime in the RA or
DHCPv6 message?
The protocols supports this.

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Roy Marples]

Post by Martin Husemann

Post by Rhialto
(There seem some other weird things with the Fritz!Box and IPv6 so it
may well be its problem!)

FWIW, I use a Fritz!Box and a IPv4/IPv6 setup as well and have not seen
any problems.

There are Fritz! boxes that work and those that don't.

Other the years, I frequently get reports about dhcpcd not working with
a Fritz! box because the Fritz! box barfs on anything it does not
understand. This includes rapid_comit, clientid being anything other
than a standard mac address and it's refusal to include a DHCP server id
in quite old versions.

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Martin Husemann]

Post by Roy Marples
Other the years, I frequently get reports about dhcpcd not working with
a Fritz! box because the Fritz! box barfs on anything it does not
understand.

Ah, and of course I forgot: I do never use the dhcp server in any of the
Fritz! boxes around here[1] - so sorry for the noise.

Martin
[1] beyound IPv6 prefix delegation via a dhcpcd "test" hack

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Rhialto]

Post by Roy Marples
Other the years, I frequently get reports about dhcpcd not working with
a Fritz! box because the Fritz! box barfs on anything it does not
understand. This includes rapid_comit, clientid being anything other
than a standard mac address and it's refusal to include a DHCP server id
in quite old versions.

This one has a checkbox to enable or disable rapid_comit so one would
expect that it knows about it.

Just now I got another alien address assigned (I shortened the lines a
bit):

23:02:49 dhcpcd[21800]: re1: Router Advertisement from fe80::ca0e:14ff:feee:a54b
23:02:49 dhcpcd[21800]: re1: adding address 2001:984:4b2a:1:1d38:3900:5871:2a5c/64
23:02:49 dhcpcd[21800]: re1: pltime 3600 seconds, vltime 6715 seconds
23:02:49 dhcpcd[21800]: re1: executing `/libexec/dhcpcd-run-hooks' ROUTERADVERT
23:03:15 dhcpcd[21800]: re1: Router Advertisement from fe80::ca0e:14ff:feee:a54b

Here, this one is definitely not mine:

23:03:15 dhcpcd[21800]: re1: adding address 2001:984:4b2a:1:1d38:3900:5871:2a5c/64
23:03:15 dhcpcd[21800]: re1: pltime 3600 seconds, vltime 6689 seconds
23:03:15 dhcpcd[21800]: re1: adding address 2001:bc8:30d3:0:6363:549e:8149:be05/64
23:03:15 dhcpcd[21800]: re1: pltime 0 seconds, vltime 7200 seconds
23:03:15 dhcpcd[21800]: re1: adding route to 2001:bc8:30d3::/64
23:03:15 dhcpcd[21800]: re1: waiting for Router Advertisement DAD to complete
23:03:16 dhcpcd[21800]: re1: Router Advertisement DAD completed
23:03:16 dhcpcd[21800]: re1: executing `/libexec/dhcpcd-run-hooks' ROUTERADVERT
23:03:18 ntpd[14026]: Listen normally on 17 re1 [2001:bc8:30d3:0:6363:549e:8149:be05]:123
23:03:18 ntpd[14026]: new interface(s) found: waking up resolver

That's weird, isn't it??

Post by Roy Marples
Roy

-Olaf.

[Roy Marples]

Post by Rhialto
And dhcpcd has been doing more weird things.
It looks like it has been adding network addresses for hosts I've
connected to my own interface!
re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities=3f80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx>
capabilities=3f80<UDP4CSUM_Rx,UDP4CSUM_Tx>
enabled=0
ec_capabilities=3<VLAN_MTU,VLAN_HWTAGGING>
ec_enabled=0
address: 00:e0:4c:1f:96:8e
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 192.168.178.20 netmask 0xffffff00 broadcast 192.168.178.255
inet6 fe80::2e0:4cff:fe1f:968e%re1 prefixlen 64 scopeid 0x2
inet6 2001:984:4b2a:1:1d38:3900:5871:2a5c prefixlen 64
inet6 2001:984:4b2a:1:9130:93cf:ad00:3aa4 prefixlen 64 temporary
inet6 2001:984:4b2a:1:2e0:4cff:fe1f:968e prefixlen 128
inet6 2001:888:0:3:587a:8297:386c:f47c prefixlen 64 deprecated
inet6 2001:43f8:1f4:100:6d37:3044:5b16:1f44 prefixlen 64 deprecated
inet6 2001:4168:3:0:f4fc:2643:f50f:aecc prefixlen 64 deprecated
inet6 2001:41d0:2:55c2:1b1a:32fb:3380:bc1f prefixlen 64 deprecated
inet6 2a00:1158:3:0:d989:9409:2294:c346 prefixlen 64 deprecated
-> inet6 2001:888:0:1:c37e:ee5d:d756:5b14 prefixlen 64 deprecated
inet6 2001:770:400:1d:b4e6:eda:da13:d21a prefixlen 64 deprecated
inet6 2001:41d0:8:da47:87ab:d00e:df1f:f5ef prefixlen 64 deprecated
inet6 2001:738:0:850:e4f4:2182:9f40:e664 prefixlen 64 deprecated
inet6 2001:43f8:1f5:100:740a:2e97:217e:3d52 prefixlen 64 deprecated
inet6 2001:67c:1360:8c01:dc84:9807:dd5b:9e81 prefixlen 64 deprecated
inet6 2001:7b8:3:37:d02f:1397:d74a:9eed prefixlen 64 deprecated
inet6 2001:67c:1562:0:f479:47f6:6446:b16 prefixlen 64 deprecated
inet6 2001:67c:1560:8001:b80a:a3c6:f2a8:b8f8 prefixlen 64 deprecated
inet6 2a03:7900:2:0:7c9f:2ae6:856e:b74b prefixlen 64 deprecated
inet6 2a03:b0c0:2:d0:b6f:a01e:3a46:f81f prefixlen 64 deprecated
inet6 2001:9e0:408:0:6dd8:9d48:fbd4:12c2 prefixlen 64 deprecated
inet6 2001:980:130b:1:b049:536e:8db6:9526 prefixlen 64 deprecated
shell.xs4all.nl has IPv6 address 2001:888:0:1::9
Why???? Is it the Fritz!Box sending out stupid messages, or is it dhcpcd?

Going to guess you have temporary IPv6 addresses enabled?
net.inet6.ip6.use_tempaddr = 1

Try setting that to zero.

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Rhialto]

Post by Roy Marples
Going to guess you have temporary IPv6 addresses enabled?
net.inet6.ip6.use_tempaddr = 1
Try setting that to zero.

Indeed I had. I've turned it off now. Let's see if it happens again.
Unfortunately I have no idea what actually triggered it... just that it
was logged. I'm just copying a few of the messages:

Feb 4 22:27:21 murthe dhcpcd[11370]: re1: adding route to 2001:67c:1562::/64
Feb 4 22:35:15 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::ca0e:14ff:feee:a54b
Feb 4 22:39:22 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::ca0e:14ff:feee:a54b
Feb 4 22:39:22 murthe dhcpcd[11370]: re1: adding address 2001:67c:1560:8001:b80a:a3c6:f2a8:b8f8/64
Feb 4 22:39:22 murthe dhcpcd[11370]: re1: adding route to 2001:67c:1560:8001::/64
Feb 4 22:40:23 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::ca0e:14ff:feee:a54b
Feb 4 22:40:23 murthe dhcpcd[11370]: re1: adding address 2a03:7900:2:0:7c9f:2ae6:856e:b74b/64
Feb 4 22:40:23 murthe dhcpcd[11370]: if_addaddress6: Cannot allocate memory
Feb 4 22:40:23 murthe dhcpcd[11370]: re1: adding route to 2a03:7900:2::/64
Feb 4 22:40:25 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::ca0e:14ff:feee:a54b
Feb 4 22:40:25 murthe dhcpcd[11370]: re1: adding address 2a03:7900:2:0:7c9f:2ae6:856e:b74b/64
Feb 4 22:40:25 murthe dhcpcd[11370]: if_addaddress6: Cannot allocate memory

The "if_addaddress6: Cannot allocate memory" doesn't look very
encouraging and was repeated several more times in between similar
messages.

Oh, and I found it very mystifying that I got no error messages at all
from the end-of-line comments in the config file. The manual does say
more or less that that's not supported, but still... before I realised
that my attempts were failing because of that, I had torn out a lot of
hair.

Post by Roy Marples
Roy

-Olaf.

[Roy Marples]

Post by Rhialto
Feb 4 22:27:21 murthe dhcpcd[11370]: re1: adding route to 2001:67c:1562::/64
Feb 4 22:35:15 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::ca0e:14ff:feee:a54b
Feb 4 22:39:22 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::ca0e:14ff:feee:a54b
Feb 4 22:39:22 murthe dhcpcd[11370]: re1: adding address 2001:67c:1560:8001:b80a:a3c6:f2a8:b8f8/64
Feb 4 22:39:22 murthe dhcpcd[11370]: re1: adding route to 2001:67c:1560:8001::/64
Feb 4 22:40:23 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::ca0e:14ff:feee:a54b
Feb 4 22:40:23 murthe dhcpcd[11370]: re1: adding address 2a03:7900:2:0:7c9f:2ae6:856e:b74b/64
Feb 4 22:40:23 murthe dhcpcd[11370]: if_addaddress6: Cannot allocate memory
Feb 4 22:40:23 murthe dhcpcd[11370]: re1: adding route to 2a03:7900:2::/64
Feb 4 22:40:25 murthe dhcpcd[11370]: re1: Router Advertisement from fe80::ca0e:14ff:feee:a54b
Feb 4 22:40:25 murthe dhcpcd[11370]: re1: adding address 2a03:7900:2:0:7c9f:2ae6:856e:b74b/64
Feb 4 22:40:25 murthe dhcpcd[11370]: if_addaddress6: Cannot allocate memory
The "if_addaddress6: Cannot allocate memory" doesn't look very
encouraging and was repeated several more times in between similar
messages.

You're receiving RA's quite quickly.
The IPv6 spec says to create a new temporary address for each prefix
each time we receive one in a RA.
Is the out of memory referring to the sheer quantity of addresses maybe?

Post by Rhialto
Oh, and I found it very mystifying that I got no error messages at all
from the end-of-line comments in the config file. The manual does say
more or less that that's not supported, but still... before I realised
that my attempts were failing because of that, I had torn out a lot of
hair.

Hopefully the next version won't trigger panic buying of hair
restoration products :)

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Rhialto]

Post by Rhialto

Post by Roy Marples
Other the years, I frequently get reports about dhcpcd not working with
a Fritz! box because the Fritz! box barfs on anything it does not
understand. This includes rapid_comit, clientid being anything other
than a standard mac address and it's refusal to include a DHCP server id
in quite old versions.

This one has a checkbox to enable or disable rapid_comit so one would
expect that it knows about it.
Just now I got another alien address assigned (I shortened the lines a

Correction, I put the "not mine" marker on the wrong line.

23:02:49 dhcpcd[21800]: re1: Router Advertisement from fe80::ca0e:14ff:feee:a54b
23:02:49 dhcpcd[21800]: re1: adding address 2001:984:4b2a:1:1d38:3900:5871:2a5c/64
23:02:49 dhcpcd[21800]: re1: pltime 3600 seconds, vltime 6715 seconds
23:02:49 dhcpcd[21800]: re1: executing `/libexec/dhcpcd-run-hooks' ROUTERADVERT
23:03:15 dhcpcd[21800]: re1: Router Advertisement from fe80::ca0e:14ff:feee:a54b
23:03:15 dhcpcd[21800]: re1: adding address 2001:984:4b2a:1:1d38:3900:5871:2a5c/64
23:03:15 dhcpcd[21800]: re1: pltime 3600 seconds, vltime 6689 seconds

Here, this one is definitely not mine:

23:03:15 dhcpcd[21800]: re1: adding address 2001:bc8:30d3:0:6363:549e:8149:be05/64
23:03:15 dhcpcd[21800]: re1: pltime 0 seconds, vltime 7200 seconds
23:03:15 dhcpcd[21800]: re1: adding route to 2001:bc8:30d3::/64
23:03:15 dhcpcd[21800]: re1: waiting for Router Advertisement DAD to complete
23:03:16 dhcpcd[21800]: re1: Router Advertisement DAD completed
23:03:16 dhcpcd[21800]: re1: executing `/libexec/dhcpcd-run-hooks' ROUTERADVERT
23:03:18 ntpd[14026]: Listen normally on 17 re1 [2001:bc8:30d3:0:6363:549e:8149:be05]:123
23:03:18 ntpd[14026]: new interface(s) found: waking up resolver

-Olaf.

[Roy Marples]

Post by Rhialto

Post by Rhialto

Post by Roy Marples
Other the years, I frequently get reports about dhcpcd not working with
a Fritz! box because the Fritz! box barfs on anything it does not
understand. This includes rapid_comit, clientid being anything other
than a standard mac address and it's refusal to include a DHCP server id
in quite old versions.

This one has a checkbox to enable or disable rapid_comit so one would
expect that it knows about it.
Just now I got another alien address assigned (I shortened the lines a

Correction, I put the "not mine" marker on the wrong line.
23:02:49 dhcpcd[21800]: re1: Router Advertisement from
fe80::ca0e:14ff:feee:a54b
23:02:49 dhcpcd[21800]: re1: adding address
2001:984:4b2a:1:1d38:3900:5871:2a5c/64
23:02:49 dhcpcd[21800]: re1: pltime 3600 seconds, vltime 6715 seconds
23:02:49 dhcpcd[21800]: re1: executing `/libexec/dhcpcd-run-hooks' ROUTERADVERT
23:03:15 dhcpcd[21800]: re1: Router Advertisement from
fe80::ca0e:14ff:feee:a54b
23:03:15 dhcpcd[21800]: re1: adding address
2001:984:4b2a:1:1d38:3900:5871:2a5c/64
23:03:15 dhcpcd[21800]: re1: pltime 3600 seconds, vltime 6689 seconds
23:03:15 dhcpcd[21800]: re1: adding address
2001:bc8:30d3:0:6363:549e:8149:be05/64
23:03:15 dhcpcd[21800]: re1: pltime 0 seconds, vltime 7200 seconds
23:03:15 dhcpcd[21800]: re1: adding route to 2001:bc8:30d3::/64
23:03:15 dhcpcd[21800]: re1: waiting for Router Advertisement DAD to complete
23:03:16 dhcpcd[21800]: re1: Router Advertisement DAD completed
23:03:16 dhcpcd[21800]: re1: executing `/libexec/dhcpcd-run-hooks' ROUTERADVERT
23:03:18 ntpd[14026]: Listen normally on 17 re1
[2001:bc8:30d3:0:6363:549e:8149:be05]:123
23:03:18 ntpd[14026]: new interface(s) found: waking up resolver

Looks to me there is a secondary prefix being advertised.
You can check this with tcpdump.

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Rhialto]

Post by Roy Marples
Looks to me there is a secondary prefix being advertised.
You can check this with tcpdump.

Yes, I'm pretty sure it is a Fritz "weirdness" (or just plain bug).
Catching it in the act isn't going to be so simple since I don't know
what triggers it.

Also: this looks like it's assigning a prefix to my second interface, as
asked (as in the example from the manual). But does it add a route for
it? NetBSD 7.0's dhcpcd-run-hooks doesn't know about DELEGATED6 so it
isn't done there.

23:18:31 dhcpcd[21800]: re1: broadcasting RENEW6 (xid 0x114687), next in 9.6 seconds
23:18:31 dhcpcd[21800]: re1: REPLY6 received from fe80::ca0e:14ff:feee:a54b
23:18:31 dhcpcd[21800]: re0: adding address 2001:984:4b2a:fc::1/64
23:18:31 dhcpcd[21800]: re0: pltime 3600 seconds, vltime 7200 seconds
23:18:31 dhcpcd[21800]: re0: executing `/libexec/dhcpcd-run-hooks' DELEGATED6

But when I do a "route get" for some host on that interface, I get the
default route, i.e. not to re0. Looking at it from the local network,
pings don't get replies. I tried it a few hours after re0 was initially
set up, so something could have timed out in the mean time.

It's all so annoying... I had a perfectly working static setup with a
tunnel for IPv6 but now that I'm forced to use the FritzBox and its
dynamic stuff, my whole network is broken. </whine>

Post by Roy Marples
Roy

-Olaf.