On Saturday 23 June 2007 03:17, Simon Arlott wrote:
Because then it requires yet another network daemon, RA in
the kernel means there's no need for one to manage adding
auto-configured IP addresses... what's wrong with doing the
same for DNS?
Actually I think an integrated network
On Sat, 2007-06-23 at 10:47 -0400, C. Scott Ananian wrote:
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
From: Dan Williams [EMAIL PROTECTED]
Date: Sun, 24 Jun 2007 22:17:31 -0400
The glibc guys rejected things like periodically stat()-ing resolv.conf.
At least these days such a thing could be re-proposed using
something like inotify(), although it might be difficult
to get glibc to receive that
On Sat, Jun 23, 2007, David Miller wrote:
From: David Stevens [EMAIL PROTECTED]
Auto-configured addresses are used by the kernel. It has to
have those addresses. But the kernel doesn't do DNS look-ups, or
write resolv.conf; that's the difference, for me.
I totally agree with
On Saturday 23 June 2007 02:09:18 C. Scott Ananian wrote:
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
+++
Hello,
Le samedi 23 juin 2007, David Stevens a écrit :
Why not make the application that writes resolv.conf
also listen on a raw ICMPv6 socket? I don't believe you'd need
any kernel changes, then, and it seems pretty simple and
straightforward.
Unfortunately, ICMPv6 raw
Le samedi 23 juin 2007, David Stevens a écrit :
No, in fact! I didn't hear anyone suggesting that all of
neighbor discovery be pushed out of the kernel. All I suggested is
that you read a raw ICMPv6 socket for RA's that have the RDNS header
and the app _process_the_RDNS_header. The
[EMAIL PROTECTED] wrote on 06/23/2007 07:47:06 AM:
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
It would be two pieces looking
On 23/06/07 15:47, C. Scott Ananian wrote:
Advertisements it received. I considered storing the *complete*
Router Advertisement messages received and pushing them unparsed to
userland, just to get around the bogus DNS in the kernel politics
(hint: it's not a resolver in the kernel, it's just
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
Rémi Denis-Courmont [EMAIL PROTECTED] wrote on 06/23/2007 09:51:55
AM:
How do I authenticate SeND RA? How do I deal with the link going down
before the expiration? How do I know this interface is doing autoconf
at all?
The kernel should do the authentication, as it will for other
Rémi Denis-Courmont [EMAIL PROTECTED] wrote on 06/23/2007 11:13:01
AM:
An implementation might perform additional validity checks on the
ICMPv6 message content and discard malformed packets. However, a
portable application must not assume that such validity checks have
been
Le samedi 23 juin 2007, David Stevens a écrit :
This doesn't say that unauthenticated packets must be
delivered, and I don't think the portability of an RDNS daemon is an
issue. But even if you really wanted to run the same code on a
non-Linux machine, it just means that your daemon
Le samedi 23 juin 2007, David Stevens a écrit :
The kernel should do the authentication, as it will for other
RA's,
and should not deliver (IMAO) unauthenticated packets. If it is, I
would consider that a bug (for all cases, not just this), and that
would be a good thing to fix. :-)
On Sat, Jun 23, 2007, David Stevens wrote:
There certainly may be complications I haven't thought of, since
I haven't implemented it. But I still don't see a good case for using the
kernel as a DNS database.
Excuse me for being a bit confused by the approach that you suggest, as
so far
From: Michael Buesch [EMAIL PROTECTED]
Date: Sat, 23 Jun 2007 11:07:14 +0200
Yeah, it might work. But I think the compiler doesn't guarantee
you anything about it.
The compiler actually does guarentee these things, and that's why we
have the endian bitfield macros. You're overreacting, we've
Attached is my first draft of a patch to implement RDNSS-in-Router
Advertisements support for IPv6 (
http://tools.ietf.org/html/draft-jeong-dnsop-ipv6-dns-discovery-12 )
as implemented in radvd ( http://www.litech.org/radvd/ ). It
currently exports the autoconfigured DNS list as
On Saturday 23 June 2007 01:26:19 C. Scott Ananian wrote:
Attached is my first draft of a patch to implement RDNSS-in-Router
Advertisements support for IPv6 (
http://tools.ietf.org/html/draft-jeong-dnsop-ipv6-dns-discovery-12 )
as implemented in radvd ( http://www.litech.org/radvd/ ). It
On Saturday 23 June 2007 01:26:19 C. Scott Ananian wrote:
+struct rdns6_info {
+ rwlock_tlock;
+ struct timer_list expiry_timer;
+ struct rdns6_entry *rdnss_list;
+ struct inet6_dev * in6_dev; /* back pointer for netlink notify */
+
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,58
Scott,
Why not make the application that writes resolv.conf
also listen on a raw ICMPv6 socket? I don't believe you'd need
any kernel changes, then, and it seems pretty simple and
straightforward.
+-DLS
-
To unsubscribe from this list: send the
On 23/06/07 02:04, David Stevens wrote:
Why not make the application that writes resolv.conf
also listen on a raw ICMPv6 socket? I don't believe you'd need
any kernel changes, then, and it seems pretty simple and
straightforward.
Because then it requires yet another network daemon, RA
On Fri, 2007-06-22 at 20:09 -0400, C. Scott Ananian wrote:
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
+++
On 23/06/07 05:30, David Stevens wrote:
[EMAIL PROTECTED] wrote on 06/22/2007 06:17:46 PM:
Is there a reason why you're CC:ing the Sender? Doesn't that end
up in the mailbox(es) of the netdev admin(s)?
On 23/06/07 02:04, David Stevens wrote:
Why not make the application that writes
[EMAIL PROTECTED] wrote on 06/22/2007 06:17:46 PM:
On 23/06/07 02:04, David Stevens wrote:
Why not make the application that writes resolv.conf
also listen on a raw ICMPv6 socket? I don't believe you'd need
any kernel changes, then, and it seems pretty simple and
straightforward.
From: David Stevens [EMAIL PROTECTED]
Date: Fri, 22 Jun 2007 21:30:05 -0700
[EMAIL PROTECTED] wrote on 06/22/2007 06:17:46 PM:
On 23/06/07 02:04, David Stevens wrote:
Why not make the application that writes resolv.conf
also listen on a raw ICMPv6 socket? I don't believe you'd
26 matches
Mail list logo
