[WireGuard] fq, ecn, etc with wireguard

Dave Taht dave.taht at gmail.com
Mon Aug 29 23:11:16 CEST 2016

well, you should see ect(3) if you pound the network interface. Things
like tcp small queues get in the way so you won't see it with a simple
single flow test against cake/codel/etc.

something like 4 netperfs will do it.

Since you are so fast at getting code running, I think you'll like
flent as a test tool. It's pretty easy to install:

sudo apt-get install python-matplotlib python-qt4 netperf fping # some
distros don't include netperf tho

# you only need netperf's netserver running on the clients

git clone https://github.com/tohojo/flent.git

cd flent; sudo make install
netserver -N # wherever you have targets

It has a zillion tests, lets you plot the results, over time, etc,
etc. The rrul test, in particular, would be a good stress test of your
code. You can see usage of flent (formerly known as netperf-wrapper)
all over the web now....

example test script (with a title of what I'm testing now)


for i in 1 2 4 8 12 16 24;
flent -t "unencrypted-ht40-$i-flows-osx-ether" -H -l 30
--test-parameter=upload_streams=$i tcp_nup
flent -t "unencrypted-ht40-$i-flows-osx-ether" -H -l 30
--test-parameter=download_streams=$i tcp_ndown

flent -t "unencrypted-ht40-$i-flows-osx-ether" -H -l 30 rrul_be
flent -t "unencrypted-ht40-$i-flows-osx-ether" -H -l 30 rrul

flent-gui *.gz

# Anyway, I'll join you in irc to look over what you doing.....

More information about the WireGuard mailing list