The version of systemd-networkd in #Ubuntu 22.04 makes substantial improvements in support for delegating #IPv6 prefixes obtained via DHCPv6-PD. If you are (foolishly like me?) trying to use a #Linux server as a home router, this makes it much more viable. I've updated my blog post with details: erik.nygren.org/dhcpv6-pd-on-u

Now that I can have #IPv6 on more than two subnets at home I was also able to setup a DNS64 guest network. Perhaps at some point I'll swap the dual-stack guest network with the IPv6-only NAT64 network and make the latter the default. Unfortunately some enterprise access software doesn't seem to work in IPv6-only NAT64.

Show thread

@nygren That's why 464XLAT exists, for (*¨$!(& that hardcodes obsolete IP literals.

Follow

@UnderEu @nygren it is not necessarily hard coded literals, but more likely coding assumptions that there is only IPv4, e.g. C++ insufficient memory allocation, etc.

Especially seems to fail with DNS64, where they may have made a seemingly reasonable assumption that they only publish IPv4 address, so a DNS resolve will get that address.

Bad assumption: for the usual NAT44 that address is fine, but for NAT64 it will resolve to an IPv6 address, which is probably where the code fails.

Same underlying issue, i.e. assuming IPv4 when it is not, so 464XLAT can fix it... but it means setting up an IPv4 island in the middle of your network, which is not ideal.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.