From: Patrick McHardy <kaber@trash.net>
To: Brad Fisher <brad@info-link.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH] Re: Setting skb->priority with libnetfilter_queue (patch really attached this time)
Date: Thu, 06 Apr 2006 13:03:58 +0200 [thread overview]
Message-ID: <4434F59E.6060000@trash.net> (raw)
In-Reply-To: <44285BC2.3020602@info-link.net>
Brad Fisher wrote:
> Sorry - I got trigger happy and sent without attaching the patch...
> Patches should be attached now.
> -Brad
>
> Brad Fisher wrote:
>
>> In case anyone is interested, I have written a couple of small patches
>> to accomplish what I desired. It adds three new functions to
>> libnetfilter_queue:
>>
>> /* Set both mark and priority */
>> int nfq_set_verdict_mark_priority(struct nfq_q_handle *qh, u_int32_t
>> id, u_int32_t verdict, u_int32_t mark, u_int32_t priority,
>> u_int32_t data_len, unsigned char *buf)
>>
>> /* Sets priority, but leaves mark unchanged */
>> int nfq_set_verdict_priority(struct nfq_q_handle *qh, u_int32_t id,
>> u_int32_t verdict, u_int32_t priority,
>> u_int32_t data_len, unsigned char *buf)
>>
>> /* Get current skb->priority value */
>> u_int32_t nfq_get_priority(struct nfq_data *nfad)
I think allowing to set skb->priority makes sense, but I'm not entirely
happy with the 2^n nfq_set_verdict_* combinations. It would be nicer
if we had some struct representing the packet and some functions to
change nfmark, priority etc. Then we could just do
nfq_set_verdict(qh, pkt, verdict).
prev parent reply other threads:[~2006-04-06 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 19:40 Setting skb->priority with libnetfilter_queue Brad Fisher
2006-03-27 21:38 ` [PATCH] " Brad Fisher
2006-03-27 21:40 ` [PATCH] Re: Setting skb->priority with libnetfilter_queue (patch really attached this time) Brad Fisher
2006-04-06 11:03 ` Patrick McHardy [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=4434F59E.6060000@trash.net \
--to=kaber@trash.net \
--cc=brad@info-link.net \
--cc=netfilter-devel@lists.netfilter.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 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.