From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: martin@strongswan.org, netdev@vger.kernel.org
Subject: Re: [PATCH] xfrm: Accept ESP packets regardless of UDP encapsulation mode
Date: Thu, 18 Dec 2008 19:23:13 -0800 (PST) [thread overview]
Message-ID: <20081218.192313.250049404.davem@davemloft.net> (raw)
In-Reply-To: <20081218205406.GA451@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Fri, 19 Dec 2008 07:54:06 +1100
> On Thu, Dec 18, 2008 at 01:36:56PM +0100, Martin Willi wrote:
> >
> > >From the key manager perspective, I can enable or disable UDP
> > encapsulation, fine. I decide locally what I'll use for outgoing
> > packets. But how should I know what the peer uses? I can't, it isn't
> > negotiated. It is, by the standard, perfectly valid to send UDP
> > encapsulated packets if the peer wants to do so. And there is no need to
> > communicate this to the key manager, there is actually no such mechanism
> > in IKEv2. Therefore I need the kernel to accept packet, encapsulated or
> > not.
>
> Even if the kernel did accept such packets, there is no guarantee
> that your return traffic will make it back to the other side because
> stateful firewalls may be present.
>
> Responding with unencapsulated ESP traffic when the peer is sending
> you UDP-encapsulated traffic is just not going to fly.
>
> BTW I think the IKEv2 draft has stuffed it up on this one (though
> luckily it hasn't made it to RFC yet). I'll open a report on it.
I'm going to revert the change from net-next-2.6 from now
becasue:
1) The general scheme's validity is still suspect and under
discussion
2) The change has a known bug (the UDP header access issue)
3) Martin can apply the change locally to do testing until we
work this stuff out.
Thanks guys.
next prev parent reply other threads:[~2008-12-19 3:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 13:18 [PATCH] xfrm: Accept ESP packets regardless of UDP encapsulation mode Martin Willi
2008-12-04 23:40 ` David Miller
2008-12-18 3:47 ` Herbert Xu
2008-12-18 3:49 ` David Miller
2008-12-18 3:57 ` Herbert Xu
2008-12-18 4:14 ` Herbert Xu
2008-12-18 4:17 ` David Miller
2008-12-18 4:21 ` Herbert Xu
2008-12-18 10:35 ` Martin Willi
2008-12-18 11:04 ` Herbert Xu
2008-12-18 12:36 ` Martin Willi
2008-12-18 20:54 ` Herbert Xu
2008-12-19 3:23 ` David Miller [this message]
2008-12-19 10:00 ` Martin Willi
2008-12-19 10:19 ` Herbert Xu
2008-12-18 22:38 ` Herbert Xu
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=20081218.192313.250049404.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=martin@strongswan.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.