From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oki DZ okidz@telkom.net Date: Thu, 25 Jan 2001 00:09:39 +0000 Subject: [LARTC] Limiting incoming bandwidth Message-Id: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org 
Hi,

Due to the fact that you can only limit out-going packets, I'd like to 
to the following:

+             |  128Kbps                    10Mbps |
+ [Internet]  |  [eth0]---[eth1]  [eth2]----[eth3] | [Int. LAN]
+             |              |       |             |
+                            +-------+
+                             x'ed UTP

So that for limiting the incoming bandwidth, I'm going to set up tc on 
the eth2. Problem is, would this kind of setup burn the CPU pretty fast?

BTW, the router is a P III machine (also running Squid), and I don't 
think that I could go any faster.

Another question, can the above setup be accomplished by using 
/dev/tapX's? I have tried to have /dev/tap0 running. But when I looked 
the device up using tcpdump, there was nothing in it. (I bound Squid on 
the tap device, and had the routing set up properly.)

Thanks in advance,
Oki
-- 
An implication embedded in this is that the socialist days
of the Internet are over. Socially, the advent of IP-QoS is
already being blamed for introducing a caste system on
the Internet: the ``bit-haves'' and ``bit-have-nots''
are becoming reality.
http://www2.linuxjournal.com/lj-issues/issue62/3369.html