From: Andrew Morton <akpm@osdl.org>
To: "David S. Miller" <davem@redhat.com>
Cc: ak@suse.de, shemminger@osdl.org, netdev@oss.sgi.com
Subject: Re: network delay simulation
Date: Wed, 17 Mar 2004 19:17:16 -0800 [thread overview]
Message-ID: <20040317191716.460836b0.akpm@osdl.org> (raw)
In-Reply-To: <20040316175052.556d5c22.davem@redhat.com>
"David S. Miller" <davem@redhat.com> wrote:
>
> On Wed, 17 Mar 2004 00:00:48 +0100
> Andi Kleen <ak@suse.de> wrote:
>
> > iirc there was a 2.4 port of NistNet. Porting it to 2.6 is probably
> > not that much work.
>
> nistnet works, but even akpm remembers it as pretty grotty, who knows
> maybe the most recent 2.4.x variant was much better, but I doubt it.
whaddya mean "even"?
I wrote a userspace thingy many moons ago which provides variable delays
and bandwidth restriction. It's for simulating long, thin pipes. It uses
the tap/tun interface to route packets up to userspace where the
delay/throttling is implemented. It requires weird policy routing rules,
but there are scripts there which set everything up.
http://www.zipworld.com.au/~akpm/linux/patches/stuff/packet-delay.tar.gz
next prev parent reply other threads:[~2004-03-18 3:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 23:10 network delay simulation Stephen Hemminger
2004-03-16 23:00 ` Andi Kleen
2004-03-17 1:50 ` David S. Miller
2004-03-17 2:06 ` Andi Kleen
2004-03-18 3:17 ` Andrew Morton [this message]
2004-03-17 1:41 ` David S. Miller
2004-03-17 15:37 ` John Heffner
2004-03-17 16:09 ` jamal
2004-03-17 17:51 ` David S. Miller
2004-03-17 18:00 ` Stephen Hemminger
2004-03-17 18:25 ` David S. Miller
2004-03-18 20:04 ` [PATCH] packet delay scheduler Stephen Hemminger
2004-03-19 4:53 ` David S. Miller
2004-03-19 18:47 ` Stephen Hemminger
2004-03-23 2:50 ` David S. Miller
2004-03-19 14:52 ` jamal
2004-03-19 22:21 ` David S. Miller
2004-03-22 13:40 ` jamal
2004-03-17 2:40 ` network delay simulation Ben Greear
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=20040317191716.460836b0.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).