Groups | Search | Server Info | Login | Register


Groups > linux.debian.maint.ipv6 > #180

Bug#1101842: ITP: racd -- Extensible IPv6 Router Advertisement Client Daemon

From Daniel Gröber <dxld@darkboxed.org>
Newsgroups linux.debian.bugs.dist, linux.debian.devel, linux.debian.maint.ipv6
Subject Bug#1101842: ITP: racd -- Extensible IPv6 Router Advertisement Client Daemon
Date 2025-04-01 18:20 +0200
Message-ID <KwMvf-aiu4-11@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Cross-posted to 3 groups.

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Package: wnpp
Severity: wishlist
Owner: Daniel Gröber <dxld@darkboxed.org>
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-ipv6@lists.debian.org, dxld@darkboxed.org

Forging ever on along the IPv6-only path.

RAcd is a peice of glue intended to allow system components such as
src:clatd to interface easily with IPv6 router advertisements, but while
I'm at it I may as well fix my gripes with Linux ipv6/addrconf — something
that will ofc. be configurable.

The relatively recent addition of PREF64 to IPv6 standards has shown that
ossification is a terrible idea in a modern protocol implementations and
leads to sluggish deployment of perfectly good, but new, ideas.

RAcd is my fork of rdnssd (src:ndisc6) with DNS-configuration specific code
pushed out of the C-part of the program with a generalized mechanism to let
the system interface with it in it's place.

* Package name    : racd
  Version         : 0.1 (native package)
  Upstream Contact: Daniel Gröber <dxld@darkboxed.org>
* License         : GPL-2 or GPL-3
  Programming Lang: C
  Description     : Extensible IPv6 Router Advertisement Client Daemon

 The RAcd userspace daemon takes over responsibility for IPv6 RAs from the
 Linux kernel. It does so by kicking off the necessary system changes using
 a system specific script akin to a DHCP client.
 .
 RAcd fixes some rough edges in the kernel ipv6/addrconf facility and goes
 back to the good'ol unix ways of being simple, portable and composible.

I haven't 100% decided on the script interface yet. I'm thinking either
(binary) files in /run/racd/$IFACE (in raw ICMPv6 option format) with a
commandline tool to query them or just steal the dhclient design involving
envvars.

I like the idea of having the state of RAs passively queryable in the
system somewhere so we could (in theory) always check what the state of the
system should be given a RA state, but maybe it's not actually so important
given rdisc6 exists for admins.

Personally I always found the dhclient script style to be very hard to work
with so maybe I should just follow my experience here.

I plan on maintaining racd myself, but co-maintainers are, as always,
welcome. Perhaps once some other people get interested in IPv6 again we
could start a team :-).

--Daniel

Back to linux.debian.maint.ipv6 | Previous | NextNext in thread | Find similar


Thread

Bug#1101842: ITP: racd -- Extensible IPv6 Router Advertisement Client Daemon Daniel Gröber <dxld@darkboxed.org> - 2025-04-01 18:20 +0200
  Re: Bug#1101842: ITP: racd -- Extensible IPv6 Router Advertisement Client Daemon Michael Richardson <mcr@sandelman.ca> - 2025-04-01 22:50 +0200
    Re: Bug#1101842: ITP: racd -- Extensible IPv6 Router Advertisement Client Daemon Daniel Gröber <dxld@darkboxed.org> - 2025-04-02 02:20 +0200

csiph-web