From: Karuna Grewal <karunagrewal98@gmail.com>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nftables] tests/py: Add Test for `meta time`
Date: Tue, 19 Mar 2019 12:34:15 +0530 [thread overview]
Message-ID: <CAHRz_yY=yrrMJS98s6cq9sRP_nrSNrv5kKCPxKT+BAj_GGS5hw@mail.gmail.com> (raw)
In-Reply-To: <20190318220923.5v64yccan6shhpnq@breakpoint.cc>
On Tue, Mar 19, 2019 at 3:39 AM Florian Westphal <fw@strlen.de> wrote:
>
> Karuna Grewal <karunagrewal98@gmail.com> wrote:
> > command: add rule ip test-ip4 input meta time 100
> > Error: Could not process rule: Operation not supported
>
> This means that nft_meta.c doesn't recognize the TIME key.
> You need to run the modified/patched kernel for this to work --
> it looks like nft_meta_get_init() hits the "default:" switch label.
I'm running the tests against the new modified kernel (I've applied
the patch to kernel 5.0.2) and when I logged a debug message it
confirms that it's indeed hitting the default switch.
But previously running nft against the nf-next fork of the kernel was
recognising the `meta time`. This leaves me in a bit of confusion.
Meanwhile I'm trying to verify other things, could you please confirm
if the kernel tree isn't any issue here.
next prev parent reply other threads:[~2019-03-19 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 9:47 [nftables] tests/py: Add Test for `meta time` Karuna Grewal
[not found] ` <CAHRz_yZMsP2RQPu=8pTigq8SrYz9xYSef3S_d4ORAMkkYDEv4Q@mail.gmail.com>
[not found] ` <20190318105545.qz5oddbjah4qc4fa@breakpoint.cc>
[not found] ` <CAHRz_yYk_Yq5+Tp1J1jT2rVT0pHWjH37-F8Rdi1XCLWj79J6rg@mail.gmail.com>
[not found] ` <20190318220923.5v64yccan6shhpnq@breakpoint.cc>
2019-03-19 7:04 ` Karuna Grewal [this message]
2019-03-19 7:17 ` Florian Westphal
2019-03-19 7:27 ` Karuna Grewal
2019-03-19 7:50 ` Florian Westphal
2019-04-08 22:35 ` 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='CAHRz_yY=yrrMJS98s6cq9sRP_nrSNrv5kKCPxKT+BAj_GGS5hw@mail.gmail.com' \
--to=karunagrewal98@gmail.com \
--cc=fw@strlen.de \
--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).