From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Tom Yan <tom.ty89@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [Bug] Reverse translation skips "leading" meta protocol match
Date: Thu, 26 Aug 2021 12:51:00 +0200 [thread overview]
Message-ID: <20210826105100.GA4859@salvia> (raw)
In-Reply-To: <CAGnHSEmo1D2bCemVuCT-D2jdM8AmUgGKxZrq0RpXUMaLyQqjwA@mail.gmail.com>
On Thu, Aug 26, 2021 at 12:10:05PM +0800, Tom Yan wrote:
[...]
> bridge meh hmm 3 2
> [ meta load protocol => reg 1 ]
> [ cmp eq reg 1 0x00000008 ]
> [ meta load l4proto => reg 1 ]
> [ cmp eq reg 1 0x00000011 ]
> [ payload load 2b @ transport header + 2 => reg 1 ]
> [ cmp eq reg 1 0x00004300 ]
> [ immediate reg 0 accept ]
https://patchwork.ozlabs.org/project/netfilter-devel/patch/20210826104952.4812-1-pablo@netfilter.org/
prev parent reply other threads:[~2021-08-26 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 4:10 [Bug] Reverse translation skips "leading" meta protocol match Tom Yan
2021-08-26 4:13 ` Tom Yan
2021-08-26 10:51 ` Pablo Neira Ayuso [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=20210826105100.GA4859@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=tom.ty89@gmail.com \
/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).