From: "S Mohan" <smohan@vsnl.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] traffic controlling strategy
Date: Wed, 25 Jun 2003 02:31:02 +0000 [thread overview]
Message-ID: <marc-lartc-105650768121847@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105644555723803@msgid-missing>
Shaping is done on the physical device irrespective of number of virtual
interface unless there is a specific virtual device support in kernel like
for IMQ. Best option would be to shape traffic on eth1 and eth0. Activate
policing for ingress queue on eth0 (external interface). Queue builds up for
incoming on linux box for incoming traffic.
Reason for this, no change/ recompilation of kernel required. Stable (look
at recent post on IMQ bug fix). IMQ need be used only if you want to
control/cap aggregated incoming and outgoing bandwidth and not control them
individually.
Mohan
-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]On
Behalf Of Kai Weber
Sent: Tuesday, June 24, 2003 6:20 PM
To: lartc
Subject: Re: [LARTC] traffic controlling strategy
* alexandru matei <alex@qb.ro>:
> 1/ using default outbound shaping on eth1 (outside interface) for
> outgoing and outbound shaping on eth0 (inside interface) for incoming
> 2/ using default outbound shaping on eth1 (outside interface) for
> outgoing and inbound shaping (with IMQ) on eth1 (outside interface) for
> incoming
> ...
> Which combination do you recommand? Any reason for your recommandation?
I have the same problem and thinking of an third strategy:
3/ Splitting the outside interface into two virtual interfaces: eth0:0
for incoming, eth0:1 for outgoing traffic and routing the two interfaces
that both traffic seems to go out of the interface.
Bad english maybe, but probably totally wrong, too.
Kai
--
* mail kai.weber@glorybox.de
web http://www.glorybox.de
pgp 0x594D4132
_______________________________________________
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/
prev parent reply other threads:[~2003-06-25 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 9:01 [LARTC] traffic controlling strategy alexandru matei
2003-06-24 12:49 ` Kai Weber
2003-06-25 2:31 ` S Mohan [this message]
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-105650768121847@msgid-missing \
--to=smohan@vsnl.com \
--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.