From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] shaping incoming with ingress
Date: Thu, 31 Jul 2003 11:34:20 +0000 [thread overview]
Message-ID: <marc-lartc-105965135308609@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105960881709594@msgid-missing>
On Thursday 31 July 2003 12:00, Rio Martin. wrote:
> On Thursday 31 July 2003 16:46, you wrote:
> > If I understand correctly, you have 1 router with 2 nics. So you shape
> > incoming traffic on nic1 by shaping outgoing traffic on nic2. This is
> > fine for your setup, but if you 3 nic's and you are running some services
> > on the router, you will have a problem.
>
> If i want to add more service, i will ask my boss to prepare another PC for
> those service, simple isnt it ? (:
> It would be better and wont interfere the performance of bandwidth manager
> ..
It's best if you have a dedicated shaper in bridge mode behind your firewall.
So all traffic passes thru the shaper and the shaper sees the real ip
addresses. If the shaper is in bridge mode, your don't have to change your
network toplogy. And you can even remove the shaper for tests/repairs
without interrupting your network.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-07-31 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 23:45 [LARTC] shaping incoming with ingress Damion de Soto
2003-07-31 3:00 ` Martin A. Brown
2003-07-31 3:55 ` Rio Martin.
2003-07-31 5:50 ` smohan
2003-07-31 9:46 ` Stef Coene
2003-07-31 9:46 ` Stef Coene
2003-07-31 9:56 ` Rio Martin.
2003-07-31 11:34 ` Stef Coene [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-105965135308609@msgid-missing \
--to=stef.coene@docum.org \
--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.