#8317: Haiku needs IPv6 global scope Auto Configuration
--------------------------------------+--------------------------------
Reporter: kallisti5 | Owner: nobody
Type: enhancement | Status: assigned
Priority: normal | Milestone: Unscheduled
Component: Network & Internet/IPv6 | Version: R1/Development
Resolution: | Keywords: radvd global scope
Blocked By: | Blocking:
Platform: All |
--------------------------------------+--------------------------------
Comment (by jeremyvisser):
Agree, IPv6 auto configuration is required, but we should first build
support for SLAAC (stateless autoconfiguration) via ICMPv6 Router
Solicitation / Router Advertisement without worrying about DHCPv6 at least
for the short/medium term.
Unlike IPv4, requesting individual addresses via DHCPv6 is extremely
uncommon. (DHCPv6-PD is quite common, used by ISPs to delegate subnets to
routers, but this is not Haiku's concern unless we want to implement
router functionality.)
Most setups (all typical home setups, and even the enterprise I work at)
use SLAAC (stateless autoconfiguration) which is totally based on ICMPv6
Router Solicitation / Router Advertisements, with no DHCPv6 whatsoever.
(FWIW, Android does not have a DHCPv6 stack whatsoever, with no plans to
implement one, so it's unlikely any sane ISP would start requiring DHCPv6
in the foreseeable future.)
Addressing radvd in the bug description, radvd is not useful to us, since
it used for *sending* Router Advertisements, so also likely not useful at
present. As a client, which I presume is the use case of this bug, you
typically want to be *receiving* Router Advertisements.
On Linux, router solicitiation and receiving of RAs is typically done in-
kernel. On FreeBSD, the rtsold tool does this in userspace. It's possibly
worth investigating rtsold.
--
Ticket URL: <https://dev.haiku-os.org/ticket/8317#comment:3>
Haiku <https://dev.haiku-os.org>
The Haiku operating system.
