From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: "Rémi Denis-Courmont" <rdenis@simphalempin.com>
Cc: "David Stevens" <dlstevens@us.ibm.com>,
davem@davemloft.net, netdev@vger.kernel.org,
"YOSHIFUJI Hideaki / ????" <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH] IPv6: optionaly validate RAs on raw sockets
Date: Wed, 11 Jul 2007 12:50:12 -0400 [thread overview]
Message-ID: <46950A44.2040808@hp.com> (raw)
In-Reply-To: <200707111919.11746@auguste.remlab.net>
Rémi Denis-Courmont wrote:
> Le mercredi 11 juillet 2007, David Stevens a écrit :
>> That sounds like a good idea to me (FWIW),
>> though I also still think a simple raw-socket
>> application would do it just fine, possibly with
>> no kernel modification at all.
>> But since the kernel wouldn't be maintaining
>> the DNS info, which was my real objection to the
>> original version, netlink would work well too.
>
> One remaining corner case is NFS/IPv6 root, whereby userland won't have
> a chance to start before the network, and hence may miss the solicited
> RA. Or would it? By default, the next unsolicited RA can be anytime
> from now to after 10 minutes, so that's not sufficient. I wouldn't
> personnaly care, but...
>
You've got the same issue with the socket option approach.
-vlad
next prev parent reply other threads:[~2007-07-11 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 18:11 [PATCH] IPv6: optionaly validate RAs on raw sockets Remi Denis-Courmont
2007-07-11 12:29 ` YOSHIFUJI Hideaki / 吉藤英明
2007-07-11 12:44 ` Rémi Denis-Courmont
2007-07-11 13:20 ` David Stevens
2007-07-11 14:10 ` Vlad Yasevich
2007-07-11 16:10 ` David Stevens
2007-07-11 16:19 ` Rémi Denis-Courmont
2007-07-11 16:50 ` Vlad Yasevich [this message]
2007-07-11 20:56 ` David Miller
2007-07-11 21:17 ` James Morris
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=46950A44.2040808@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=rdenis@simphalempin.com \
--cc=yoshfuji@linux-ipv6.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).