All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oki DZ okidz@telkom.net
To: lartc@vger.kernel.org
Subject: [LARTC] Limiting incoming bandwidth
Date: Thu, 25 Jan 2001 00:09:39 +0000	[thread overview]
Message-ID: <marc-lartc-98373940416913@msgid-missing> (raw)

<PRE>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.
<A HREF="http://www2.linuxjournal.com/lj-issues/issue62/3369.html">http://www2.linuxjournal.com/lj-issues/issue62/3369.html</A>



</PRE>

                 reply	other threads:[~2001-01-25  0:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-98373940416913@msgid-missing \
    --to=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.