From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: Karel Rericha <karel@maxent.cz>
Cc: netfilter@lists.netfilter.org
Subject: Re: downlink marked packets dont go to qdisc, uplink ok
Date: Thu, 23 Dec 2004 01:16:40 +0000 [thread overview]
Message-ID: <41CA1C78.2030502@dsl.pipex.com> (raw)
In-Reply-To: <41B97CCE.2060904@maxent.cz>
Karel Rericha wrote:
> Short:**********************************************************
>
> On Mandrake 10.0 router with htb shaping I have to use U32 classifier
> for inserting
> packets to downlink qdiscs, because marking packets only work for uplink
> qdiscs.
> Downlink packets are properly market, but always reach only default
> class without
> U32. Why?
The LARTC list is back up now.
Maybe what you see is a quirk of shaping on br0 rather than a real
interface. If you really need to mark then you could try using IMQ -
www.linuximq.net
Andy.
prev parent reply other threads:[~2004-12-23 1:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 10:39 downlink marked packets dont go to qdisc, uplink ok Karel Rericha
2004-12-15 15:55 ` Karel Rericha
2004-12-23 1:16 ` Andy Furniss [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=41CA1C78.2030502@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=karel@maxent.cz \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox