All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc show error for ingress
Date: Fri, 06 Jun 2003 16:38:55 +0000	[thread overview]
Message-ID: <marc-lartc-105491758518556@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105491046609745@msgid-missing>

On Friday 06 June 2003 16:39, Rajesh Srivastava wrote:
> Hi,
>
> I am trying to do both ingress and egress bandwidth management on a bridge.
> eth0 is the WAN interface. IPTraf shows that the following script is
> running successfully and it limits bandwidth both ways to 256 KB
>
> However when I want to see the statistics using tc - it only shows me stats
> for htb class
> and not for ingress class. The tc output is as follows:
>
> tc -s -d class show dev eth0
> class htb 1:1 root prio 0 quantum 3276 rate 256Kbit ceil 256Kbit burst
> 1926b/8 mpu 0b cburst 1926b/8 mpu 0b level 0
>  Sent 193313679 bytes 189055 pkts (dropped 1, overlimits 0)
>  rate 32656bps 32pps backlog 9p
>  lended: 189046 borrowed: 0 giants: 0
>  tokens: -77245 ctokens: -77245
>
> What is wrong here?
Try
tc -s -d class show dev eth0 parent ffff:

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

  reply	other threads:[~2003-06-06 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06 14:39 [LARTC] tc show error for ingress Rajesh Srivastava
2003-06-06 16:38 ` Stef Coene [this message]
2003-06-06 16:51 ` Rajesh Srivastava
2003-06-06 17:26 ` Stef Coene
2003-06-07  1:01 ` Marton Sandor

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=marc-lartc-105491758518556@msgid-missing \
    --to=stef.coene@docum.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.