All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Peter Bieringer <pb@bieringer.de>
Cc: Maillist netdev <netdev@oss.sgi.com>,
	Netfilter development mailing list
	<netfilter-devel@lists.netfilter.org>,
	USAGI core <usagi-core@linux-ipv6.org>,
	Harald Welte <laforge@gnumonks.org>
Subject: Re: ip6tables: accept of IPv6 transport esp packages not possible - no rule matches
Date: Sun, 02 Jan 2005 22:14:56 +0100	[thread overview]
Message-ID: <41D86450.1070904@trash.net> (raw)
In-Reply-To: <E7944B8AE7C7468F39D3C2F8@worker.muc.bieringer.de>

Peter Bieringer wrote:

>>>BTW: how to filter incoming traffic after decryption?
>>>
>>Use tunnel-mode. The decrypted packets will hit PRE_ROUTING
>>and LOCAL_IN again.
>>
>
>Ok, confirmed working in tunnel mode, ping6 packet was counted twice in
>different rules (esp and icmpv6)
>
>But for outgoing ping6 packets, this won't work, packet is only counted
>(and accepted) by the icmpv6 rule, esp rule got no match, also not the
>"all" rule.
>
>Looks like at the moment, outgoing packet is passing netfilter only one
>time, even if encryption is in tunnel mode.
>
That is correct.

>
>By design / bug / missing feature?
>
By design and missing feature :) As I said, patches to fix this for
IPv4 will be submitted this week .. IPv6 will hopefully follow soon.

Regards
Patrick

      reply	other threads:[~2005-01-02 21:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-24  9:45 ip6tables: accept of IPv6 transport esp packages not possible - no rule matches Peter Bieringer
2004-12-24 15:59 ` Peter Bieringer
2004-12-25 15:46   ` Patrick McHardy
2005-01-02  9:01     ` Peter Bieringer
2005-01-02 11:42       ` Patrick McHardy
2005-01-02 12:15         ` Peter Bieringer
2005-01-02 21:14           ` Patrick McHardy [this message]

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=41D86450.1070904@trash.net \
    --to=kaber@trash.net \
    --cc=laforge@gnumonks.org \
    --cc=netdev@oss.sgi.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pb@bieringer.de \
    --cc=usagi-core@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 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.