Re: dhcp6leased: problem configuring a public IPv6 address on the external interface

On 12/10/2024 5:43 am, Jurjen Oskam wrote:
>
> Back when using dhcpcd, hostname.em1 just contained a single line
> "autoconf". dhcpcd was able to get a /128 using router solicitations,
> configure that address on the external interface, and then get a
> prefix to configure the other interfaces:
>
> interface em1
>        ipv6rs
>        ia_na 1
>        ia_pd 2 em0/1 vlan4/2 wg0/3 vlan5/4 vlan3/5
>
> The /128 was in a way different range than the prefix.
>
You would have been getting your external /128 address via ia_na, not
slaac. My ISP is configured the same way.
>
> I was able to get things working with dhcp6leased by assigning an
> address from the prefix itself the external interface, like so (note
> that em1 appears both in the "on" and the "for" part):
>
> request prefix delegation on em1 for { em1/128 em0 vlan4 wg0 vlan5 vlan3 }
>
> This doesn't feel right though, but I'm not sure why. I don't know why
> em1 doesn't get a public IPv6 address from slaacd.

dhcp6leased only does PD and not NA at this time. In my case, once I
request a PD from the ISP, I can route all traffic without issue. I can
even pin a /64 from the issued /48 (via PD) to the external interface so
that has a GUA too (I don't need the NA /128 to function, the link-local
is sufficient).

If you need the NA to function, then you'll need to continue to use
dhcpcd. In my case, it was a slight configuration change on how I do
things so I didn't need to go back to dhcpcd and have the simplicity of
dhcp6leased.

Thanks for the tool @florian, very elegant and easy to use.


Cheers,

Jason.