From: John Anthony Kazos Jr. programmer@vt.edu
To: lartc@vger.kernel.org
Subject: [LARTC] Shaping Incoming Traffic
Date: Thu, 16 Nov 2000 20:09:37 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216928@msgid-missing> (raw)
<PRE>Is there no way to shape incoming traffic? With any kernel version, or
even by rewriting the networking code? I understand the difficulties, and
the reasons why outgoing shaping is simple at the low-level but incoming
shaping is not done even at the high-level, but what about this? Use the
TCP window field to restrict the rate of data transfer (not worrying about
the details right now; just the general feasibility). (This is for a
single box, rather than for a box on a network which has a separate router
to shape its traffic.) If a node were to consistently violate the window,
it could be blocked until the administrator fixed the problem at that
node. (This is intended for thsoe who do not intend to violate the
policies of the server, rather than those who may wish to do so
maliciously.)
I'd just like some pointers and hints for this...it seems workable to me.
But if there is another way, or *any* way, I'd rather pursue that before
the TCP way so I can see which is better. I'm simply discouraged by the
fact that no one seems to have tried this before, while it seems a
painfully obvious way to do it to me, so I wonder what I'm missing
conceptually.
</PRE>
next reply other threads:[~2000-11-16 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-16 20:09 John [this message]
2000-11-17 8:42 ` [LARTC] Shaping Incoming Traffic
2000-11-17 12:53 ` Gregory
2000-11-24 15:38 ` [LARTC] shaping incoming traffic steeman
2003-02-11 17:03 ` [LARTC] Shaping " Andreas Wright
2003-02-11 18:11 ` Stef Coene
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-98373938216928@msgid-missing \
--to=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.