Page MenuHomeVyOS Platform

DHCPv6 WAN client seems to be broken again.
Closed, InvalidPublicBUG

Description

As mentioned in previous bug issues over this last year, I finally got DHCPv6 to work on previous versions of VyOS 1.3 rolling releases.

I've been holding off switching to it because various other functionality that I need breaks and then is fixed.

At the moment, all other functionality I need seems to be working but DHCPv6 client to ISP seems to be broken again.

When I "set interfaces ethernet eth2 address dhcpv6" and then commit, no IPv6 address shows up on the eth2 interface and in the /var/log/messages I get:

Sep 4 02:38:07 vyos-summersoft dhcp6c[15564]: dhcp6_ctl_authinit: failed to open /run/dhcp6c/dhcp6c.eth2.sock: No such file or directory

My config for eth2 is as follows:

ethernet eth2 {
     address XX.XXX.XXX.210/28
     address XX.XXX.XXX.212/28
     address XX.XXX.XXX.213/28
     address XX.XXX.XXX.217/28
     address dhcpv6
     description "WAN Network Interface"
     duplex auto
     hw-id 52:54:00:bf:64:0b
     speed auto
 }

This has worked in the past but now it seems to be broken again.

The Vyos version is:

adminuser@router:~$ show version

Version: VyOS 1.3.0-rc6
Release Train: equuleus

Built by: Sentrium S.L.
Built on: Sun 22 Aug 2021 15:37 UTC
Build UUID: 965518de-857d-4e61-ab09-381aadf24eb1
Build Commit ID: 75b37b28b2e9ab

Architecture: x86_64
Boot via: installed image
System type: KVM guest

Hardware vendor: Red Hat
Hardware model: KVM
Hardware S/N:
Hardware UUID: 0e690a2a-a893-4dc3-9430-0ccec9904d6f

Copyright: VyOS maintainers and contributors

I thought all this had been resolved this last year, but evidently still problems????

Or am I doing something wrong in the config?

Details

Difficulty level
Unknown (require assessment)
Version
Vyos 1.3.0-rc6
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Unspecified (please specify)

Event Timeline

I get dhcpv6 address in 1.3.0-rc6 but with prefix /128

vyos@r4-1.3# run show int
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface        IP Address                        S/L  Description
---------        ----------                        ---  -----------
eth0             192.168.122.14/24                 u/u  FOO-BAR
eth1             192.0.2.14/24                     u/u  FOO
                 2001:db8::199/128

I was hoping to get that as well (and have in the past). What could be causing the problem?

Are you getting the error message in /var/log/message that I noted?

Is it something to do with multiple static IPv4 addresses on that interface?

adminuser@vyos:~$ show interfaces ethernet eth2
eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000

link/ether 52:54:00:bf:64:0b brd ff:ff:ff:ff:ff:ff
inet XX.XXX.XXX.210/28 brd 98.187.179.223 scope global eth2
   valid_lft forever preferred_lft forever
inet XX.XXX.XXX.212/28 brd 98.187.179.223 scope global secondary eth2
   valid_lft forever preferred_lft forever
inet XX.XXX.XXX.213/28 brd 98.187.179.223 scope global secondary eth2
   valid_lft forever preferred_lft forever
inet XX.XXX.XXX.217/28 brd 98.187.179.223 scope global secondary eth2
   valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:febf:640b/64 scope link 
   valid_lft forever preferred_lft forever
Description: WAN Network Interface

RX:      bytes  packets  errors  dropped  overrun       mcast
     340488337   500573       0        0        0           0
TX:      bytes  packets  errors  dropped  carrier  collisions
      70372606   315791       0        0        0           0

I don't see any issue yet with multiple static addresses

vyos@r4-1.3:~$ show interfaces 
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface        IP Address                        S/L  Description
---------        ----------                        ---  -----------
eth0             192.168.122.14/24                 u/u  FOO-BAR
eth1             192.0.2.14/24                     u/u  FOO
                 100.64.5.1/24                          
                 100.64.6.1/24                          
                 2001:db8::199/128

I see errors but it works:

Sep  4 12:41:03 r4-1 systemd[1]: Starting WIDE DHCPv6 client on eth1...
Sep  4 12:41:03 r4-1 dhcp6c[4921]: dhcp6_ctl_authinit: failed to open /run/dhcp6c/dhcp6c.eth1.sock: No such file or directory
Sep  4 12:41:03 r4-1 dhcp6c[4921]: client6_init: failed initialize control message authentication
Sep  4 12:41:03 r4-1 dhcp6c[4921]: client6_init: skip opening control port
Sep  4 12:41:03 r4-1 systemd[1]: dhcp6c@eth1.service: Can't open PID file /run/dhcp6c/dhcp6c.eth1.pid (yet?) after start: No such file or directory
Sep  4 12:41:03 r4-1 systemd[1]: Started WIDE DHCPv6 client on eth1.
Sep  4 12:41:03 r4-1 vyos-configd[588]: Sending response 1
Sep  4 12:41:03 r4-1 systemd[1676]: opt-vyatta-config-tmp-new_config_2350.mount: Succeeded.
Sep  4 12:41:03 r4-1 systemd[1]: opt-vyatta-config-tmp-new_config_2350.mount: Succeeded.
Sep  4 12:41:03 r4-1 commit: Successful change to active configuration by user vyos on /dev/pts/0
Sep  4 12:41:04 r4-1 systemd[1]: opt-vyatta-config-tmp-new_config_2350.mount: Succeeded.
Sep  4 12:41:04 r4-1 systemd[1676]: opt-vyatta-config-tmp-new_config_2350.mount: Succeeded.
Sep  4 12:41:04 r4-1 dhcp6c[4922]: update_ia: T1(13500) and/or T2(21600) is locally determined
Sep  4 12:41:07 r4-1 ntpd[1562]: Listen normally on 22 eth1 [2001:db8::199]:123

Do you see any other logs regarding this issue?

No, I saw no other errors that looked related to the DHCPv6 WAN client.

I will try with another box and a fresh installation instead of my production configuration and see what happens and report back here.

I was assuming it wasn't working because of the listed error but if you are getting that error as well and it is working for you then there is something else wrong.

I assumed there shouldn't be any errors. :-)

Sorry for the noise.

I got it working on a test system with minimal config.

I think the problem on my production system is probably that I need to allow the DHCPv6 receive port through the firewall is what I'm guessing.

User error.

Please close.

Thanks.