From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] why shape incoming traffic
Date: Fri, 01 Mar 2002 10:04:27 +0000 [thread overview]
Message-ID: <marc-lartc-101497713902188@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101494774514020@msgid-missing>
On Thu, Feb 28, 2002 at 05:53:15PM -0800, Don Cohen wrote:
> > On Thu, Feb 28, 2002 at 10:08:16AM +0100, Martin Devera wrote:
> > > qdisc (shaper) only for outgoing data. It is generaly
> > > believed to be dumb to throttle data when they already
> > > reached your computer or gateway.
> >
> > The only reason I've ever been able to see for incoming data shaping is
> > to reorder packets so that, for example, FINs are sent to their
> > respective applications before SYNs (just an example) or ACKs before data.
>
> It doesn't seem very important to shape the incoming traffic that will
> be forwarded, since the same shaping can be done at output.
An important reason to be able to do incoming shaping is that you may lose
information while routing, which doesn't help you with shaping on egress.
For example, to shape traffic going via a proxy server, outgoing.
There is no way to recognize on ppp0 that traffic was generated by an
internal host who sent it to eth0, where it was packaged by a proxy, and
sent out over ppp0.
With ingress shaping I would be able to do that.
So in short - if you like CBQ, HTB etc on egress, and you accept that
informationloss occurs between ingress and egress, you want to be able to
shape ingress.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
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-03-01 10:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 1:53 [LARTC] why shape incoming traffic Don Cohen
2002-03-01 10:04 ` bert hubert [this message]
2002-03-01 15:47 ` Don Cohen
2002-03-01 15:50 ` bert hubert
2002-03-01 19:27 ` Michael T. Babcock
2002-03-01 19:34 ` Michael T. Babcock
2002-03-01 21:48 ` Don Cohen
2002-03-02 11:16 ` Michael T. Babcock
2002-03-04 5:05 ` Michael T. Babcock
2002-03-04 15:22 ` Don Cohen
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-101497713902188@msgid-missing \
--to=ahu@ds9a.nl \
--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.