From: Phil Sutter <phil@nwl.cc>
To: "Serguei Bezverkhi (sbezverk)" <sbezverk@cisco.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>
Subject: Re: Operation not supported when adding jump command
Date: Tue, 26 Nov 2019 16:51:25 +0100 [thread overview]
Message-ID: <20191126155125.GD8016@orbyte.nwl.cc> (raw)
In-Reply-To: <427E92A6-2FFA-47CF-BF3B-C08961C978C9@cisco.com>
Hi Serguei,
On Tue, Nov 26, 2019 at 03:47:49PM +0000, Serguei Bezverkhi (sbezverk) wrote:
> I totally get it that it is not possible in theory, but the matter of fact is in kubernetes somehow it works, maybe in some cases this check is not enforced, I do not know. If you are interested to investigate it further, please let me know as I said I have a cluster with these 2 rules configured.
In another case I noticed that user-defined chains are a way to
circumvent these types of functional restrictions. If that's good or bad
is up to you to decide. ;)
Regarding the desired functionality, I guess you're wandering the
sinkhole-filled plains of undefined behaviour.
Cheers, Phil
next prev parent reply other threads:[~2019-11-26 15:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 18:55 Operation not supported when adding jump command Serguei Bezverkhi (sbezverk)
2019-11-26 12:21 ` Florian Westphal
2019-11-26 14:30 ` Serguei Bezverkhi (sbezverk)
2019-11-26 14:52 ` Florian Westphal
2019-11-26 15:38 ` Pablo Neira Ayuso
2019-11-26 15:47 ` Serguei Bezverkhi (sbezverk)
2019-11-26 15:51 ` Phil Sutter [this message]
2019-11-26 18:47 ` Serguei Bezverkhi (sbezverk)
2019-11-26 19:27 ` Phil Sutter
2019-11-26 21:20 ` Serguei Bezverkhi (sbezverk)
2019-11-26 22:15 ` Phil Sutter
2019-11-27 10:11 ` Arturo Borrero Gonzalez
2019-11-27 11:57 ` Phil Sutter
2019-11-27 14:36 ` Serguei Bezverkhi (sbezverk)
2019-11-27 15:08 ` Phil Sutter
2019-11-27 15:35 ` Serguei Bezverkhi (sbezverk)
2019-11-27 16:06 ` Phil Sutter
2019-11-27 16:50 ` Serguei Bezverkhi (sbezverk)
2019-11-27 17:22 ` Phil Sutter
2019-11-28 1:22 ` Serguei Bezverkhi (sbezverk)
2019-11-28 9:10 ` Laura Garcia
2019-11-28 11:58 ` Serguei Bezverkhi (sbezverk)
2019-11-28 13:08 ` Phil Sutter
2019-11-28 13:34 ` Serguei Bezverkhi (sbezverk)
2019-11-28 14:51 ` Serguei Bezverkhi (sbezverk)
2019-11-28 15:15 ` Phil Sutter
2019-11-29 20:13 ` Serguei Bezverkhi (sbezverk)
2019-11-30 0:04 ` Phil Sutter
2019-12-03 18:43 ` Serguei Bezverkhi (sbezverk)
2019-12-04 10:36 ` Phil Sutter
2019-12-03 23:50 ` Duncan Roe
2019-12-04 1:13 ` [PATCH nft] doc: Clarify conditions under which a reject verdict is permissible Duncan Roe
2019-12-06 2:37 ` [PATCH nft v2] " Duncan Roe
2019-12-06 6:55 ` Florian Westphal
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=20191126155125.GD8016@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=sbezverk@cisco.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