From: "Manfred Bartz" <md-lartc@logi.cc>
To: lartc@vger.kernel.org
Subject: [LARTC] Shaping incoming traffic?
Date: Sun, 18 Nov 2001 13:21:19 +0000 [thread overview]
Message-ID: <marc-lartc-100608970116427@msgid-missing> (raw)
I would like to differentiate incoming traffic streams to guarantee
minimum bandwidth to some services. However, as per the
Adv-Routing-HOWTO it appears that only outgoing traffic can be shaped.
Is this correct or is there a way of shaping incoming traffic?
The problem could possibly be overcome if there is a way of routing
traffic through a virtual host. Any tips on how to go about that?
--
Manfred
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next reply other threads:[~2001-11-18 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 13:21 Manfred Bartz [this message]
2001-11-18 13:48 ` [LARTC] Shaping incoming traffic? Martin Devera
2001-11-18 14:17 ` Manfred Bartz
2001-11-18 23:50 ` Michael T. Babcock
2001-11-19 10:42 ` Fredrik Björk
2001-11-19 11:07 ` devik
2001-11-20 7:12 ` Kristian Hoffmann
2001-11-20 9:12 ` Martin Devera
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-100608970116427@msgid-missing \
--to=md-lartc@logi.cc \
--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.