All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rajesh Srivastava" <rajesh@balcomt.com>
To: lartc@vger.kernel.org
Subject: [LARTC] tc show error for ingress
Date: Fri, 06 Jun 2003 14:39:04 +0000	[thread overview]
Message-ID: <marc-lartc-105491046609745@msgid-missing> (raw)

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?

The shaping+limiting script is provided below

---
#Delete existing qdics
tc qdisc del dev eth0 root
tc qdisc del dev eth0 ingress
#add HTB for egress
tc qdisc add dev eth0 root handle 1: htb default 1
tc class add dev eth0 parent 1: classid 1:1 htb rate 256kbit ceil 256kbit
#Add ingress queue
tc qdisc add dev eth0 handle ffff: ingress
tc filter add dev eth0 parent ffff: protocol ip prio 50 u32 match ip src
0.0.0.0/0 police rate 256kbit burst 10k drop flowid :1

Thanks

Rajesh


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

             reply	other threads:[~2003-06-06 14:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06 14:39 Rajesh Srivastava [this message]
2003-06-06 16:38 ` [LARTC] tc show error for ingress Stef Coene
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-105491046609745@msgid-missing \
    --to=rajesh@balcomt.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.