From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems setting up nested qdisc, feedback to LARTC HOWTO
Date: Sat, 16 Jul 2005 10:40:29 +0000 [thread overview]
Message-ID: <42D8E41D.2050207@dsl.pipex.com> (raw)
In-Reply-To: <m3slygxqh4.fsf@reason.gnuhh-core>
Georg C. F. Greve wrote:
> || On Sat, 16 Jul 2005 01:14:48 -0400
> || Jody Shumaker <jody.shumaker@gmail.com> wrote:
>
> js> When I read this earlier I thought of offering the same, i'm
> js> using a mix of -j mark and tc filters to do my routing into
> js> nexted qdiscs. Seems more like i'd consider this a bug of
> js> classify that should be fixed, and maybe a note in the howto that
> js> it is broken for now.
>
> I fully agree with your classification of this behaviour as a bug.
>
> Also I agree that ideally it should be fixed.
I don't know if I would call it a bug - you are nesting classfull qdiscs
and expecting them to know about each others classes when they don't.
You have to filter the packets from root to the leaf containing the next
qdisc and if it is classfull you have to filter again there. This is
never going to be doable with just iptables classify.
IIRC the example in LARTC doesn't nest classful - I agree documenting
your setup will be usefull - but LARTC doesn't get updated much.
FWIW your setup just wouldn't work for me - you are not limiting
bandwidth for the link - you would need htb as root to do that.
In my case if I put that on my dsl connection it would go overlimits and
I would end up with a 2 second queue in my modem.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-07-16 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 11:23 [LARTC] Problems setting up nested qdisc, feedback to LARTC HOWTO Georg C. F. Greve
2005-07-15 18:46 ` Jody Shumaker
2005-07-15 20:58 ` Georg C. F. Greve
2005-07-15 22:45 ` Georg C. F. Greve
2005-07-16 5:14 ` Jody Shumaker
2005-07-16 8:46 ` Georg C. F. Greve
2005-07-16 10:40 ` 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=42D8E41D.2050207@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=lartc@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 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.