From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shaping incoming traffic?
Date: Sun, 18 Nov 2001 23:50:57 +0000 [thread overview]
Message-ID: <marc-lartc-100694028702680@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100608970116427@msgid-missing>
On Mon, Nov 19, 2001 at 12:21:19AM +1100, Manfred Bartz wrote:
>
> 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?
"Shaping" of incoming traffic would only (if anything) have an effect
on applications that received that traffic and/or CPU usage, it
wouldn't change whether or not packets got to you. The problem is that
by the time the packet is in the shaping routine, it has already
inherently passed your network interface. At that point, it had
already passed your ISP's router and any limitations they have on your
incoming traffic (like speed caps, etc.). If your interface was fully
congested or your incoming bandwidth is saturated at the ISP link, the
ISP would be dropping/queuing packets, not you. If you are
experiencing incoming network congestion (packets are out of order
during high usage times is a good indicator), then ask your ISP if they
will shape the traffic to you based on your preferences.
--
Michael T. Babcock
CTO, FibreSpeed Ltd.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-11-18 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 13:21 [LARTC] Shaping incoming traffic? Manfred Bartz
2001-11-18 13:48 ` Martin Devera
2001-11-18 14:17 ` Manfred Bartz
2001-11-18 23:50 ` Michael T. Babcock [this message]
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-100694028702680@msgid-missing \
--to=mbabcock@fibrespeed.net \
--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