astraceroute: double line break after no success with -Z

Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
astraceroute: short sleep after each probe

Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
astraceroute: refactoring and improvements in ui

Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
csum: move p4_csum into csum.h

Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
curvetun: Added error reporting for mal-formed tcp/udp carrier types

I personally had mis-spelled udp (upd) and found myself diving into source
to determine why tcp was repeatedly being used instead of udp.

I'm uncertain whether the general lack of error checking and reporting
is intentional, or simply due to the very large task of getting the tools
up and running.

Further, if error checking is to be done on parameters and inputs, I'm
personally uneducated on the best method for reporting them.  I assumed
syslog(), as that is used frequently in setup/teardown messaging for
curvetun.  Is the inclusion of syslog.h reasonable here?
Merge pull request #53 from electronjoe/curvetun-udp-tcp-server-spec-check

curvetun: Added error reporting for mal-formed tcp/udp carrier types
Merge branch 'master' of github.com:borkmann/netsniff-ng
xio: redirect stdout, stderr to syslog in daemon mode

Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
xio: minor: rename variable

Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Improved error reporting in xio

How portable is strerror? Assuming it is... This patch provides more robust
failure mode reporting in xio.

Pre patch:
curvetun[15819]: ioctl screwed up!

Post patch:
curvetun[15819]: ioctl screwed up! Operation not permitted.
Corrected spinning loop potential in getrandombytes

Client was unable to start due to repeated loop execution.

Successful file descriptor opening of /dev/urandom had no
impact on loop execution, preventing the client from moving on.

Signed-off-by: Scott Moeller <electronjoe@gmail.com>
docs: add Scott to authors

Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
curvetun: Fied client initial message padding randomization

secrand() returns a signed integer, which was being taken modulo
200 and used as a padding amount for the connection initialization.

When the result was negative this resulted in a negative padding
amount, which subsequently caused segmentation fault during memset.

Signed-off-by: Scott Moeller <electronjoe@gmail.com>
xio: secrand: test for -1

Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
trafgen: simplify built-in example

Signed-off-by: Daniel Borkmann <dborkman@redhat.com>