From: Andy Furniss <lists@andyfurniss.entadsl.com>
To: Tommy W <tommy@svearike.sytes.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: Simulating a "bad" connection.
Date: Sat, 05 May 2007 20:07:28 +0100 [thread overview]
Message-ID: <463CD5F0.8090904@andyfurniss.entadsl.com> (raw)
In-Reply-To: <200705042201.21985.tommy@svearike.sytes.net>
Tommy W wrote:
> Hi,
> I was just wondering if someone knows of a good way to simulate a "bad"
> network?.
> I want high latency AND/OR high packet loss.
>
> I was thinking along the lines
> iptables -I INPUT -m random --average 90 -j DROP
>
> but then I get libipt_random.so doesn't exist.
> I see that it is not included, how do you get it ?
>
> kernel: 2.6.16-rc5
> iptables: 1.3.4
>
> or is there some other more simple solution?
>
> Thanks in advance
> /Tommy
>
>
http://linux-net.osdl.org/index.php/Netem
Is in kernel.
Andy.
next prev parent reply other threads:[~2007-05-05 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 20:01 Simulating a "bad" connection Tommy W
2007-05-04 21:11 ` Jan Engelhardt
2007-05-04 21:42 ` Tommy W
2007-05-04 21:55 ` Pascal Hambourg
2007-05-04 21:58 ` Pascal Hambourg
2007-05-05 19:07 ` Andy Furniss [this message]
2007-05-06 11:00 ` Tommy W
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=463CD5F0.8090904@andyfurniss.entadsl.com \
--to=lists@andyfurniss.entadsl.com \
--cc=netfilter@lists.netfilter.org \
--cc=tommy@svearike.sytes.net \
/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.