From: "Anders K. Pedersen | Cohaesio" <akp@cohaesio.com>
To: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: nftables rules not matching after upgrading from 0.7 to 0.8
Date: Wed, 25 Oct 2017 16:31:55 +0000 [thread overview]
Message-ID: <1508949114.1154.14.camel@cohaesio.com> (raw)
Hello,
After upgrading to nftables 0.8 (from 0.7) on one of my systems, I've
experiences several cases where rules that used to work fine with 0.7
sometimes doesn't match anymore with 0.8 (it's not consistent -
sometimes the rules do match with 0.8).
The rule chains end with a log statement before rejecting or dropping
the packets, and I can see in the log that everything is as expected
and the rules should match. After downgrading to nftables 0.7
everything works again.
I tried loading my rule set with "--debug=netlink" and diff the output
from 0.7 vs. 0.8. Apart from syntax differences the only thing that
changed is
ip filter input
- [ payload load 1b @ network header + 9 => reg 1 ]
+ [ meta load l4proto => reg 1 ]
and
ip6 filter input
- [ payload load 1b @ network header + 6 => reg 1 ]
+ [ meta load l4proto => reg 1 ]
for many of the rules. I believe this is intentional and correct by
itself, so I guess the problem is in the kernel (the system is
currently running 4.13.8), where "meta l4proto" sometimes isn't what it
should be.
Does this sound right and does it ring any bells?
Regards,
Anders K. Pedersen
next reply other threads:[~2017-10-25 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 16:31 Anders K. Pedersen | Cohaesio [this message]
2017-10-25 17:57 ` nftables rules not matching after upgrading from 0.7 to 0.8 Florian Westphal
2017-10-25 18:20 ` Anders K. Pedersen | Cohaesio
2017-10-25 22:22 ` Anders K. Pedersen | Cohaesio
2017-10-25 22:45 ` Florian Westphal
2017-10-25 23:44 ` Pablo Neira Ayuso
2017-10-26 7:00 ` Anders K. Pedersen | Cohaesio
2017-10-25 23:47 ` Pablo Neira Ayuso
2017-10-26 6:47 ` Anders K. Pedersen | Cohaesio
2017-11-06 16:49 ` Anders K. Pedersen | Cohaesio
2017-11-07 0:58 ` Pablo Neira Ayuso
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=1508949114.1154.14.camel@cohaesio.com \
--to=akp@cohaesio.com \
--cc=netfilter-devel@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).