From: Loganaden Velvindron <loganaden@gmail.com>
To: Loganaden Velvindron <loganaden@gmail.com>,
Fernando Gont <fernando@gont.com.ar>,
netdev <netdev@vger.kernel.org>
Subject: Re: Fwd: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery
Date: Thu, 22 Aug 2013 09:39:45 +0400 [thread overview]
Message-ID: <CAOp4FwTcJX4dy23oZv6bU-+Fe-ZmwXp0WGonXVC_xvqPhpmxFQ@mail.gmail.com> (raw)
In-Reply-To: <CAOp4FwTPuY9H=w_A7vdwiJv3RqKLWnf+Nk=q8xaa9sN6+g4j1g@mail.gmail.com>
On Mon, Aug 19, 2013 at 12:52 AM, Loganaden Velvindron
<loganaden@gmail.com> wrote:
> On Thu, Aug 15, 2013 at 2:25 PM, Hannes Frederic Sowa
> <hannes@stressinduktion.org> wrote:
>>
>> On Thu, Aug 15, 2013 at 02:14:46PM +0400, Loganaden Velvindron wrote:
>> > I'm not sure if you got my previous mails, but I'd like to know a
>> > couple of things:
>>
>> Ah, you asked me off-list. So, for a wider audience, I copy & paste my answers
>> from the just answered mail. ;)
>>
>> > 1) How can I test this diff ?
>>
>> Actually, nothing should change at all.
>>
>> Myself, I used scapy to construct some packets and send it to a system
>> with the patched kernel and had some printks sprinkeled in the source
>> while watching tcpdump.
>>
>> > 2) It's developed against which git brach ? linux-next ?
>>
>> Yes, I targeted linux-next. But it should apply to older kernels
>> without too much fuzz as well.
>>
>
> I've tested with linux-next.
>
>> > 3) What will/could break with this diff in a production environment ?
>>
>> RA messages could get fragmented if a speaker puts lots of options in it. I
>> hope all RA speakers already spread the options over multiple RAs, but I don't
>> know. In case the RA is fragmented it will now be dropped silently.
>>
>
> My IPv6 gateway machine runs OpenBSD, and so far, no issues with it.
> I'm going to test
> it at work in a couple of hours and report back.
Works fine @ work with cisco routers.
>
>
>> Thanks,
>>
>> Hannes
>>
>
>
>
> --
> This message is strictly personal and the opinions expressed do not
> represent those of my employers, either past or present.
--
This message is strictly personal and the opinions expressed do not
represent those of my employers, either past or present.
next prev parent reply other threads:[~2013-08-22 5:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130813221321.AEA1AB1E003@rfc-editor.org>
2013-08-14 8:19 ` Fwd: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery Fernando Gont
2013-08-14 23:06 ` Hannes Frederic Sowa
2013-08-15 6:28 ` Fernando Gont
2013-08-15 10:04 ` Hannes Frederic Sowa
2013-08-15 10:14 ` Loganaden Velvindron
2013-08-15 10:25 ` Hannes Frederic Sowa
2013-08-18 20:52 ` Loganaden Velvindron
2013-08-22 5:39 ` Loganaden Velvindron [this message]
2013-08-31 5:22 ` Fernando Gont
[not found] ` <CAOp4FwSatwRtx_O4Aio4e0HmahxdwiY9JToc8E+1rMT9oCjLrA@mail.gmail.com>
2013-08-31 5:20 ` Fernando Gont
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=CAOp4FwTcJX4dy23oZv6bU-+Fe-ZmwXp0WGonXVC_xvqPhpmxFQ@mail.gmail.com \
--to=loganaden@gmail.com \
--cc=fernando@gont.com.ar \
--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).