Re: Shaper problem in 2.2.14.

From: Daniel Ryde (ryde@tripnet.se)
Date: Tue Feb 22 2000 - 10:17:43 EST


On Tue, 22 Feb 2000, Alan Cox wrote:

> > TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
>
> Its also sending out your ping packets. Thus it seems most odd that the
> replies didnt get out. Do both the ethernet and the shaper tx increment
> matching ?

Nope. Found no way how to reset the counters, but:

$ ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:80:C8:57:36:5A
          inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:186 errors:0 dropped:0 overruns:0 frame:0
          TX packets:87 errors:0 dropped:0 overruns:0 carrier:0
          Collisions:0
          Interrupt:5 Base address:0xa400

$ ifconfig shaper0
shaper0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          inet addr:192.168.0.1 Mask:255.255.255.0
          UP RUNNING MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          Collisions:0

$ ping -c 1 192.168.0.2
PING 192.168.0.2 (192.168.0.2): 56 data bytes

--- 192.168.0.2 ping statistics ---
1 packets transmitted, 0 packets received, 100% packet loss

$ ifconfig shaper0
shaper0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          inet addr:192.168.0.1 Mask:255.255.255.0
          UP RUNNING MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
          Collisions:0

$ ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:80:C8:57:36:5A
          inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:188 errors:0 dropped:0 overruns:0 frame:0
          TX packets:89 errors:0 dropped:0 overruns:0 carrier:0
          Collisions:0
          Interrupt:5 Base address:0xa400

The eth1 rx and tx counters increase by 2, but shaper0 tx increase by 1.

IMHO painful lack of documentation on iproute. Not a single word on rate
limiting or traffic shaping, seems mostly like queue oriented things...
How on earth do I set up a 64Kbit rate limit using iproute?

/Dr

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:30 EST