From: Jeremy Sowden <jeremy@azazel.net>
To: Kyle Bowman <kbowman@cloudflare.com>
Cc: Phil Sutter <phil@nwl.cc>, Alex Forster <aforster@cloudflare.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
kernel-team <kernel-team@cloudflare.com>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
coreteam@netfilter.org, netfilter-devel@vger.kernel.org
Subject: Re: [netfilter-core] [PATCH] netfilter: xt_NFLOG: allow 128 character log prefixes
Date: Thu, 5 Aug 2021 22:07:37 +0100 [thread overview]
Message-ID: <YQxTGZ1h3X8gem75@azazel.net> (raw)
In-Reply-To: <YQvAsgl/ylNAZVVP@azazel.net>
[-- Attachment #1.1: Type: text/plain, Size: 2508 bytes --]
On 2021-08-05, at 11:42:58 +0100, Jeremy Sowden wrote:
> On 2021-08-03, at 13:36:04 -0500, Kyle Bowman wrote:
> > On Tue, Aug 03, 2021 at 10:06:41AM +0100, Jeremy Sowden wrote:
> > > Right, take three. Firstly, use udata as I previously suggested,
> > > and then use a new struct with a layout compatible with struct
> > > xt_nflog_info just for printing and saving iptables-nft targets.
> > >
> > > Seems to work. Doesn't break iptables-legacy.
> > >
> > > Patches attached.
> >
> > Thanks for writing in and helping with this, I appreciate it. I
> > actually was trying to make this work last night in a similar way to
> > how you've solved it but I gave up after a few hours. I'll go ahead
> > and organize this together and send the patches in a separate
> > thread.
>
> One thing before you do. Some of iptables' unit-tests related to
> NFLOG are now failing. For example:
>
> $ sudo python3 ./iptables-test.py -n extensions/libxt_NFLOG.t
> Cannot run in own namespace, connectivity might break
> extensions/libxt_NFLOG.t: ERROR: line 2 (cannot find: iptables -I INPUT -j NFLOG --nflog-group 1)
> extensions/libxt_NFLOG.t: ERROR: line 3 (cannot find: iptables -I INPUT -j NFLOG --nflog-group 65535)
> extensions/libxt_NFLOG.t: ERROR: line 6 (cannot find: iptables -I INPUT -j NFLOG --nflog-range 1)
> extensions/libxt_NFLOG.t: ERROR: line 7 (cannot find: iptables -I INPUT -j NFLOG --nflog-range 4294967295)
> extensions/libxt_NFLOG.t: ERROR: line 10 (cannot find: iptables -I INPUT -j NFLOG --nflog-size 0)
> extensions/libxt_NFLOG.t: ERROR: line 11 (cannot find: iptables -I INPUT -j NFLOG --nflog-size 1)
> extensions/libxt_NFLOG.t: ERROR: line 12 (cannot find: iptables -I INPUT -j NFLOG --nflog-size 4294967295)
> extensions/libxt_NFLOG.t: ERROR: line 19 (cannot find: iptables -I INPUT -j NFLOG --nflog-threshold 1)
> extensions/libxt_NFLOG.t: ERROR: line 22 (cannot find: iptables -I INPUT -j NFLOG --nflog-threshold 65535)
> 1 test files, 17 unit tests, 8 passed
>
> I'm working my way through them. I've got fixes for most. I'll send
> patches when I've sorted out the remaining ones.
Patches attached. The first is the same as before. The second is
slightly different: I've moved around the initialization of the info
struct, but there are no functional differences. Of the remaining
patches, 3-8 fix bugs that were flagged up by the failing unit-tests, 9
adds a comment explaining that we don't support `--nflog-range`, and 10
drops unit-tests for this.
J.
[-- Attachment #1.2: v4-0001-extensions-libxt_NFLOG-use-udata-to-store-longer-.patch --]
[-- Type: text/x-diff, Size: 2455 bytes --]
From a50a604d2dfdb8951433a7c5adce02c589a07dae Mon Sep 17 00:00:00 2001
From: Jeremy Sowden <jeremy@azazel.net>
Date: Sun, 1 Aug 2021 14:47:52 +0100
Subject: [PATCH v4 01/10] extensions: libxt_NFLOG: use udata to store longer
prefixes suitable for the nft log statement.
Hitherto NFLOG has truncated the log-prefix to the 64-character limit
supported by iptables-legacy. We now use the struct xtables_target's
udata member to store the longer 128-character prefix supported by
iptables-nft.
Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
---
extensions/libxt_NFLOG.c | 6 ++++++
iptables/nft.c | 6 +-----
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/extensions/libxt_NFLOG.c b/extensions/libxt_NFLOG.c
index 02a1b4aa35a3..9057230d7ee7 100644
--- a/extensions/libxt_NFLOG.c
+++ b/extensions/libxt_NFLOG.c
@@ -5,6 +5,7 @@
#include <getopt.h>
#include <xtables.h>
+#include <linux/netfilter/nf_log.h>
#include <linux/netfilter/x_tables.h>
#include <linux/netfilter/xt_NFLOG.h>
@@ -53,12 +54,16 @@ static void NFLOG_init(struct xt_entry_target *t)
static void NFLOG_parse(struct xt_option_call *cb)
{
+ char *nf_log_prefix = cb->udata;
+
xtables_option_parse(cb);
switch (cb->entry->id) {
case O_PREFIX:
if (strchr(cb->arg, '\n') != NULL)
xtables_error(PARAMETER_PROBLEM,
"Newlines not allowed in --log-prefix");
+
+ snprintf(nf_log_prefix, NF_LOG_PREFIXLEN, "%s", cb->arg);
break;
}
}
@@ -149,6 +154,7 @@ static struct xtables_target nflog_target = {
.save = NFLOG_save,
.x6_options = NFLOG_opts,
.xlate = NFLOG_xlate,
+ .udata_size = NF_LOG_PREFIXLEN
};
void _init(void)
diff --git a/iptables/nft.c b/iptables/nft.c
index dce8fe0b4a18..13cbf0a8b87b 100644
--- a/iptables/nft.c
+++ b/iptables/nft.c
@@ -1365,11 +1365,7 @@ int add_log(struct nftnl_rule *r, struct iptables_command_state *cs)
return -ENOMEM;
if (info->prefix != NULL) {
- //char prefix[NF_LOG_PREFIXLEN] = {};
-
- // get prefix here from somewhere...
- // maybe in cs->argv?
- nftnl_expr_set_str(expr, NFTNL_EXPR_LOG_PREFIX, "iff the value at the end is 12 then this string is truncated 123");
+ nftnl_expr_set_str(expr, NFTNL_EXPR_LOG_PREFIX, cs->target->udata);
}
if (info->group) {
nftnl_expr_set_u16(expr, NFTNL_EXPR_LOG_GROUP, info->group);
--
2.30.2
[-- Attachment #1.3: v4-0002-extensions-libxt_NFLOG-don-t-truncate-log-prefix-.patch --]
[-- Type: text/x-diff, Size: 3683 bytes --]
From 05f656f9ac89cb348f82d522a5fc1c19e367504a Mon Sep 17 00:00:00 2001
From: Jeremy Sowden <jeremy@azazel.net>
Date: Mon, 2 Aug 2021 22:54:27 +0100
Subject: [PATCH v4 02/10] extensions: libxt_NFLOG: don't truncate log-prefix
when printing and saving iptables-nft nflog targets.
When parsing the rule, use a struct with a layout compatible to that of
struct xt_nflog_info, but with a buffer large enough to contain the
whole 128-character nft prefix.
Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
---
iptables/nft-shared.c | 45 +++++++++++++++++++++++--------------------
1 file changed, 24 insertions(+), 21 deletions(-)
diff --git a/iptables/nft-shared.c b/iptables/nft-shared.c
index b5259db07723..22a1a08ed862 100644
--- a/iptables/nft-shared.c
+++ b/iptables/nft-shared.c
@@ -20,6 +20,7 @@
#include <xtables.h>
+#include <linux/netfilter/nf_log.h>
#include <linux/netfilter/xt_comment.h>
#include <linux/netfilter/xt_limit.h>
#include <linux/netfilter/xt_NFLOG.h>
@@ -598,21 +599,35 @@ static void nft_parse_limit(struct nft_xt_ctx *ctx, struct nftnl_expr *e)
static void nft_parse_log(struct nft_xt_ctx *ctx, struct nftnl_expr *e)
{
- __u16 group = nftnl_expr_get_u16(e, NFTNL_EXPR_LOG_GROUP);
- __u16 qthreshold = nftnl_expr_get_u16(e, NFTNL_EXPR_LOG_QTHRESHOLD);
- __u32 snaplen = nftnl_expr_get_u32(e, NFTNL_EXPR_LOG_SNAPLEN);
- const char *prefix = nftnl_expr_get_str(e, NFTNL_EXPR_LOG_PREFIX);
struct xtables_target *target;
struct xt_entry_target *t;
size_t target_size;
-
- void *data = ctx->cs;
+ /*
+ * In order to handle the longer log-prefix supported by nft, instead of
+ * using struct xt_nflog_info, we use a struct with a compatible layout, but
+ * a larger buffer for the prefix.
+ */
+ struct xt_nflog_info_nft {
+ __u32 len;
+ __u16 group;
+ __u16 threshold;
+ __u16 flags;
+ __u16 pad;
+ char prefix[NF_LOG_PREFIXLEN];
+ } info = {
+ .group = nftnl_expr_get_u16(e, NFTNL_EXPR_LOG_GROUP),
+ .threshold = nftnl_expr_get_u16(e, NFTNL_EXPR_LOG_QTHRESHOLD),
+ .len = nftnl_expr_get_u32(e, NFTNL_EXPR_LOG_SNAPLEN),
+ };
+ snprintf(info.prefix, sizeof(info.prefix), "%s",
+ nftnl_expr_get_str(e, NFTNL_EXPR_LOG_PREFIX));
target = xtables_find_target("NFLOG", XTF_TRY_LOAD);
if (target == NULL)
return;
- target_size = XT_ALIGN(sizeof(struct xt_entry_target)) + target->size;
+ target_size = XT_ALIGN(sizeof(struct xt_entry_target)) +
+ XT_ALIGN(sizeof(struct xt_nflog_info_nft));
t = xtables_calloc(1, target_size);
t->u.target_size = target_size;
@@ -621,21 +636,9 @@ static void nft_parse_log(struct nft_xt_ctx *ctx, struct nftnl_expr *e)
target->t = t;
- struct xt_nflog_info *info = xtables_malloc(sizeof(struct xt_nflog_info));
- info->group = group;
- info->len = snaplen;
- info->threshold = qthreshold;
-
- /* Here, because we allow 128 characters in nftables but only 64
- * characters in xtables (in xt_nflog_info specifically), we may
- * end up truncating the string when parsing it.
- */
- strncpy(info->prefix, prefix, sizeof(info->prefix));
- info->prefix[sizeof(info->prefix) - 1] = '\0';
-
- memcpy(&target->t->data, info, target->size);
+ memcpy(&target->t->data, &info, sizeof(info));
- ctx->h->ops->parse_target(target, data);
+ ctx->h->ops->parse_target(target, ctx->cs);
}
static void nft_parse_lookup(struct nft_xt_ctx *ctx, struct nft_handle *h,
--
2.30.2
[-- Attachment #1.4: v4-0003-extensions-libxt_NFLOG-only-send-the-prefix-if-it.patch --]
[-- Type: text/x-diff, Size: 913 bytes --]
From c75e6f19307ffdecf1f99205f31c3aa61cde7350 Mon Sep 17 00:00:00 2001
From: Jeremy Sowden <jeremy@azazel.net>
Date: Thu, 5 Aug 2021 15:38:40 +0100
Subject: [PATCH v4 03/10] extensions: libxt_NFLOG: only send the prefix if it
is not empty.
`info->prefix` is an array, not a pointer, and so is never `NULL`.
Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
---
iptables/nft.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/iptables/nft.c b/iptables/nft.c
index 13cbf0a8b87b..e5e5b8e1046b 100644
--- a/iptables/nft.c
+++ b/iptables/nft.c
@@ -1364,7 +1364,7 @@ int add_log(struct nftnl_rule *r, struct iptables_command_state *cs)
if (!expr)
return -ENOMEM;
- if (info->prefix != NULL) {
+ if (info->prefix[0] != '\0') {
nftnl_expr_set_str(expr, NFTNL_EXPR_LOG_PREFIX, cs->target->udata);
}
if (info->group) {
--
2.30.2
[-- Attachment #1.5: v4-0004-extensions-libxt_NFLOG-check-that-the-prefix-is-s.patch --]
[-- Type: text/x-diff, Size: 1283 bytes --]
From cb11ef308b8624fff2f8611648daee2545902184 Mon Sep 17 00:00:00 2001
From: Jeremy Sowden <jeremy@azazel.net>
Date: Thu, 5 Aug 2021 16:01:07 +0100
Subject: [PATCH v4 04/10] extensions: libxt_NFLOG: check that the prefix is
set.
Since we don't send the prefix if it empty, we may not get one back from
the kernel.
Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
---
iptables/nft-shared.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/iptables/nft-shared.c b/iptables/nft-shared.c
index 22a1a08ed862..ecce64cd166f 100644
--- a/iptables/nft-shared.c
+++ b/iptables/nft-shared.c
@@ -619,8 +619,10 @@ static void nft_parse_log(struct nft_xt_ctx *ctx, struct nftnl_expr *e)
.threshold = nftnl_expr_get_u16(e, NFTNL_EXPR_LOG_QTHRESHOLD),
.len = nftnl_expr_get_u32(e, NFTNL_EXPR_LOG_SNAPLEN),
};
- snprintf(info.prefix, sizeof(info.prefix), "%s",
- nftnl_expr_get_str(e, NFTNL_EXPR_LOG_PREFIX));
+ if (nftnl_expr_is_set(e, NFTNL_EXPR_LOG_PREFIX)) {
+ snprintf(info.prefix, sizeof(info.prefix), "%s",
+ nftnl_expr_get_str(e, NFTNL_EXPR_LOG_PREFIX));
+ }
target = xtables_find_target("NFLOG", XTF_TRY_LOAD);
if (target == NULL)
--
2.30.2
[-- Attachment #1.6: v4-0005-extensions-libxt_NFLOG-always-send-the-nflog-grou.patch --]
[-- Type: text/x-diff, Size: 1598 bytes --]
From 0db1b2666240effef0b75b31cd07233146b36c45 Mon Sep 17 00:00:00 2001
From: Jeremy Sowden <jeremy@azazel.net>
Date: Thu, 5 Aug 2021 15:52:58 +0100
Subject: [PATCH v4 05/10] extensions: libxt_NFLOG: always send the
nflog-group.
For nft, log and nflog targets are handled by the same kernel module,
and are distinguished by whether they define a nflog-group. Therefore,
we must send the group even if it is zero, or the kernel will configure
the target as a log, not an nflog.
Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
---
iptables/nft.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/iptables/nft.c b/iptables/nft.c
index e5e5b8e1046b..4bfc85a7d0bc 100644
--- a/iptables/nft.c
+++ b/iptables/nft.c
@@ -1367,15 +1367,14 @@ int add_log(struct nftnl_rule *r, struct iptables_command_state *cs)
if (info->prefix[0] != '\0') {
nftnl_expr_set_str(expr, NFTNL_EXPR_LOG_PREFIX, cs->target->udata);
}
- if (info->group) {
- nftnl_expr_set_u16(expr, NFTNL_EXPR_LOG_GROUP, info->group);
- if (info->flags & XT_NFLOG_F_COPY_LEN)
+
+ nftnl_expr_set_u16(expr, NFTNL_EXPR_LOG_GROUP, info->group);
+ if (info->flags & XT_NFLOG_F_COPY_LEN)
nftnl_expr_set_u32(expr, NFTNL_EXPR_LOG_SNAPLEN,
info->len);
- if (info->threshold)
+ if (info->threshold)
nftnl_expr_set_u16(expr, NFTNL_EXPR_LOG_QTHRESHOLD,
info->threshold);
- }
nftnl_rule_add_expr(r, expr);
return 0;
--
2.30.2
[-- Attachment #1.7: v4-0006-extensions-libxt_NFLOG-only-targets-which-have-a-.patch --]
[-- Type: text/x-diff, Size: 1089 bytes --]
From d32fda241b2a60eda0709e62602f6b703d4c3347 Mon Sep 17 00:00:00 2001
From: Jeremy Sowden <jeremy@azazel.net>
Date: Thu, 5 Aug 2021 15:55:28 +0100
Subject: [PATCH v4 06/10] extensions: libxt_NFLOG: only targets which have a
nflog-group are compatible.
Since nflog targets are distinguished by having a nflog-group, we ignore
targets without one. Since nflog targets don't support levels or flags,
we can ignore these attributes.
Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
---
iptables/nft.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/iptables/nft.c b/iptables/nft.c
index 4bfc85a7d0bc..5778496e9ef2 100644
--- a/iptables/nft.c
+++ b/iptables/nft.c
@@ -3516,9 +3516,8 @@ static int nft_is_expr_compatible(struct nftnl_expr *expr, void *data)
return 0;
if (!strcmp(name, "log") &&
- nftnl_expr_get_u32(expr, NFTNL_EXPR_LOG_LEVEL) == 4 &&
- !nftnl_expr_is_set(expr, NFTNL_EXPR_LOG_FLAGS))
- return 0;
+ nftnl_expr_is_set(expr, NFTNL_EXPR_LOG_GROUP))
+ return 0;
return -1;
}
--
2.30.2
[-- Attachment #1.8: v4-0007-extensions-libxt_NFLOG-check-whether-the-snap-len.patch --]
[-- Type: text/x-diff, Size: 1305 bytes --]
From a9c88a338218a4eabc89b357d8d9f21939e20898 Mon Sep 17 00:00:00 2001
From: Jeremy Sowden <jeremy@azazel.net>
Date: Thu, 5 Aug 2021 16:04:25 +0100
Subject: [PATCH v4 07/10] extensions: libxt_NFLOG: check whether the
snap-length is set.
We don't always send the length to the kernel, so we need to check
whether we have received it.
Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
---
iptables/nft-shared.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/iptables/nft-shared.c b/iptables/nft-shared.c
index ecce64cd166f..8227c4308f84 100644
--- a/iptables/nft-shared.c
+++ b/iptables/nft-shared.c
@@ -617,8 +617,10 @@ static void nft_parse_log(struct nft_xt_ctx *ctx, struct nftnl_expr *e)
} info = {
.group = nftnl_expr_get_u16(e, NFTNL_EXPR_LOG_GROUP),
.threshold = nftnl_expr_get_u16(e, NFTNL_EXPR_LOG_QTHRESHOLD),
- .len = nftnl_expr_get_u32(e, NFTNL_EXPR_LOG_SNAPLEN),
};
+ if (nftnl_expr_is_set(e, NFTNL_EXPR_LOG_SNAPLEN)) {
+ info.len = nftnl_expr_get_u32(e, NFTNL_EXPR_LOG_SNAPLEN);
+ }
if (nftnl_expr_is_set(e, NFTNL_EXPR_LOG_PREFIX)) {
snprintf(info.prefix, sizeof(info.prefix), "%s",
nftnl_expr_get_str(e, NFTNL_EXPR_LOG_PREFIX));
--
2.30.2
[-- Attachment #1.9: v4-0008-extensions-libxt_NFLOG-set-copy-len-flag-if-the-s.patch --]
[-- Type: text/x-diff, Size: 1009 bytes --]
From e88fb277d5d406034c9099af1c25cceac02db1a7 Mon Sep 17 00:00:00 2001
From: Jeremy Sowden <jeremy@azazel.net>
Date: Thu, 5 Aug 2021 16:06:25 +0100
Subject: [PATCH v4 08/10] extensions: libxt_NFLOG: set copy-len flag if the
snap-length is set.
Without this, iptables mistakes `nflog-size` for `nflog-range`.
Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
---
iptables/nft-shared.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/iptables/nft-shared.c b/iptables/nft-shared.c
index 8227c4308f84..70d1e20f80f1 100644
--- a/iptables/nft-shared.c
+++ b/iptables/nft-shared.c
@@ -620,6 +620,7 @@ static void nft_parse_log(struct nft_xt_ctx *ctx, struct nftnl_expr *e)
};
if (nftnl_expr_is_set(e, NFTNL_EXPR_LOG_SNAPLEN)) {
info.len = nftnl_expr_get_u32(e, NFTNL_EXPR_LOG_SNAPLEN);
+ info.flags = XT_NFLOG_F_COPY_LEN;
}
if (nftnl_expr_is_set(e, NFTNL_EXPR_LOG_PREFIX)) {
snprintf(info.prefix, sizeof(info.prefix), "%s",
--
2.30.2
[-- Attachment #1.10: v4-0009-extensions-libxt_NFLOG-add-a-comment-to-the-code-.patch --]
[-- Type: text/x-diff, Size: 1722 bytes --]
From 0da888807aa82a6ab327bc252f447df1ded81ddc Mon Sep 17 00:00:00 2001
From: Jeremy Sowden <jeremy@azazel.net>
Date: Thu, 5 Aug 2021 21:15:58 +0100
Subject: [PATCH v4 09/10] extensions: libxt_NFLOG: add a comment to the code
explaining that we ignore `--nflog-range`.
Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
---
iptables/nft.c | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/iptables/nft.c b/iptables/nft.c
index 5778496e9ef2..3a3e70d5824f 100644
--- a/iptables/nft.c
+++ b/iptables/nft.c
@@ -1369,6 +1369,21 @@ int add_log(struct nftnl_rule *r, struct iptables_command_state *cs)
}
nftnl_expr_set_u16(expr, NFTNL_EXPR_LOG_GROUP, info->group);
+ /*
+ * In iptables-legacy, `--nflog-range` sets the length, and `--nflog-size`
+ * set the length _and_ the `XT_NFLOG_COPY_LEN` flag. For iptables-nft, we
+ * cannot set a flag: setting the length always implies (the equivalent
+ * of) `--nflog-size` (`snaplen` in nft parlance). This means we cannot
+ * emulate `--nflog-range`. However, `--nflog-range` is broken and doesn't
+ * do anything. If given `--nflog-range`, we have two choices: we can send
+ * the given length anyway, effectively converting it to `--nflog-size`, or
+ * we can ignore it. `--nflog-size` was added explicitly to avoid changing
+ * the broken behaviour of `--nflog-range`:
+ *
+ * https://lore.kernel.org/netfilter-devel/20160624204231.GA3062@akamai.com/
+ *
+ * so we ignore it.
+ */
if (info->flags & XT_NFLOG_F_COPY_LEN)
nftnl_expr_set_u32(expr, NFTNL_EXPR_LOG_SNAPLEN,
info->len);
--
2.30.2
[-- Attachment #1.11: v4-0010-extensions-libxf_NFLOG-remove-nflog-range-Python-.patch --]
[-- Type: text/x-diff, Size: 1163 bytes --]
From 311eaed59c399966bf352712be6a753296ebe568 Mon Sep 17 00:00:00 2001
From: Jeremy Sowden <jeremy@azazel.net>
Date: Thu, 5 Aug 2021 20:37:15 +0100
Subject: [PATCH v4 10/10] extensions: libxf_NFLOG: remove `--nflog-range`
Python unit-tests.
nft has no equivalent to `--nflog-range`, so we cannot emulate it and
the Python unit-tests for it fail. However, since `--nflog-range` is
broken and doesn't do anything, the tests are not testing anything
useful.
Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
---
extensions/libxt_NFLOG.t | 4 ----
1 file changed, 4 deletions(-)
diff --git a/extensions/libxt_NFLOG.t b/extensions/libxt_NFLOG.t
index 933fa22160e5..33a15c061ed7 100644
--- a/extensions/libxt_NFLOG.t
+++ b/extensions/libxt_NFLOG.t
@@ -3,10 +3,6 @@
-j NFLOG --nflog-group 65535;=;OK
-j NFLOG --nflog-group 65536;;FAIL
-j NFLOG --nflog-group 0;-j NFLOG;OK
--j NFLOG --nflog-range 1;=;OK
--j NFLOG --nflog-range 4294967295;=;OK
--j NFLOG --nflog-range 4294967296;;FAIL
--j NFLOG --nflog-range -1;;FAIL
-j NFLOG --nflog-size 0;=;OK
-j NFLOG --nflog-size 1;=;OK
-j NFLOG --nflog-size 4294967295;=;OK
--
2.30.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-08-05 21:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 19:00 [PATCH] netfilter: xt_NFLOG: allow 128 character log prefixes Kyle Bowman
2021-07-27 19:54 ` Pablo Neira Ayuso
2021-07-27 20:06 ` Alex Forster
2021-07-27 21:10 ` Pablo Neira Ayuso
2021-07-27 21:22 ` Alex Forster
2021-07-27 21:27 ` Pablo Neira Ayuso
2021-07-27 21:44 ` Alex Forster
2021-07-27 21:52 ` Pablo Neira Ayuso
2021-07-27 22:45 ` Alex Forster
2021-07-27 23:02 ` Pablo Neira Ayuso
2021-07-28 1:43 ` [netfilter-core] " Phil Sutter
2021-07-30 18:27 ` Kyle Bowman
2021-08-01 14:14 ` Jeremy Sowden
2021-08-02 11:20 ` Jeremy Sowden
2021-08-02 16:40 ` Jeremy Sowden
2021-08-03 9:06 ` Jeremy Sowden
2021-08-03 18:36 ` Kyle Bowman
2021-08-05 10:42 ` Jeremy Sowden
2021-08-05 21:07 ` Jeremy Sowden [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=YQxTGZ1h3X8gem75@azazel.net \
--to=jeremy@azazel.net \
--cc=aforster@cloudflare.com \
--cc=coreteam@netfilter.org \
--cc=kadlec@netfilter.org \
--cc=kbowman@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.