From: Roman Chertov <rchertov@purdue.edu>
To: Jeff Gercken <JeffG@kizan.com>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] Introducing latency
Date: Wed, 04 May 2005 13:38:14 -0500 [thread overview]
Message-ID: <42791696.7090106@purdue.edu> (raw)
In-Reply-To: <EDF30175FE4D804B83444FB153172A50509A4D@louexch.KiZAN.net>
Jeff Gercken wrote:
> Does anyone know how I might introduce latency on the packets that I
> bridge? I'm trying to develop a system for simulating wan links and
> often bandwidth isn't as big an issue as delay, especially when talking
> wireless (dot11 or satellite).
You can use the dummynet of the ipfw in FreeBSD to add delays/link
limitations/loss. You can also create a bridge with ipfw as well. I am
not sure what Linux has for traffic shaping.
Roman
>
> Thanks,
> jeff
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> http://lists.osdl.org/mailman/listinfo/bridge
next prev parent reply other threads:[~2005-05-04 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 18:07 [Bridge] Introducing latency Jeff Gercken
2005-05-04 18:38 ` Roman Chertov [this message]
2005-05-04 18:53 ` Stephen Hemminger
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=42791696.7090106@purdue.edu \
--to=rchertov@purdue.edu \
--cc=JeffG@kizan.com \
--cc=bridge@lists.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 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.