Skip to contentSkip to conversation

tc show error for ingress

LARTC Rajesh Srivastava 3 participants 5 messages Jun 6, 2003 – Jun 7, 2003

lore
Share & tools
lore
#0 lore 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 / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#1 lore raw
Quoted 18 lines · Rajesh Srivastava

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

Quoted 1 line

What is wrong here?

Try
tc -s -d class show dev eth0 parent ffff:

Stef

Signature · 8 lines
[email protected]
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#2 lore raw
In reply to Rajesh Srivastava

Stef,

tc -s -d class show dev eth0 parent ffff:
gives no output.

I am using the latest tc which has been download and built with the 2.4.20 kernel includes.

Thanks,

Rajesh

Quoted 4 lines · Rajesh Srivastava
Quoted 3 lines

Hi,

I am trying to do both ingress and egress bandwidth management on a

bridge.

Quoted 4 lines
Quoted 4 lines

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

Quoted 15 lines
Quoted 11 lines

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

Quoted 1 line

What is wrong here?

Try
tc -s -d class show dev eth0 parent ffff:

Quoted 10 lines

Stef

--

[email protected]
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#3 lore raw
In reply to Rajesh Srivastava
Quoted 7 lines · Rajesh Srivastava

Stef,

tc -s -d class show dev eth0 parent ffff:
gives no output.

I am using the latest tc which has been download and built with the 2.4.20 kernel includes.

It was just a guess of me. I don't use ingress myself, but I know you can specify a parent parameter.
Sorry, can't help you further.

Stef

Signature · 8 lines
[email protected]
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#4 lore raw
In reply to Rajesh Srivastava

Ingress is a qdisc not a class.
tc -s -d qdisc show dev eth0 should give the stats.

Quoted 18 lines · Rajesh Srivastava

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

Signature · 5 lines
 Marton Sandor  -  [email protected]

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/