Page MenuHomeFreeBSD

Add random source/destination address generation to pkt-gen.
ClosedPublic

Authored by adrian on Apr 17 2015, 1:56 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Sep 18, 11:27 AM
Unknown Object (File)
Sep 10 2025, 2:14 PM
Unknown Object (File)
Aug 31 2025, 9:03 PM
Unknown Object (File)
Aug 6 2025, 5:42 AM
Unknown Object (File)
Jul 25 2025, 3:46 PM
Unknown Object (File)
Jul 4 2025, 3:22 AM
Unknown Object (File)
Jun 22 2025, 1:44 AM
Unknown Object (File)
Jun 10 2025, 2:57 AM

Details

Reviewers
hiren
gnn
Group Reviewers
network
Summary

It's hard to test hash distribution testing when pkt-gen only walks
IP ranges. This adds IPv4 source/destination randomization.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

adrian retitled this revision from to Add random source/destination address generation to pkt-gen..
adrian updated this object.
adrian edited the test plan for this revision. (Show Details)
adrian added a reviewer: network.
hiren added a reviewer: hiren.
hiren added a subscriber: hiren.

There seem to be a bunch of whitespace changes. Other than that, looks good to me.

Try to run this by luigi as he maintains this code upstream also.

tools/tools/netmap/pkt-gen.c
584

Are these all whitespace changes or something funky that phabricator is doing?

This revision is now accepted and ready to land.Apr 17 2015, 7:01 AM
gnn added a reviewer: gnn.
gnn added a subscriber: gnn.

Do it.

Is this going to be committed?

Appears to have landed, didn't close. Assuming we're done.

commit 56717743f2320dd8a13bdcc4f8decddbf1703bd1
Author: Adrian Chadd <adrian@FreeBSD.org>
Date: Sun Apr 19 17:07:51 2015 +0000

Update pkt-gen to optionally use randomised source/destination
IPv4 addresses/ports.

When doing traffic testing of actual code that /does/ things to the
packet (rather than say, 'bridge.c'), it's typically a good idea to
use a variety of cache-busting and flow-tracking-busting packet
spreads.  The pkt-gen method of testing an IP range was to walk
it linearly - which is fine, but not useful enough.

This can be used to completely randomize the source/destination
addresses (eg to test out flow-tracking-busting) and to keep the
destination fixed whilst randomising the source (eg to test out
what a DDoS may look like.)

Tested:

* Intel ixgbe 10G (82599) netmap

Differential Revision:  https://reviews.freebsd.org/D2309
MFC after:      2 weeks
Sponsored by:   Norse Corp, Inc.

Notes:

svn path=/head/; revision=281746