All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: Netfilter-devel <netfilter-devel@lists.netfilter.org>,
	Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: Re: [PATCH] CLASSIFY target
Date: Wed, 09 Apr 2003 01:26:20 +0200	[thread overview]
Message-ID: <3E935A9C.9030700@trash.net> (raw)
In-Reply-To: <1049832299.1318.19.camel@tux.rsn.bth.se>

Hi Martin,
thanks for your response,

Martin Josefsson wrote:

>Regarding this patch... iirc, Bert Hubert wrote a similar target a while
>ago and I think he wanted a small change in the core QoS stuff and that
>was voted down, might be something to look into?
>
>I think the discussion took place on the netdev list.
>

Google found a discussion about moving "skb->priority = sk->priority" 
line to
ip_queue_xmit2 to allow netfilter targets to override SO_PRIORITY value of
local sockets. A quick check told me this change was never made, so the
CLASSIFY target is only working correctly in the POST_ROUTING chain, which
is what i have tested. This doesn't seem to affect usage of the target, 
worse
would be if POST_ROUTING didn't work correctly. My suggestion is to
restrict usage to POST_ROUTING chain, this seems like a natural place for
QoS classification. What do you think ?

Thanks,
Patrick

  reply	other threads:[~2003-04-08 23:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08 16:04 [PATCH] CLASSIFY target Patrick McHardy
2003-04-08 20:05 ` Martin Josefsson
2003-04-08 23:26   ` Patrick McHardy [this message]
2003-04-09  0:21     ` Martin Josefsson
2003-04-09  1:14       ` Patrick McHardy
2003-04-11 10:15         ` Jozsef Kadlecsik
2003-04-13 16:24       ` Harald Welte
2003-04-13 16:22   ` Harald Welte

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=3E935A9C.9030700@trash.net \
    --to=kaber@trash.net \
    --cc=gandalf@wlug.westbo.se \
    --cc=kadlec@blackhole.kfki.hu \
    --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.