From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, Fabio <pedretti.fabio@gmail.com>
Subject: Re: [nf-next PATCH v2 2/2] netfilter: xt_recent: Lift restrictions on max hitcount value
Date: Fri, 14 Jun 2024 17:24:32 +0200 [thread overview]
Message-ID: <ZmxgsGWJ3IUizwVb@calendula> (raw)
In-Reply-To: <20240614151641.28885-3-phil@nwl.cc>
On Fri, Jun 14, 2024 at 05:16:41PM +0200, Phil Sutter wrote:
> Support tracking of up to 65535 packets per table entry instead of just
> 255 to better facilitate longer term tracking or higher throughput
> scenarios.
Could you develop a bit more the use case to expand this? Do you have
an example rule for me?
> Requested-by: Fabio <pedretti.fabio@gmail.com>
> Link: https://bugzilla.netfilter.org/show_bug.cgi?id=1745
Hm, original bug report only refer to documentation update?
Is there a way to know what kernel support what value? I guess not,
only probing.
Thanks.
> Signed-off-by: Phil Sutter <phil@nwl.cc>
> ---
> net/netfilter/xt_recent.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/net/netfilter/xt_recent.c b/net/netfilter/xt_recent.c
> index 60259280b2d5..588a5e6ad899 100644
> --- a/net/netfilter/xt_recent.c
> +++ b/net/netfilter/xt_recent.c
> @@ -59,9 +59,9 @@ MODULE_PARM_DESC(ip_list_gid, "default owning group of /proc/net/xt_recent/* fil
> /* retained for backwards compatibility */
> static unsigned int ip_pkt_list_tot __read_mostly;
> module_param(ip_pkt_list_tot, uint, 0400);
> -MODULE_PARM_DESC(ip_pkt_list_tot, "number of packets per IP address to remember (max. 255)");
> +MODULE_PARM_DESC(ip_pkt_list_tot, "number of packets per IP address to remember (max. 65535)");
>
> -#define XT_RECENT_MAX_NSTAMPS 256
> +#define XT_RECENT_MAX_NSTAMPS 65536
>
> struct recent_entry {
> struct list_head list;
> @@ -69,8 +69,8 @@ struct recent_entry {
> union nf_inet_addr addr;
> u_int16_t family;
> u_int8_t ttl;
> - u_int8_t index;
> - u_int8_t nstamps;
> + u_int16_t index;
> + u_int16_t nstamps;
> unsigned long stamps[];
> };
>
> @@ -80,7 +80,7 @@ struct recent_table {
> union nf_inet_addr mask;
> unsigned int refcnt;
> unsigned int entries;
> - u8 nstamps_max_mask;
> + u_int16_t nstamps_max_mask;
> struct list_head lru_list;
> struct list_head iphash[];
> };
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-06-14 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 15:16 [nf-next PATCH v2 0/2] netfilter: xt_recent: Allow for larger hitcount values Phil Sutter
2024-06-14 15:16 ` [nf-next PATCH v2 1/2] netfilter: xt_recent: Reduce size of struct recent_entry::nstamps Phil Sutter
2024-06-26 16:12 ` Pablo Neira Ayuso
2024-06-26 22:40 ` Phil Sutter
2024-06-26 23:39 ` Pablo Neira Ayuso
2024-06-27 0:06 ` Phil Sutter
2024-06-14 15:16 ` [nf-next PATCH v2 2/2] netfilter: xt_recent: Lift restrictions on max hitcount value Phil Sutter
2024-06-14 15:24 ` Pablo Neira Ayuso [this message]
2024-06-14 15:58 ` Fabio Pedretti
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=ZmxgsGWJ3IUizwVb@calendula \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pedretti.fabio@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox