Dhcpv6 pd issues

General questions
1

Hi.
I’m not sure if this is an issue with the config or a bug, or maybe things are working and i just don’t know what i’m doing?
I’m trying to configure ipv6 pd on my router and it keeps interfereing with my connection, and in other ways not working.
The wan interface on the router is configured like this.

[edit interfaces ethernet eth0]
vyos@vyos.thekingstech.com# show
 address dhcp
 dhcpv6-options {
     pd 1 {
         interface eth0 {
         }
         length 60
     }
     rapid-commit
 }
 hw-id 00:e0:67:09:a1:4c
 ipv6 {
     address {
         autoconf
     }
 }

The interface doesn’t get an address.

vyos@vyos.thekingstech.com:~$ show interfaces ethernet eth0
eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:e0:67:09:a1:4c brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.179/24 brd 10.0.0.255 scope global dynamic eth0
       valid_lft 171962sec preferred_lft 171962sec
    inet6 fe80::2e0:67ff:fe09:a14c/64 scope link
       valid_lft forever preferred_lft forever

The dhcp6c logs are as follows.

Jun 24 20:05:33 vyos.thekingstech.com systemd[1]: Starting WIDE DHCPv6 client on
 eth0...
-- Subject: A start job for unit dhcp6c@eth0.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit dhcp6c@eth0.service has begun execution.
--
-- The job identifier is 1907.
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: get_duid: extracted an exis
ting DUID from /var/lib/dhcpv6/dhcp6c_duid: 00:01:00:01:28:25:8d:f7:00:e0:67:09:
a1:4c
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: dhcp6_ctl_authinit: failed
to open /run/dhcp6c/dhcp6c.eth0.sock: No such file or directory
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: client6_init: failed initia
lize control message authentication
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: client6_init: skip opening
control port
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>comment [
### Autogenerated by interface.py ###] (37)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>comment [
# man https://www.unix.com/man-page/debian/5/dhcp6c.conf/] (57)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[interfac
e] (9)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <5>[eth0] (4
)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>begin of
closure [{] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[send] (4
)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[ia-pd] (
5)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[1] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>end of se
ntence [;] (1)
Jun 24 20:05:33 vyos.thekingstech.com systemd[1]: dhcp6c@eth0.service: Can't ope
n PID file /run/dhcp6c/dhcp6c.eth0.pid (yet?) after start: No such file or direc
tory
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>comment [
# prefix delegation #1] (22)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>end of cl
osure [}] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>end of se
ntence [;] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[id-assoc
] (8)
Jun 24 20:05:33 vyos.thekingstech.com systemd[1]: Started WIDE DHCPv6 client on
eth0.
-- Subject: A start job for unit dhcp6c@eth0.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit dhcp6c@eth0.service has finished successfully.
--
-- The job identifier is 1907.
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <15>[pd] (2)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <15>[1] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <15>begin of
 closure [{] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[prefix]
(6)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[::] (2)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[/] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[60] (2)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[infinity
] (8)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>end of se
ntence [;] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[prefix-i
nterface] (16)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <5>[eth0] (4
)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>begin of
closure [{] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[sla-len]
 (7)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[4] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>end of se
ntence [;] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[sla-id]
(6)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>[0] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>end of se
ntence [;] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>end of cl
osure [}] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>end of se
ntence [;] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>end of cl
osure [}] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: cfdebug_print: <3>end of se
ntence [;] (1)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: configure_pool: called
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10918]: clear_poolconf: called
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10922]: dhcp6_reset_timer: reset a
timer on eth0, state=INIT, timeo=0, retrans=352
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10922]: client6_send: a new XID (71
f64c) is generated
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10922]: copy_option: set client ID
(len 14)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10922]: copy_option: set elapsed ti
me (len 2)
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10922]: copyout_option: set IA_PD p
refix
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10922]: copyout_option: set IA_PD
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10922]: client6_send: send solicit
to ff02::1:2%eth0
Jun 24 20:05:33 vyos.thekingstech.com dhcp6c[10922]: dhcp6_reset_timer: reset a
timer on eth0, state=SOLICIT, timeo=0, retrans=1054
Jun 24 20:05:34 vyos.thekingstech.com dhcp6c[10922]: copy_option: set client ID
(len 14)
Jun 24 20:05:34 vyos.thekingstech.com dhcp6c[10922]: copy_option: set elapsed ti
me (len 2)
Jun 24 20:05:34 vyos.thekingstech.com dhcp6c[10922]: copyout_option: set IA_PD p
refix
Jun 24 20:05:34 vyos.thekingstech.com dhcp6c[10922]: copyout_option: set IA_PD
Jun 24 20:05:34 vyos.thekingstech.com dhcp6c[10922]: client6_send: send solicit
to ff02::1:2%eth0
Jun 24 20:05:34 vyos.thekingstech.com dhcp6c[10922]: dhcp6_reset_timer: reset a
timer on eth0, state=SOLICIT, timeo=1, retrans=2195
Jun 24 20:05:36 vyos.thekingstech.com dhcp6c[10922]: copy_option: set client ID
(len 14)
Jun 24 20:05:36 vyos.thekingstech.com dhcp6c[10922]: copy_option: set elapsed ti
me (len 2)
Jun 24 20:05:36 vyos.thekingstech.com dhcp6c[10922]: copyout_option: set IA_PD p
refix
Jun 24 20:05:36 vyos.thekingstech.com dhcp6c[10922]: copyout_option: set IA_PD
Jun 24 20:05:36 vyos.thekingstech.com dhcp6c[10922]: client6_send: send solicit
to ff02::1:2%eth0
Jun 24 20:05:36 vyos.thekingstech.com dhcp6c[10922]: dhcp6_reset_timer: reset a
timer on eth0, state=SOLICIT, timeo=2, retrans=4476
Jun 24 20:05:41 vyos.thekingstech.com dhcp6c[10922]: copy_option: set client ID
(len 14)
Jun 24 20:05:41 vyos.thekingstech.com dhcp6c[10922]: copy_option: set elapsed ti
me (len 2)
Jun 24 20:05:41 vyos.thekingstech.com dhcp6c[10922]: copyout_option: set IA_PD p
refix
2

Hello @nktech1135

Your ISP provide you with an IPv6 address or prefix?
If the prefix then ipv6 address autoconf on the eth0 interface is not required.
I can give an example of my working config when the provider an IPv6 prefix:

set interfaces ethernet eth0 dhcpv6-options pd 0 interface eth1 sla-id '1'
set interfaces ethernet eth0 dhcpv6-options pd 0 length '64'
set interfaces ethernet eth1 ipv6 address autoconf
set service router-advert interface eth1 name-server '2001:4860:4860::8888'
set service router-advert interface eth1 other-config-flag
set service router-advert interface eth1 prefix ::/64
1 Like
3

Thanks for that. This is an interesting looking config. I guess i’m still to ipv4 minded as i’m a little confused on how this traffic can route if only eth1 has an address.
Seems to me it should hop from eth1>eth0>internet, but from what you’re showing it would be eth1>internet, Is this correct?