From: david@lang.hm
To: Dave Taht <dave.taht@gmail.com>
Cc: Stephen Walker <stephendwalker@gmail.com>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Next release plan (sugarland-2)
Date: Wed, 3 Oct 2012 23:58:36 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1210032355500.10082@asgard.lang.hm> (raw)
In-Reply-To: <CAA93jw4eVBdW55-soOR2KNjsRi6LkkNtzLJO3ZXXzv8oCya7qw@mail.gmail.com>
On Wed, 3 Oct 2012, Dave Taht wrote:
> Fiddling with qos effectively however requires I get some netem boxes
> up to simulate long RTTs. While I have got the vyatta boxes to do so,
> they are short on documentation, and I haven't even got a console
> prompt out of them yet. Might acquire more/different boxes. Might get
> the time and bum the hw to slam a video card into them to get them
> updated. Don't know yet.
can you setup a linux box with the iptables delay module as a router
between your nodes to go this?
David Lang
next prev parent reply other threads:[~2012-10-04 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 1:18 Dave Taht
2012-10-04 6:58 ` david [this message]
2012-10-04 15:38 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1210032355500.10082@asgard.lang.hm \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=stephendwalker@gmail.com \
/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