All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] These tc commands used to work... what's broken them?
Date: Fri, 01 Apr 2005 20:35:08 +0000	[thread overview]
Message-ID: <424DB07C.1080901@dsl.pipex.com> (raw)
In-Reply-To: <20050325220314.73F5D32AB1D@www.davidwhite.org>

George Adams wrote:
> I have a Gentoo Linux (kernel 2.6.11) server.  Several months ago, I
> made a traffic shaping setup for my box (running a 2.4 kernel then)
> that worked beautifully.  It gave high priority to SSH and RealAudio
> traffic, and put HTTP downloading traffic on a lower prio so they could
> only use what bandwidth was left.
> 
> However, I've only just realized that tc is no longer accepting the
> commands I setup in a script to start it.  I don't know when it stopped
> working.
> 
> I can post the tcng script if anyone wants to see how I generated my tc 
> commands, but I suspect it may not be relevant since tc is bombing out 
> so early in the process.  Here's what I get:
> 
> ------------------------------------------------------------
> 
>>tc -s qdisc show dev eth0
> 
> 
> qdisc pfifo_fast 0: bands 3 priomap  1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1   
>  Sent 455120063 bytes 553706 pkt (dropped 0, overlimits 0 requeues 25)
>  rate 0bit 0pps backlog 0b 0p requeues 25
> 
> 
>>tc -s class show dev eth0
> 
> 
>>tc qdisc add dev eth0 handle 1:0 root dsmark indices 8 default_index 0

That works for me using the latest iproute2 and 2.6.12-rc1 I think you 
just hit unlucky with your version/kernel and it's been fixed now.

http://developer.osdl.org/dev/iproute2/download/iproute2-2.6.11-050330.tar.gz

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

      parent reply	other threads:[~2005-04-01 20:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-25 22:03 [LARTC] These tc commands used to work... what's broken them? George Adams
2005-04-01  5:19 ` Corey Hickey
2005-04-01 15:37 ` Thomas Graf
2005-04-01 20:35 ` 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=424DB07C.1080901@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.