netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <rdenis@simphalempin.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: "C. Scott Ananian" <cscott@laptop.org>,
	cananian@gmail.com, netdev@vger.kernel.org
Subject: Re: [RFD] First draft of RDNSS-in-RA support for IPv6 DNS autoconfiguration
Date: Sat, 23 Jun 2007 19:51:55 +0300	[thread overview]
Message-ID: <200706231952.03096@auguste.remlab.net> (raw)
In-Reply-To: <OFD5BE4667.E4A6D7D5-ON88257303.005932BE-88257303.005C40E3@us.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]

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 kernel should still
> continue to do everything it needs to with the kernel data in the RA.
> Then you just need a hash table (or maybe just a list -- there
> shouldn't be a lot of them) and a timer to delete them when the RDNS
> expiration hits. Easy, right?

The exact thing I pointed out does not work. I *DID* write RA parsing in 
userland in the past.

>         You might have to change the icmp6_filter, if RA's are not
> already copied to raw sockets (I don't know either way offhand),
> but that's a trivial kernel patch; otherwise, I don't believe you
> have to do anything but read the socket and process the RDNS header
> on RAs you receive.

To reiterate:

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?

-- 
Rémi Denis-Courmont
http://www.remlab.net/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2007-06-23 16:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22 23:26 [RFD] First draft of RDNSS-in-RA support for IPv6 DNS autoconfiguration C. Scott Ananian
2007-06-22 23:39 ` Michael Buesch
2007-06-23  0:09   ` C. Scott Ananian
2007-06-23  2:11     ` Dan Williams
2007-06-23  9:07     ` Michael Buesch
2007-06-23 20:41       ` David Miller
2007-06-22 23:42 ` Michael Buesch
2007-06-23  1:04 ` David Stevens
2007-06-23  1:17   ` Simon Arlott
2007-06-23  4:30     ` David Stevens
2007-06-23  4:50       ` Simon Arlott
2007-06-23  5:12       ` David Miller
2007-06-23  8:23         ` Pierre Ynard
2007-06-24 19:05     ` Olaf Kirch
2007-06-23 13:25   ` Rémi Denis-Courmont
2007-06-23 14:47     ` C. Scott Ananian
2007-06-23 16:40       ` Simon Arlott
2007-06-23 16:48       ` David Stevens
2007-06-23 16:51         ` Rémi Denis-Courmont [this message]
2007-06-23 17:45           ` David Stevens
2007-06-23 18:13             ` Rémi Denis-Courmont
2007-06-23 18:51               ` David Stevens
2007-06-23 19:18                 ` Rémi Denis-Courmont
2007-06-23 20:27             ` Pierre Ynard
2007-06-25  2:17       ` Dan Williams
2007-06-25  2:53         ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200706231952.03096@auguste.remlab.net \
    --to=rdenis@simphalempin.com \
    --cc=cananian@gmail.com \
    --cc=cscott@laptop.org \
    --cc=dlstevens@us.ibm.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).