From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How much does it matter where the throttling is done?
Date: Mon, 25 Nov 2002 17:10:11 +0000 [thread overview]
Message-ID: <marc-lartc-103824431618552@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103820565817632@msgid-missing>
On Monday 25 November 2002 07:25, Brian Capouch wrote:
> I got into a "spirited discussion" tonight about just what the upstream
> effects of traffic shaping look like.
>
> In the case in point, a private WAN with quite a few routers connects to
> a number of Internet POPs. In some cases, the "leaves" are three or
> four hops from the backbone source.
>
> The central focus of the discussion was the relative harm/benefit from
> putting the traffic shaper at the point where the bandwidth hits the
> Internet, at one extreme, versus at the "last-hop" routers on the other.
>
> I won't go into the details as I suspect there is probably a cut and
> dried answer.
>
> And rather than proffering my own ideas, I would rather not embarrass
> myself and just ask the experts.
It all depends on the network configuration. You have to shape on the
bottleneck on the network. If you don't do that, your shaping can be undone
by the bottleneck.
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/
next prev parent reply other threads:[~2002-11-25 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 6:25 [LARTC] How much does it matter where the throttling is done? Brian Capouch
2002-11-25 17:10 ` Stef Coene [this message]
2002-11-25 18:55 ` [LARTC] How much does it matter where the throttling is Art Reisman
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-103824431618552@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.