Hello,
I was attempting to throttle egress traffic to a specific rate using a
tbf. As a starting point I used an example from the LARTC howto, which
goes:
tc qdisc add dev eth1 root tbf rate 220kbit latency 50ms burst 1540
I then attempt a large fetch from another machine via wget (~40
No takers on this question? I investigated further and it seems that
this is a specific problem with iputils-ping. It seems that regardless
of the supplied interface name, the source IP is chosen to be closest t
the default gateway. OTOH my ability to follow C code is next to
minimal, and I
Hello,
On Tue, 21 Aug 2007, Grant Taylor wrote:
I want to be able to take traffic in from a local LAN on eth0 and route
it out eth1 to a default gateway with a static IP. I want said default
gateway with the static IP to be assigned to eth2. I then want to route
and masquerade
Older versions of ping does not support interface with I option. It
won't give error, but it simply won't work. I had such an issue and was
solved with the latest ping tool.
Have you tried using tcpdump to capture packets from interfaces?
-Original Message-
From: [EMAIL PROTECTED]
My first guess would be vlans being a problem. I know at least for
class based queuing disciplines on vlans, you have to take care to
define filters that funnel traffic through a class by selecting
802.1q traffic on the real interface, not the vlan interface.
I know traffic shaping does
I answer randomly but,
perhaps you have to give 17 parameters as well for the priomap. you
have only 16 of them in your second example.
Vincent.
Le 22 août 07 à 13:24, Patrick Reinhardt a écrit :
Hello,
is it possible that the number of bands for the PRIO qdisc is
limited to 16?
tc
My first guess would be vlans being a problem. I know at least for
class based queuing disciplines on vlans, you have to take care to
define filters that funnel traffic through a class by selecting
802.1q traffic on the real interface, not the vlan interface.
Wow, why would that be though?
Marco C. Coelho wrote:
I've got a linux (2.6.18-8.1.6.el5.centos.plus) router doing pppoe
termination and HTB rate limiting.
the number of connections has grown quite a bit in the last few months,
and I'm now getting a:
HTB tree is too deep
message on the monitor.
where is the setting
Patrick Reinhardt wrote:
Hello,
is it possible that the number of bands for the PRIO qdisc is limited to 16?
tc qdisc add dev $DEVICE root handle 1: prio bands 16 priomap 1 2 2 2 1 2 0 0
1 1 1 1 1 1 1 1
succeeds but
tc qdisc add dev $DEVICE root handle 1: prio bands 17 priomap 1 2 2 2 1 2
On Wed, 2007-08-22 at 14:01 -0400, sting wrote:
My first guess would be vlans being a problem. I know at least for
class based queuing disciplines on vlans, you have to take care to
define filters that funnel traffic through a class by selecting
802.1q traffic on the real interface, not
try this:
#makes sure you've deleted anything old
#you might wanna try running /sbin/tc -s qdisc show dev eth1 to verify
your current config.
#deletes all qdisc stuff just in case
/sbin/tc qdisc del dev eth1 root
#define root qdisc
/sbin/tc qdisc add dev eth1 root handle 1: htb default 2
sting wrote:
Hello,
I was attempting to throttle egress traffic to a specific rate using a
tbf. As a starting point I used an example from the LARTC howto, which
goes:
tc qdisc add dev eth1 root tbf rate 220kbit latency 50ms burst 1540
It's not the best example as latency is a way of
David Boreham wrote:
I'm grappling with a problem that looks like sfq is not working
(packets don't get fairly queued, they appear to be always
sent FIFO). My configuration appears to be correct.
The machine is running quite an old kernel and if I could
convince myself that the sfq code it has
Andy Furniss wrote:
David Boreham wrote:
I'm grappling with a problem that looks like sfq is not working
(packets don't get fairly queued, they appear to be always
sent FIFO). My configuration appears to be correct.
The machine is running quite an old kernel and if I could
convince myself that
14 matches
Mail list logo
