As of TKL v19.0 IPv6 has "first class" support (or at least close to). We have swapped out udhcpd (IPv4 DHCP only) with dhcpcd (IPv4 & IPv6 DHCP). We did need to do a little hackery to ensure that it all works as intended and it all seems to work quite well.
However there are scenarios where the default config may not be optimal and will make network changes/updates slower than desired/required and pollute the journal a little with extraneous messages.
The 2 cases where this occurs are:
- If IPv6 is not available on the network; dhcpcd will still try to get IPv6 DHCP until it times out - messages:
dhcpcd[_PID_]: eth0: soliciting an IPv6 router
dhcpcd[_PID_]: eth0: no IPv6 Routers available
dhcpcd[_PID_]: timed out
- If IPv6 is available but no DHCPv6 (IPv6 address via SLAAC); again dhcpcd will still try to get IPv6 DHCP but the message is a little different:
dhcpcd[_PID_]: eth0: requesting DHCPv6 information
dhcpcd[_PID_]: eth0: failed to request DHCPv6 information
MVP is probably adding a "disable IPv6" option at first boot and/or within confconsole.
Although it might be better if an "everyboot" hook detected IPv6 DHCP and disable it if no DHCPv6 is discovered.
Having said that, perhaps it's not that big a deal? After all how often will a "normal" TurnKey user be changing their network config?
As of TKL v19.0 IPv6 has "first class" support (or at least close to). We have swapped out
udhcpd(IPv4 DHCP only) withdhcpcd(IPv4 & IPv6 DHCP). We did need to do a little hackery to ensure that it all works as intended and it all seems to work quite well.However there are scenarios where the default config may not be optimal and will make network changes/updates slower than desired/required and pollute the journal a little with extraneous messages.
The 2 cases where this occurs are:
dhcpcd[_PID_]: eth0: soliciting an IPv6 routerdhcpcd[_PID_]: eth0: no IPv6 Routers availabledhcpcd[_PID_]: timed outdhcpcd[_PID_]: eth0: requesting DHCPv6 informationdhcpcd[_PID_]: eth0: failed to request DHCPv6 informationMVP is probably adding a "disable IPv6" option at first boot and/or within confconsole.
Although it might be better if an "everyboot" hook detected IPv6 DHCP and disable it if no DHCPv6 is discovered.
Having said that, perhaps it's not that big a deal? After all how often will a "normal" TurnKey user be changing their network config?