From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] [IPSEC]: Reinject v6 packet on input instead of calling netfilter
Date: Thu, 29 Nov 2007 22:21:05 +0100 [thread overview]
Message-ID: <474F2D41.60707@trash.net> (raw)
In-Reply-To: <1196370761.4437.28.camel@localhost>
jamal wrote:
> On Thu, 2007-29-11 at 21:55 +0100, Patrick McHardy wrote:
>
>> jamal wrote:
>>
>> [ can't quote because non-inline attachment ]
>>
>
> Evolution seems to have whitespace issues everytime i inlined the
> attachment; and Dave has been able to tolerate me doing this so far.
> I have just read it in
>
I used to work fine for me as well, the Debian switch to icedove
broke it. Never mind, I'm sure its going to get fixed some day :)
>
>> I think Yoshifuji had some objections to this because extension
>> headers will be processed twice.
>>
>
> ah, i missed that part. Could you point to a specific portion?
>
http://lists.openwall.net/netdev/2007/10/16/88
> I wouldnt mind just ipv4 going in - but that would be lacking
> consistency. Is there anything that can be done to get the extension
> headers to be processed only once?
>
I would prefer to keep things consistent between IPv4 and IPv6. Not
sure if anything could be done, perhaps we could keep the necessary
parts of the IP6CB and skip parsing up to the ESP nexthdr.
next prev parent reply other threads:[~2007-11-29 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 20:52 [PATCH 2/2] [IPSEC]: Reinject v6 packet on input instead of calling netfilter jamal
2007-11-29 20:55 ` Patrick McHardy
2007-11-29 21:12 ` jamal
2007-11-29 21:21 ` Patrick McHardy [this message]
2007-11-29 22:05 ` jamal
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=474F2D41.60707@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=herbert@gondor.apana.org.au \
--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).