All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: [LARTC] QOS Script difficulty on bridge
Date: Wed, 16 Jun 2004 15:53:19 +0000	[thread overview]
Message-ID: <40D06CEF.3000005@wildgooses.com> (raw)

I'm playing with the rather excellent QOS script from Alexander Clouter  
at http://digriz.org.uk/jdg-qos-script/

So far I am really impressed with it - a very impressive example of the 
power of linux QOS rules (has pretty much everything in it from the 
LARTC Howto!)  However, the instructions hint that "for QoS to affect 
locally generated traffic in a non ethernet bridge setup you must have 
IMQ". 

Now, I *DO* have a bridged config (br -> eth0 & eth1), but I can't see 
how I can set things up so that traffic from the local machine suffers 
the effect of the QOS limitations (on download) without using IMQ.

More broadly, can *anyone* see how it might be possible to limit the 
download rate to a local machine running as a bridge, without using IMQ? 
(err, and not using the policer either, I want an HTB qdisk running on 
the download traffic - I just want to know if I am missing something 
obvious about the way the bridge works)

Just for reference only the bridge has an ip address, both physical 
interfaces are anonymous.

Thanks for any pointers. 

Ed W

P.S. Anyone using this script on 2.6 with a bridge needs to be aware 
that the syntax for "tc" has changed.  You can't use "tc -i eth0" 
anymore, you need "tc -i br0 -m physdev --physdev-in eth0".  And the 
same for "-o".  Hope that helps anyone who tries the script out

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2004-06-16 15:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 15:53 Ed Wildgoose [this message]
2004-06-16 17:29 ` [LARTC] QOS Script difficulty on bridge S Mohan
2004-06-16 18:02 ` Jason Boxman
2004-06-16 21:31 ` Ed Wildgoose
2004-06-17  7:29 ` Ed Wildgoose
2004-06-17 18:10 ` Jason Boxman
2004-06-17 20:38 ` Ed Wildgoose

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=40D06CEF.3000005@wildgooses.com \
    --to=lists@wildgooses.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.