From: Neal Cardwell <ncardwell@google.com>
To: Netdev <netdev@vger.kernel.org>
Subject: packetdrill: a scriptable network stack testing tool
Date: Tue, 2 Jul 2013 13:21:53 -0700 [thread overview]
Message-ID: <CADVnQymNus-PXFpZQf3tsiGNeqUATgvOSRcVUMiUPsAzfA7WHQ@mail.gmail.com> (raw)
I'd like to announce the availability of the packetdrill network stack
testing tool.
The packetdrill scripting tool enables users to quickly write precise
tests for entire TCP/UDP/IPv4/IPv6 network stacks, from the system
call layer down to the NIC hardware. packetdrill currently works on
Linux, FreeBSD, OpenBSD, and NetBSD. It can test network stack
behavior over physical NICs on a LAN, or on a single machine using a
tun virtual network device.
The code is licensed under version 2 of the GPL, and available in a
git repository at:
https://code.google.com/p/packetdrill/
Here's a USENIX 2013 paper about the tool:
http://research.google.com/pubs/pub41316.html
This paper describes the design and implementation of the tool, and
our experiences using it to execute 657 test cases. The tool was
instrumental in our development of three new features for Linux
TCP—Early Retransmit, Fast Open, and Loss Probes—and allowed us to
find and fix 10 bugs in Linux. Our team uses packetdrill in all phases
of the development process.
Currently the source for the testing tool is in the git repository,
along with an example script for each supported OS. We will also be
posting tests from our team's Linux TCP test suite (described in the
paper), as time permits.
There is a mailing list for questions, discussions and patches:
http://groups.google.com/group/packetdrill
Enjoy!
neal
reply other threads:[~2013-07-02 20:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CADVnQymNus-PXFpZQf3tsiGNeqUATgvOSRcVUMiUPsAzfA7WHQ@mail.gmail.com \
--to=ncardwell@google.com \
--cc=netdev@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 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).