From: jamal <hadi@cyberus.ca>
To: piet@bluelane.com
Cc: Rajneesh Saini <rksaini@gmail.com>,
piet at work <piet@work.piet.net>, Andi Kleen <ak@suse.de>,
David Miller <davem@davemloft.net>,
Stephen Hemminger <shemminger@osdl.org>,
netdev@vger.kernel.org
Subject: Re: Alternate to Ixia's ANVL test harness for tcp compliance.
Date: Thu, 20 Jul 2006 16:08:49 -0400 [thread overview]
Message-ID: <1153426129.5273.123.camel@jzny2> (raw)
In-Reply-To: <1153424967.8114.450.camel@piet2.bluelane.com>
On Thu, 2006-20-07 at 12:49 -0700, Piet Delaney wrote:
> Hey Gang:
>
> Both at UNM and Bluelane we have used Ixia's ANVL test harness for
> verifying TCP protocol compliance with the RFC's. Recent additions
> to Ixia's ANVL GUI provide a ethereal like GUI. It looks really slick;
> even providing ladder diagrams for quickly viewing the big picture.
>
> Unfortunately Ixia told me they don't have any plains to port the
> new GUI to linux. Instead they are trying to migrate Linux developers,
> us, to using Windows. Yeck!
>
> With Ixia migrating away from Linux I was wondering if we should
> consider using an alternate test bed for TCP protocol compliance.
>
> Do any of you use tools other than ANVL for RFC compliance while
> hacking to the tcp code?
>
Talk to the USAGI folks. They have something similar to ANVL called TAHI
that they use to check compliance in IPV4, IPV6 and IPSEC. It should be
extendable with some effort to do TCP.
> In the unlikely event that there isn't an alternate; is there any
> interest in a netdev group effort to motivate Ixia to porting their C
> sharp code to linux. I get the feeling that come of their developers
> would like to port the code to linux.
Create competition for them - it is the easiest way to get them
motivated.
cheers,
jamal
next prev parent reply other threads:[~2006-07-20 20:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 19:49 Alternate to Ixia's ANVL test harness for tcp compliance Piet Delaney
2006-07-20 20:04 ` Jeff Garzik
2006-07-20 20:24 ` Piet Delaney
2006-07-20 21:17 ` David Miller
2006-07-20 21:31 ` Jeff Garzik
2006-07-20 21:42 ` Piet Delaney
2006-07-20 21:47 ` Brent Cook
2006-07-20 21:56 ` Jeff Garzik
2006-07-20 20:08 ` jamal [this message]
2006-07-20 20:28 ` Andi Kleen
2006-07-20 20:43 ` Tomasz Torcz
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=1153426129.5273.123.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=ak@suse.de \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=piet@bluelane.com \
--cc=piet@work.piet.net \
--cc=rksaini@gmail.com \
--cc=shemminger@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).