From: Patrick McHardy <kaber@trash.net>
To: Jan Srzednicki <w@303.krakow.pl>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ipt_CLASSIFY module
Date: Mon, 21 Apr 2003 16:23:34 +0200 [thread overview]
Message-ID: <3EA3FEE6.3010601@trash.net> (raw)
In-Reply-To: <20030421140746.GQ89044@spitfire.303.krakow.pl>
Hi Jan,
thanks for your patch ;)
My first version worked in FORWARD chain, too. The problem is
LOCAL_OUT doesn't work because "skb->priority = sk->priority"
line in ip_queue_xmit2. It was discussed to move it to ip_queue_xmit
some time ago because Bert Huber made a similar patch but the
networking maintainers didn't like it. So for consistency i decided
to restrict usage to POST_ROUTING only. Harald said he would have
no problem with such a change because he doesn't plan to submit
the CLASSIFY target in the near future anyways, so maybe an
incremental patch which enables use in FORWARD and OUTPUT
chain would be ok ..
Best regards,
Patrick
Jan Srzednicki wrote:
>Hello there,
>
>I've just checked: -j CLASSIFY works well also in mangle table, chain
>FORWARD (with HTB, if that matters). So I made a little fix for that:
>
>--- ipt_CLASSIFY.c.old Mon Apr 21 16:02:08 2003
>+++ ipt_CLASSIFY.c Mon Apr 21 15:58:12 2003
>@@ -39,8 +39,9 @@
> return 0;
> }
>
>- if (hook_mask & ~(1 << NF_IP_POST_ROUTING)) {
>- printk(KERN_ERR "CLASSIFY: only valid in POST_ROUTING.\n");
>+ if (hook_mask & ~(1 << NF_IP_POST_ROUTING) &&
>+ hook_mask & ~(1 << NF_IP_FORWARD) ) {
>+ printk(KERN_ERR "CLASSIFY: only valid in POSTROUTING or FORWARD.\n");
> return 0;
> }
>
>greets,
>
>
prev parent reply other threads:[~2003-04-21 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 14:07 ipt_CLASSIFY module Jan Srzednicki
2003-04-21 14:23 ` 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=3EA3FEE6.3010601@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=w@303.krakow.pl \
/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.