From: Patrick McHardy <kaber@trash.net>
To: Thomas Jacob <jacob@internet24.de>
Cc: netfilter@vger.kernel.org
Subject: Re: Warning: never matched protocol: ah. use extension match instead.
Date: Mon, 23 Jun 2008 16:07:45 +0200 [thread overview]
Message-ID: <485FAE31.4050203@trash.net> (raw)
In-Reply-To: <1214229359.9717.34.camel@enterprise.ims-firmen.de>
Thomas Jacob wrote:
> Could someone clarify what exactly the warning message in the subject
> (from ip6tables) is supposed to tell me?
>
> It looks like that ip6tables -p ah (or -p in general) would match
> packets that contain an ah header as the last extension header whereas
> -m ah matches packets that contain an ah header at any position, but
> I'm not sure.
Almost. "-p" uses the first non-extension header (which can never
be AH), while "-m ah" matches on AH extension headers.
> The core of the question is this: how does one pass unspecified
> ipsec traffic in ip6tables (the way you could do with -p ah + -p esp in
> iptables)?
"-m ah" and both "-m esp" and "-p esp" should work.
next prev parent reply other threads:[~2008-06-23 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 13:55 Warning: never matched protocol: ah. use extension match instead Thomas Jacob
2008-06-23 14:07 ` Patrick McHardy [this message]
2008-06-23 15:14 ` Jan Engelhardt
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=485FAE31.4050203@trash.net \
--to=kaber@trash.net \
--cc=jacob@internet24.de \
--cc=netfilter@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