From: Kerin Millar <kerframil@gmail.com>
To: gentoo-server@lists.gentoo.org
Subject: [gentoo-server] Re: Relatively recent guide on TCP congestion-avoidance algo's & traffic shaping
Date: Mon, 16 Jan 2012 19:10:25 +0000 [thread overview]
Message-ID: <jf1snf$5uu$1@dough.gmane.org> (raw)
In-Reply-To: <BANLkTikK9VdGO__BejX-0SWXPWX2a__42g@mail.gmail.com>
On 01/07/2011 01:58, Pandu Poluan wrote:
> Another factor that made me re-think my setup is the 'strange'
> characteristics of traffic between my office and our
> brand-spankin'-new subsidiary office 14 floors below us: SSH is very
> nice, but any big file transfers (sftp, http, ftp, cifs,*anything*
> biggish) will run well only for the first 10 seconds or so, before
> slowing to a crawl (and even managed to make WinSCP complaining of 'no
> response for 15 seconds'). But the ping's have no dropped packets at
> all.
With respect to this particular syndrome, I have found the approach
described here to be extraordinarily effective:-
http://blog.edseek.com/~jasonb/articles/traffic_shaping/scenarios.html
At the time of writing, the link appears to be down but you should able
to access it via Google's cache.
Also, check out the tosfix() function in FireHOL, which demonstrates the
above implementation (and happens to be the best iptables wrapper,
imho). There's an ebuild in portage but I would advise that you
supplement it by grabbing the latest instance of the "firehol.sh" script
from upstream CVS.
Cheers,
--Kerin
next prev parent reply other threads:[~2012-01-16 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 0:58 [gentoo-server] Relatively recent guide on TCP congestion-avoidance algo's & traffic shaping Pandu Poluan
2012-01-16 19:10 ` Kerin Millar [this message]
2012-01-17 15:16 ` [gentoo-server] " David
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='jf1snf$5uu$1@dough.gmane.org' \
--to=kerframil@gmail.com \
--cc=gentoo-server@lists.gentoo.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