From: Patrick Turley <pturley@rocksteady.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Testing traffic control
Date: Fri, 25 Apr 2003 21:57:03 +0000 [thread overview]
Message-ID: <marc-lartc-105130762206276@msgid-missing> (raw)
We are just starting to research this stuff - I expect this mailing list
to save my bacon many times :)
I'd like to hear some ideas on how people test their setups. It seems to
me that the ideal testing rig would be two computers, one on either side
the router. Have one computer open up some number of connections with
various procol characteristics to the other and start blasting data
through each connection. Have the other computer display the rate at
which data is being received for each connection in a really cool
graphical way.
Does anyone here actually have the tools to do this? I would be terribly
grateful if anyone could point me in the right direction.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-04-25 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 21:57 Patrick Turley [this message]
2003-04-25 22:51 ` [LARTC] Testing traffic control Stef Coene
2003-04-26 7:53 ` Stef Coene
2003-04-26 15:52 ` sufcrusher
2003-05-10 12:41 ` Srikanth
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-105130762206276@msgid-missing \
--to=pturley@rocksteady.com \
--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.