From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] most out of qos
Date: Thu, 06 Feb 2003 17:01:08 +0000 [thread overview]
Message-ID: <marc-lartc-104455093702997@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104445994220942@msgid-missing>
: > I'd suggest that Tomas throttles his bandwidth on transmit to the internal
: > network. It is a router, so very little traffic will be initiated from
: > the router itself.
: > Why not perform traffic control on packets transmitted to the Internet on
: > the outward facing NIC.
: > Then perform traffic control on packets received from the Internet on the
: > inward facing NIC.
: > What's wrong with this?
: Euh nothing :)
: But you have the same problem. You are controlling already received data. So
: you can only hope that the other end of the link stops sending data if you
: drop packets.
Well, slap me with a wet fish! That's pretty obvious.
(Martin, neophyte with traffic control, returns to routing.)
Thanks, Stef,
-Martin
--
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/
next prev parent reply other threads:[~2003-02-06 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 15:44 [LARTC] most out of qos Tomas Bonnedahl
2003-02-05 21:13 ` Stef Coene
2003-02-05 21:28 ` Tomas Bonnedahl
2003-02-06 10:04 ` Tomas Bonnedahl
2003-02-06 16:23 ` Stef Coene
2003-02-06 16:29 ` Tomas Bonnedahl
2003-02-06 16:47 ` Stef Coene
2003-02-06 16:49 ` Martin A. Brown
2003-02-06 16:58 ` Stef Coene
2003-02-06 17:01 ` Martin A. Brown [this message]
2003-02-06 17:11 ` Tomas Bonnedahl
2003-02-06 17:22 ` Stef Coene
2003-02-06 17:37 ` Tomas Bonnedahl
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-104455093702997@msgid-missing \
--to=mabrown-lartc@securepipe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox