[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <p4866orr-o8nn-6550-89o7-s3s12s27732q@vanv.qr>
Date: Tue, 23 Sep 2025 01:21:20 +0200 (CEST)
From: Jan Engelhardt <ej@...i.de>
To: Ricardo Robaina <rrobaina@...hat.com>
cc: audit@...r.kernel.org, linux-kernel@...r.kernel.org,
netfilter-devel@...r.kernel.org, coreteam@...filter.org,
paul@...l-moore.com, eparis@...hat.com, pablo@...filter.org,
kadlec@...filter.org, fw@...len.de
Subject: Re: [PATCH v1] audit: include source and destination ports to
NETFILTER_PKT
On Monday 2025-09-22 22:09, Ricardo Robaina wrote:
>NETFILTER_PKT records show both source and destination
>addresses, in addition to the associated networking protocol.
>However, it lacks the ports information, which is often
>valuable for troubleshooting.
>
>+ switch (ih->protocol) {
>+ case IPPROTO_TCP:
>+ sport = tcp_hdr(skb)->source;
>+ dport = tcp_hdr(skb)->dest;
>+ break;
>+ case IPPROTO_UDP:
>+ sport = udp_hdr(skb)->source;
>+ dport = udp_hdr(skb)->dest;
>+ }
Should be easy enough to add the cases for UDPLITE,
SCTP and DCCP, right?
Powered by blists - more mailing lists