From: "David Boreham" <david_list@boreham.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Duplexing
Date: Mon, 09 Aug 2004 14:38:17 +0000 [thread overview]
Message-ID: <007001c47e1e$82634900$fa23f741@racoon> (raw)
In-Reply-To: <41178695.20908@ycc.com>
> I haven't seen anything in tc (not iptables) that addresses direction -
> inbound or outbound.
Shaping is always done on outbound traffic only.
You can't shape incoming traffic -- it arrives at
whatever rate the sender at the other end decides
to sent at.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-08-09 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 14:13 [LARTC] Duplexing Bill Gradwohl
2004-08-09 14:26 ` Tomas Simonaitis
2004-08-09 14:38 ` David Boreham [this message]
2004-08-09 15:01 ` John Sullivan
2004-08-09 15:06 ` Rene Gallati
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='007001c47e1e$82634900$fa23f741@racoon' \
--to=david_list@boreham.org \
--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.