This directory contains some files useful for ad-hoc tests.
With these it is possible to run a test of secnet on a Linux host
even if that Linux host does not have another working network connection.

The keys here are (obviously) public.  They were generated like this:
 ssh-keygen -C inside@example.com -f test-example/inside.key -t rsa1 -b 1024
 ssh-keygen -C outside@example.com -f test-example/outside.key -t rsa1 -b 1024
 # edit sites to paste {inside,outside}.key.pub into pubkey lines
 base64 <inside.key >inside.key.b64
 base64 <outside.key >outside.key.b64

To run the test:
 Run the makefile:
  make -C test-example/
 In one window, as root
  ./secnet -dvnc test-example/inside.conf
 And in another
  ./secnet -dvnc test-example/outside.conf
 Then in a third
  ping -I secnet-test-i 172.18.232.2 
 
For running under valgrind memcheck, do something like this:
  valgrind --num-callers=40 --gen-suppressions=yes --db-attach=yes \
    --leak-check=full --suppressions=test-example/memcheck.suppressions \
    ./secnet -dvnc test-example/outside.conf
NB that --num-callers is needed as secnet's stack can be deep.

The config file outside-unshare.conf can be used on Linux in
conjunction with test-example/fake-userv and a built checkout of
userv-utils.git to run the "outside" copy of secnet in a new "network
namespace".