All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: wh_bin@126.com
Cc: kadlec@netfilter.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netfilter: conntrack do not print ah and esp as unknown via /proc
Date: Fri, 21 Feb 2025 11:53:17 +0100	[thread overview]
Message-ID: <Z7hbHd0yK5I3ks9-@calendula> (raw)
In-Reply-To: <20250221102153.4625-1-wh_bin@126.com>

On Fri, Feb 21, 2025 at 10:21:53AM +0000, wh_bin@126.com wrote:
> From: hongbin wang <wh_bin@126.com>
> 
> /proc/net/nf_conntrack shows ah and esp as unknown.

there are no AH and ESP trackers in conntrack this far, that is why
they are shown as unknown.

> Signed-off-by: hongbin wang <wh_bin@126.com>
> ---
>  net/netfilter/nf_conntrack_standalone.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/net/netfilter/nf_conntrack_standalone.c b/net/netfilter/nf_conntrack_standalone.c
> index 502cf10aab41..29fb5a07a6c2 100644
> --- a/net/netfilter/nf_conntrack_standalone.c
> +++ b/net/netfilter/nf_conntrack_standalone.c
> @@ -266,6 +266,8 @@ static const char* l4proto_name(u16 proto)
>  	case IPPROTO_SCTP: return "sctp";
>  	case IPPROTO_UDPLITE: return "udplite";
>  	case IPPROTO_ICMPV6: return "icmpv6";
> +	case IPPROTO_ESP: return "esp";
> +	case IPPROTO_AH: return "ah";
>  	}
>  
>  	return "unknown";
> -- 
> 2.34.1
> 

      reply	other threads:[~2025-02-21 10:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 10:21 [PATCH] netfilter: conntrack do not print ah and esp as unknown via /proc wh_bin
2025-02-21 10:53 ` Pablo Neira Ayuso [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=Z7hbHd0yK5I3ks9-@calendula \
    --to=pablo@netfilter.org \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kadlec@netfilter.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wh_bin@126.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 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.