All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Georg C. F. Greve" <greve@fsfeurope.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems setting up nested qdisc, feedback to LARTC HOWTO
Date: Fri, 15 Jul 2005 20:58:09 +0000	[thread overview]
Message-ID: <m3br53u6qm.fsf@reason.gnuhh-core> (raw)
In-Reply-To: <m3slygxqh4.fsf@reason.gnuhh-core>


[-- Attachment #1.1: Type: text/plain, Size: 1422 bytes --]

 || On Fri, 15 Jul 2005 14:46:24 -0400
 || Jody Shumaker <jody.shumaker@gmail.com> wrote: 

 js> Have you tried not using classify but instead using tc filters?

Well, the tc filters are much more limited than iptables, they could
not replicate what I am doing with the iptables. That is why I tried
using the -j MARK iptables target to set a tc filter based on that.


 js> Maybe this is a limitation with iptables classify.  Try using
 js> your classify to put things into 20: and then use tc filters
 js> attached to 20: to split into the htb subclasses?

Interesting idea.

It is comforting that you have done something similar with success, so
I guess a combination of -j MARK and -j CLASSIFY targets might be able
to do that job, I will have to try this.

But having to employ such a mix seems like a cludge, shouldn't this
work properly with CLASSIFY, as well? Nothing in the documentation
says that it shouldn't -- and the docs are missing sufficiently
complex examples to get an idea of how others solved that problem.

It seems some problem exists, it is just not clear to me yet whether
this is a bug in the documentation or the software.

Regards,
Georg

-- 
Georg C. F. Greve                                 <greve@fsfeurope.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Join the Fellowship and protect your freedom!     (http://www.fsfe.org)

[-- Attachment #1.2: Type: application/pgp-signature, Size: 309 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-07-15 20:58 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 [this message]
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

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=m3br53u6qm.fsf@reason.gnuhh-core \
    --to=greve@fsfeurope.org \
    --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.