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
.
--
Message: 1
Date: Tue, 21 Aug 2007 23:32:18 -0700
From: sting [EMAIL PROTECTED]
Subject: [LARTC] simple tbf rate clamping issues
To: LARTC@mailman.ds9a.nl
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset
! :)
--
Message: 1
Date: Tue, 21 Aug 2007 23:32:18 -0700
From: sting [EMAIL PROTECTED]
Subject: [LARTC] simple tbf rate clamping issues
To: LARTC@mailman.ds9a.nl
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain
.
--
Message: 1
Date: Tue, 21 Aug 2007 23:32:18 -0700
From: sting [EMAIL PROTECTED]
Subject: [LARTC] simple tbf rate clamping issues
To: LARTC@mailman.ds9a.nl
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hello,
I
report back.
But I hope that won't be the solution! :)
--
Message: 1
Date: Tue, 21 Aug 2007 23:32:18 -0700
From: sting [EMAIL PROTECTED]
Subject: [LARTC] simple tbf rate clamping issues
To: LARTC
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
