Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: marco ghidinelli <marcogh@linux.it>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Weighted packet shaping?
Date: Mon, 03 Jan 2005 11:22:15 +0000	[thread overview]
Message-ID: <20050103112214.GA10708@circolab.net> (raw)
In-Reply-To: <20041221034303.GB27656@linux.comp>

On Tue, Dec 28, 2004 at 07:53:43PM +1030, Mark Williams (MWP) wrote:
> 
> Ok...
> Using your script gave the following (from 17:30 onwards):
> 
> http://www.overclockers.com.au/~mwp/temp/tc-1hour-yours.png
> 
> Purple is class 23; all other traffic, in this case bittorrent.
> Blue is class 21; a windows box, in this case an FTP transfer.
> 
> Shouldnt class 23 still be dropping off further than that?
> It seems HTB is wanting to share traffic equally among on the classes rather than by priority.
> 
> You script is pretty much having the same effect as mine :(

ok, maybe i'm wrong, but i try to run the same script, and i think that
the script have problem setting prio 0 on filters:

running:

$TC filter add dev $IFNAME parent 1:0 prio 0 protocol ip handle 22 fw
flowid 1:20
$TC filter add dev $IFNAME parent 1:0 prio 2 protocol ip handle 21 fw
flowid 1:21

gave me:

# tc filter list dev eth0
filter parent 1: protocol ip pref 2 fw 
filter parent 1: protocol ip pref 2 fw handle 0x15 classid 1:21 
filter parent 1: protocol ip pref 49152 fw 
filter parent 1: protocol ip pref 49152 fw handle 0x16 classid 1:20 

----------------------------------^^^^^

don't blame me if this is obvious/wrong/stupid. :)

2.6.10, with lastest iproute2

-- 
BOFH excuse #212:

Of course it doesn't work. We've performed a software upgrade.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2005-01-03 11:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21  3:55 [LARTC] Weighted packet shaping? Mark Williams (MWP)
2004-12-22  4:53 ` Mark Williams (MWP)
2004-12-22  9:07 ` Ed Wildgoose
2004-12-22 13:49 ` Andy Furniss
2004-12-22 15:48 ` Mark Williams (MWP)
2004-12-22 22:54 ` Andy Furniss
2004-12-23 10:56 ` Mark Williams (MWP)
2004-12-24 14:08 ` Andy Furniss
2004-12-24 15:19 ` Mark Williams (MWP)
2004-12-24 16:36 ` Andy Furniss
2004-12-26  4:38 ` Mark Williams (MWP)
2004-12-26 13:09 ` Andy Furniss
2004-12-28  9:35 ` Mark Williams (MWP)
2004-12-29  2:46 ` Andy Furniss
2004-12-29  6:52 ` Mark Williams (MWP)
2004-12-29 13:26 ` Francisco Pereira
2004-12-30  0:05 ` Andy Furniss
2005-01-03 11:22 ` marco ghidinelli [this message]
2005-01-04 13:57 ` 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=20050103112214.GA10708@circolab.net \
    --to=marcogh@linux.it \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox