From: N N Ashok <nalkunda@cse.msu.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Test tool - traffic generator.
Date: Tue, 25 Feb 2003 20:55:44 +0000 [thread overview]
Message-ID: <marc-lartc-104620668328151@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104575612007959@msgid-missing>
On Friday 21 February 2003 08:16, Emmanuel Guiton wrote:
> >mgen. UDP only, though.
> >
> >http://manimac.itd.nrl.navy.mil/MGEN/
>
> Well, as Stef said, anyway that's why I need (because UDP won't ask for
> replies)
> However, the problem I encountered with MGEN is that it does not accept
> to blindly send udp packets: it first try to resolve the address of the
> remote station (which in my case does not exist).
> As I was away, I've just started again to look seriously at the problem
> so I still have to try Bartek and Ashok solutions.
> Up to know, I've discarded:
> - linux's kernel traffic generator: it bypasses traffic control
> - ttcp because TCP does not suit in my case
> - tg: because of an installation error :) Too lazy to even check in
> the documentation if it worths tring to install it.
> - mgen: as I said above, it doesn't accept to blindly sens udp
> packets but first try to resolve the remote address
> - ping -f: flooding is ok, but I cannot modify parameters (ports,
> adresses) as I'd like to (well, I could start many pings with different
> parameters at once) and it needs acknowledgements.
>
> And I still have to try:
> - udpgen: I have to modify the makefile to install it
> - hping2
> - spak
>
> Tahnk you guys anyway.
> By the way, Ashok you may find something that fits your needs in that list.
>
>
> Emmanuel
>
Thanks to all who gave pointers. However none of these tools accept a network
address for target. So I have to execute the programs once for each target
address. I wanted to check the multipath routing code and so required that
the packets have different destination IP addresses. So I wrote a small
program to generate packets to a range of addresses.
Thanks again,
Ashok
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-02-25 20:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 15:47 [LARTC] Test tool - traffic generator Emmanuel Guiton
2003-02-20 16:40 ` Emmanuel Guiton
2003-02-20 17:36 ` Stef Coene
2003-02-20 20:44 ` Bartek Krajnik
2003-02-20 22:02 ` N N Ashok
2003-02-20 22:11 ` N N Ashok
2003-02-21 12:39 ` Mathieu Deziel
2003-02-21 13:16 ` Emmanuel Guiton
2003-02-21 14:10 ` David Boreham
2003-02-21 14:31 ` Emmanuel Guiton
2003-02-21 15:34 ` David Boreham
2003-02-21 15:59 ` Emmanuel Guiton
2003-02-21 16:16 ` David Boreham
2003-02-21 16:29 ` Martin A. Brown
2003-02-21 16:36 ` Emmanuel Guiton
2003-02-25 20:55 ` N N Ashok [this message]
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-104620668328151@msgid-missing \
--to=nalkunda@cse.msu.edu \
--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.