From: Madhuri Patwardhan <madhuri@cc.iitb.ac.in>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to limit a dev bandwidth.
Date: Sat, 16 Aug 2003 04:36:26 +0000 [thread overview]
Message-ID: <marc-lartc-106100796828903@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106032592806296@msgid-missing>
Hi Martin,
You have explained it so well that it is very clear now.
I am trying to do something similar on our linux firewall machines
which connect to the internet.
I have few questions regarding this.
>
> Let's try this with a little diagram:
>
> +---------------+
> Internet --| wan0 eth0 |-- private network
> +---------------+
> qdisc here qdisc here
> will shape will shape
> traffic sent traffic sent
> to Internet from Internet
>
>
> So, shape your "upload" traffic on wan0 (ACKs, maybe the packets with a
> TCP source port of 25 from your internal mailserver).
>
Here one could use plain htb qdisc (without imq) to shape the outgoing
(upload) traffic.
> Shape the "download" traffic on eth0. Here you have the opportunity of
> deliberately delaying the traffic before it reaches the client in the
> private network.
>
Now for shaping "download" ( means effectively incoming) traffic on eth0
one would need to use IMQ. Because it is not really possible to schedule
the incoming traffic without simulating it as being transmitted from IMQ
device. It will not be possible to use just plain htb qdisc without ImQ
to shape incoming traffic, is that correct?
Also, even with IMQ you cannot face situations such as flooding. If
that happens with incoming traffic then the imq is useless. Is that
correct?
What would be other ways(other than imq) to shape incoming traffic on
eth0?
(I am planning to take a look at tcng)
Thanks a lot.
Madhuri
> Once again, I would like to recommend tcng [3]. If you are not yet
> familiar with the linux traffic control subsystem, you may (will) find
> tcng considerably more approachable than the raw tc commands. I have
> written a crash course in using tcng with HTB [4], which should provide
> you enough detail to get started with tcng.
>
> Best of luck,
>
> -Martin
>
> * ...although clever people have found a way around this rule, by creating
> a device which allows us to simulate packet transmission on inbound
> traffic. See my note on IMQ above.
>
> [1] http://mailman.ds9a.nl/pipermail/lartc/2003q3/009616.html
> [2] http://trash.net/~kaber/imq/
> [3] http://tcng.sourceforge.net/
> [4] http://tldp.org/HOWTO/Traffic-Control-tcng-HTB-HOWTO/
>
> --
> Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-08-16 4:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 6:59 [LARTC] How to limit a dev bandwidth anzp
2003-08-08 17:06 ` Stef Coene
2003-08-10 0:16 ` Martin A. Brown
2003-08-14 10:57 ` Raghuveer
2003-08-15 4:16 ` Martin A. Brown
2003-08-16 4:36 ` Madhuri Patwardhan [this message]
2003-08-16 17:18 ` Martin A. Brown
2003-08-16 18:43 ` Madhuri Patwardhan
2003-08-19 9:26 ` Raghuveer
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-106100796828903@msgid-missing \
--to=madhuri@cc.iitb.ac.in \
--cc=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.