Rémi and Simon give my responses very eloquently. Although you could
have yet-another-network-daemon redundantly process RA messages, the
kernel is doing it already and it makes sense to just push this
information to userland using /proc and/or netlink. Although parsing
RA messages and processin
> diff -ruHpN -X dontdiff linux-2.6.22-rc5-orig/include/net/ip6_rdnss.h
> linux-2.6.22-rc5/include/net/ip6_rdnss.h
> --- linux-2.6.22-rc5-orig/include/net/ip6_rdnss.h1969-12-31
> 19:00:00.0 -0500
> +++ linux-2.6.22-rc5/include/net/ip6_rdnss.h2007-06-21
> 18:16:33.0 -0400 @@ -0,0 +1
/proc/net/ipv6_dns
+ * (for human readability) and via netlink.
+ *
+ * Authors:
+ * C. Scott Ananian<[EMAIL PROTECTED]>
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ *
g/net/ipv6/ip6_rdnss.c 1969-12-31
19:00:00.0 -0500
+++ linux-2.6.22-rc5/net/ipv6/ip6_rdnss.c 2007-06-19 19:01:04.0
-0400
@@ -0,0 +1,260 @@
+/*
+ * Recursive DNS Server autoconfiguration for IPv6
+ * Linux INET6 implementation.
+ *
+ * Authors:
+ * C
[Re-sending an earlier email, this time with a wider distribution and
more details.]
I'd like to get opinions on how DNS information packaged with IPv6
Router Advertisement packages should be handled. The OLPC project
(laptop.org) is currently planning to use this for DNS
autoconfiguration. The
