All of lore.kernel.org
 help / color / mirror / Atom feed
From: "lartc@manchotnetworks.net" <lartc@manchotnetworks.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Artificial latency
Date: Sun, 08 Jun 2003 09:06:39 +0000	[thread overview]
Message-ID: <marc-lartc-105506327510626@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105502807826973@msgid-missing>

hi ryan,

i had asked a similar question a while back, and stef recommended the
following:


http://snad.ncsl.nist.gov/itg/nistnet


make sure to read the faq!

cheers

charles


On Sun, 2003-06-08 at 01:19, Ryan Agler wrote:
> I have a situation where I would like to introduce an artificial delay of
> 100 milliseconds to incoming UDP traffic to a particular client.  Here is my
> setup:
> 
>                  +-------+          +-----------+
>                  | Linux |          |           |
> 'Internet'---eth1| NAT   |eth0===|192.168.1.4|
>                  |       |          |           |
>                  +-------+          +-----------+
> 
> Note I'm not looking to restrict the RATE or SPEED at all, just to add a
> DELAY, and only to incoming UDP packets coming in from the Internet destined
> for 192.168.1.4.  I have kernel 2.4.20 with all the latest and greatest tc,
> htb patches, etc.
> 
> Can anyone help??
> 
> Thanks much,
> +Ryan
> 
> 
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/






_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-06-08  9:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-07 23:19 [LARTC] Artificial latency Ryan Agler
2003-06-08  9:06 ` lartc [this message]
2003-06-09 20:09 ` Ryan Agler
2003-06-10  6:52 ` lartc

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=marc-lartc-105506327510626@msgid-missing \
    --to=lartc@manchotnetworks.net \
    --cc=lartc@vger.kernel.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 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.