| To: | "David S. Miller" <davem@xxxxxxxxxx> |
|---|---|
| Subject: | Re: network delay simulation |
| From: | Andrew Morton <akpm@xxxxxxxx> |
| Date: | Wed, 17 Mar 2004 19:17:16 -0800 |
| Cc: | ak@xxxxxxx, shemminger@xxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20040316175052.556d5c22.davem@redhat.com> |
| References: | <20040316151058.3cc2fa28@dell_ss3.pdx.osdl.net> <20040317000048.10d9f52c.ak@suse.de> <20040316175052.556d5c22.davem@redhat.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
"David S. Miller" <davem@xxxxxxxxxx> wrote: > > On Wed, 17 Mar 2004 00:00:48 +0100 > Andi Kleen <ak@xxxxxxx> 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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] 2.6.5-rc1-bk2 loopback.c, Jeff Garzik |
|---|---|
| Next by Date: | Re: [PATCH] prism54 tree sync update, Luis R. Rodriguez |
| Previous by Thread: | Re: network delay simulation, Andi Kleen |
| Next by Thread: | Re: network delay simulation, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |