When configuring DHCPv6 on an interface like: set interfaces ethernet eth1 vif 1111 address dhcp
We will properly see the IPv6 address entered as a route into the IPv6 routing table:
vyos@vyos:~$ show ipv6 route
Codes: K - kernel route, C - connected, L - local, S - static,
R - RIPng, O - OSPFv3, I - IS-IS, B - BGP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
f - OpenFabric, t - Table-Direct,
> - selected route, * - FIB route, q - queued, r - rejected, b - backup
t - trapped, o - offload failure
L * 2001:db8:1111::1de4/128 is directly connected, eth1.1111, weight 1, 00:00:07
C>* 2001:db8:1111::1de4/128 is directly connected, eth1.1111, weight 1, 00:00:07
K * 2001:db8:1111::1de4/128 [0/256] is directly connected, eth1.1111, weight 1, 00:00:09
C * fe80::/64 is directly connected, eth1, weight 1, 00:02:32
C * fe80::/64 is directly connected, eth1.1111, weight 1, 00:02:32Unfortunately when rebooting the system there is a small gap in the default autoconf / ra_accept settings letting a default route slip through.
vyos@vyos:~$ show ipv6 route
Codes: K - kernel route, C - connected, L - local, S - static,
R - RIPng, O - OSPFv3, I - IS-IS, B - BGP, N - NHRP,
T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
f - OpenFabric, t - Table-Direct,
> - selected route, * - FIB route, q - queued, r - rejected, b - backup
t - trapped, o - offload failure
K>* ::/0 [0/1024] via fe80::250:56ff:feb3:cdba, eth1.1111, weight 1, 00:00:28
K>* 2001:db8:1111::/64 [0/256] is directly connected, eth1.1111, weight 1, 00:00:28
L * 2001:db8:1111::1de4/128 is directly connected, eth1.1111, weight 1, 00:00:24
C>* 2001:db8:1111::1de4/128 is directly connected, eth1.1111, weight 1, 00:00:24
K * 2001:db8:1111::1de4/128 [0/256] is directly connected, eth1.1111, weight 1, 00:00:26