From: Florian Westphal <fw@strlen.de>
To: Slavko <linux@slavino.sk>
Cc: netfilter ML <netfilter@vger.kernel.org>
Subject: Re: Log ARP headers
Date: Mon, 3 Mar 2025 20:35:33 +0100 [thread overview]
Message-ID: <20250303193533.GA16225@breakpoint.cc> (raw)
In-Reply-To: <FADC1D05-BC58-45CF-AEBA-2D4B85928185@slavino.sk>
Slavko <linux@slavino.sk> wrote:
> i want to log ARP headers, thus i create arp family table
> with one chain with only one rule, somethong as:
>
> arp operation request limit ... countef log group 2 prefix ...
>
> It basically works, counter grows and packets are logged
> via ulogd2 stack::
>
> stack=log2a:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,mac2str1:HWHDR,gp1:GPRINT
>
> Except that the log entries has not any ARP headers.
>
> Then i found this article [1], which mentions the ARP as
> sysctlt key:
>
> net.netfilter.nf_log.3
This is only required for logging that is triggered
internally, e.g. for nf_conntrack.log_Invalid.
Its not needed when using LOG or NFLOG targets or
the nftables equivalents, when rule gets triggered
its crytal clear which backend should be used.
> Thus i set it to "nfnetlink_log", but that doesn't help. It
> is hard to find what these numbers are, but i guess that
> family constants, as 2, 7 and 10 (from ulogd2 start log)
> coresponds to inet, inet6 and bridge family, but i am not
> aware of arp family...
>
> I guess that ulogd2 is able to log ARP headers as i found
> them in BASE plugin's info output, but please what i have
> to do to get them into log? Or problem is, that i play with
> it inside LXC container (other logging works in it)?
I think this is missing support in ulogd2.
Untested, to give you some starting point:
(3 is NFPROTO_ARP).
--- a/filter/raw2packet/ulogd_raw2packet_BASE.c
+++ b/filter/raw2packet/ulogd_raw2packet_BASE.c
@@ -959,6 +959,8 @@ static int _interp_pkt(struct ulogd_pluginstance *pi)
return _interp_ipv6hdr(pi, len);
case AF_BRIDGE:
return _interp_bridge(pi, len);
+ case 3:
+ return _interp_arp(pi, len);
}
return ULOGD_IRET_OK;
}
next prev parent reply other threads:[~2025-03-03 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 16:51 Log ARP headers Slavko
2025-03-03 19:35 ` Florian Westphal [this message]
2025-03-03 21:52 ` Slavko
2025-03-03 22:00 ` Jeremy Sowden
2025-04-05 9:54 ` Slavko
2025-04-18 11:00 ` Jeremy Sowden
2025-04-18 11:33 ` Slavko
2025-05-25 7:51 ` Slavko
2025-05-25 10:33 ` Florian Westphal
2025-05-25 17:24 ` Jeremy Sowden
2025-03-03 22:03 ` Florian Westphal
2025-03-03 22:20 ` Slavko
2025-03-05 13:20 ` Slavko
2025-03-05 13:30 ` Slavko
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=20250303193533.GA16225@breakpoint.cc \
--to=fw@strlen.de \
--cc=linux@slavino.sk \
--cc=netfilter@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).