Re: DHCPv6 PD - 6.3.1: dhcp6_sendmessage: Invalid argument
Roy Marples
Wed Mar 12 01:02:25 2014
Hi!
On 11/03/2014 17:51, Spyros Stathopoulos wrote:
I have been using dhcpcd for about a year now as a prefix delegation
client for
my home network. dhcpcd acquires a /56 from the ISP on the ppp
interface (ppp0)
and assigns a /64 address to the internal LAN interface (int0).
Everything else
is handled by SLAAC. In case it is of any use, I also assign a local
unicast
address to my clients in order to preserve ipv6 connectivity within my
LAN even
if Internet is down (this is handled by dnsmasq/SLAAC along with
dhcpv4). My
configuration file is pretty simple and has served me nice so far.
duid
ipv6only
# without noipv6rs dhcpcd picks my
# local unicast address instead
noipv6rs
interface ppp0
ia_pd 1 int0
Until 6.2 everything worked fine (dhcpcd6.conf is the config file
above)
# /usr/bin/dhcpcd -B -6 --waitip -f /etc/dhcpcd6.conf
dhcpcd[4710]: version 6.2.1 starting
dhcpcd[4710]: DUID 00:01:00:01:1a:0c:ec:07:90:2b:34:d7:a7:61
dhcpcd[4710]: ext0: IAID 34:d7:a7:61
dhcpcd[4710]: int0: IAID 34:d7:a7:41
dhcpcd[4710]: ppp0: IAID 00:00:00:00
dhcpcd[4710]: ppp0: IAID 00:00:00:01
dhcpcd[4710]: ppp0: confirming Prefix Delegation
dhcpcd[4710]: ppp0: REPLY6 received from fe80::eab7:48ff:fefe:ca00
dhcpcd[4710]: int0: adding address 2a02:2149:[whatever]
dhcpcd[4710]: ppp0: renew in 21600 seconds, rebind in 34560 seconds
However with 6.3 I am taking this, and of course int0 has no global
unicast
address from the ISP
dhcpcd[4471]: version 6.3.1 starting
dhcpcd[4471]: DUID 00:01:00:01:1a:0c:ec:07:90:2b:34:d7:a7:61
dhcpcd[4471]: ext0: IAID 34:d7:a7:61
dhcpcd[4471]: int0: IAID 34:d7:a7:41
dhcpcd[4471]: ppp0: IAID 00:00:00:00
dhcpcd[4471]: ppp0: IAID 00:00:00:01
dhcpcd[4471]: ppp0: confirming Prefix Delegation
dhcpcd[4471]: ppp0: dhcp6_sendmessage: sendmsg: Invalid argument
dhcpcd[4471]: timed out
Is this a dhcpcd issue? It is entirely possible that this is a
misconfiguration
on my part, but so far it worked ok. Any ideas on what to look for?
Entirely my fault.
Fixed here:
http://roy.marples.name/projects/dhcpcd/fdiff?v1=0090629d5fbba20b&v2=696b08430bcf23b1&sbs=1
A subsequent patch as well to adjust the hop limit for DHCP messages:
http://roy.marples.name/projects/dhcpcd/ci/202b0d24e5?sbs=0
Can you also test that the renew/confirm steps work with PD in 6.3 as
well? With the patch of course :)
Could be easier to test the latest dhcpcd code in fossil though as a few
related fixes have since gone in.
Thanks
Roy
Archive administrator: postmaster@marples.name