You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enable kernel configuration CONFIG_IPV6_ROUTE_INFO to allow Talos OS to enable accepting IPv6 RA route information options (24) on the local network.
Description
IPv6 routers broadcast ICMPv6 router advertisement (RA) packets on the local network containing information for autoconfiguration. RA packets can countain prefix information (option 3) which describe prefixes used on the local network. They can also contain route information (option 24) which describe what other prefixes are reachable via the router (RFC 4191).
Accepting RA prefix information is enabled by default and used for interface auto-configuration (SLAAC). It can be controlled by sysctl net.ipv6.conf.*.accept_ra. (Although Talos OS currently needs a small workaround as mentioned in #5632)
Whenever there's multiple router in an IPv6 network and hosts are using auto-configuration. E.g. in my home, there's multiple HomePod mini acting as border gateways for Thread IoT devices. A Thread border gateway maps IoT devices to an IPv6 ULA prefix which is announced on LAN via RA route information. This works out of the box on macOS, iOS, Ubuntu and Windows devices (they add routes for the Thread prefixes), so I assume these accept RA route information by default.
Workaround
If the default router has routes to other local prefixes installed (either by static configuration or by accepting the RA route information), they're reachable from a Talos host with an additional hop via default route.
Also restored support for other SoCs which got lost in 6.1 update (as
much as I could).
Enabled IPv6 RA support.
Fixessiderolabs#642Fixessiderolabs/talos#6727
Signed-off-by: Andrey Smirnov <[email protected]>
Feature Request
Enable kernel configuration
CONFIG_IPV6_ROUTE_INFO
to allow Talos OS to enable accepting IPv6 RA route information options (24) on the local network.Description
IPv6 routers broadcast ICMPv6 router advertisement (RA) packets on the local network containing information for autoconfiguration. RA packets can countain prefix information (option 3) which describe prefixes used on the local network. They can also contain route information (option 24) which describe what other prefixes are reachable via the router (RFC 4191).
Accepting RA prefix information is enabled by default and used for interface auto-configuration (SLAAC). It can be controlled by sysctl
net.ipv6.conf.*.accept_ra
. (Although Talos OS currently needs a small workaround as mentioned in #5632)Accepting RA route information can be controlled by sysctls
net.ipv6.conf.*.accept_ra_rtr_pref
,net.ipv6.conf.*.accept_ra_rt_info_max_plen
andnet.ipv6.conf.*.accept_ra_rt_info_min_plen
. It is disabled by kernel defaults (but I see it working on several systems, so distributions are probably enabling it for autoconfiguration). However, this needs a kernel compiled withCONFIG_IPV6_ROUTE_INFO
, therefore it currently doesn't work in Talos OS.Use-case
Whenever there's multiple router in an IPv6 network and hosts are using auto-configuration. E.g. in my home, there's multiple HomePod mini acting as border gateways for Thread IoT devices. A Thread border gateway maps IoT devices to an IPv6 ULA prefix which is announced on LAN via RA route information. This works out of the box on macOS, iOS, Ubuntu and Windows devices (they add routes for the Thread prefixes), so I assume these accept RA route information by default.
Workaround
If the default router has routes to other local prefixes installed (either by static configuration or by accepting the RA route information), they're reachable from a Talos host with an additional hop via default route.
Version Information
The text was updated successfully, but these errors were encountered: