From: Patrick McHardy <kaber@trash.net>
To: Jeremy Jackson <jerj@coplanar.net>
Cc: netdev@vger.kernel.org,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: PF_PACKET or nfnetlink logging of skb->priority
Date: Thu, 19 Feb 2009 00:57:56 +0100 [thread overview]
Message-ID: <499CA084.30209@trash.net> (raw)
In-Reply-To: <1234990308.18165.68.camel@ragnarok>
Jeremy Jackson wrote:
> It seems that there is nothing that can capture the skb->priority
> outside the kernel.
>
> There is an iptables *target* "CLASSIFY", which can *set* skb->priority,
> but there is no iptables *match* based on it.
>
> tcpdump/pcap/PF_PACKET are oblivious to skb->priority.
>
> netfilter netlink queue can export the skb->mark like the right
> mechanism, but it doesn't touch skb->priority anywhere. Perhaps there
> needs to be a another one in include/linux/netfilter/nfnetlink_queue.h:
>
> enum nfqnl_attr_type {
> NFQA_UNSPEC,
> NFQA_PACKET_HDR,
> NFQA_VERDICT_HDR, /* nfqnl_msg_verdict_hrd */
> NFQA_MARK,
> ... etc
> NFQA_SKBPRIORITY
>
> The specific use I'm thinking of now, is troubleshooting priority
> queueing with "tc" by being able to log or tcpdump traffic for a
> specific qdisc/class.
>
> It might also be nice to be able to tcpdump and/or log packets going
> into or out of a specific qdisc/class, but I'd settle for dumping
> packets based on skb->priority.
>
I think this makes a lot of sense for nfnetlink_queue/log, I'll
gladly take patches :) It should also support changing the priority
using nfnetlink_queue, that would simplify userspace classification
since you don't need to map to mark values, just to have the
classifier map it back to classes.
For libpcap the main problem will probably be that its meta data
that needs to be stored in the pseudo header and you'll need to
keep the format compatible and the tools need to be changed to
interpret it. Using netfilter definitely looks like the easier
route :)
parent reply other threads:[~2009-02-18 23:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1234990308.18165.68.camel@ragnarok>]
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=499CA084.30209@trash.net \
--to=kaber@trash.net \
--cc=jerj@coplanar.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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).