From f329c57d9e76983759bb47da16dd3204e0accbc8 Mon Sep 17 00:00:00 2001 From: Christian Pointner Date: Mon, 10 Feb 2014 21:40:21 +0000 Subject: fixed typos at manpage --- doc/uanytun.8.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'doc/uanytun.8.txt') diff --git a/doc/uanytun.8.txt b/doc/uanytun.8.txt index 5bb236f..2a47318 100644 --- a/doc/uanytun.8.txt +++ b/doc/uanytun.8.txt @@ -257,6 +257,7 @@ passed to the daemon: The number of bytes to use for the auth tag. This value defaults to 10 bytes unless the 'null' auth algo is used in which case it defaults to 0. + RAIL ---- @@ -266,7 +267,7 @@ UDP packets over multiple physical links. More precisly for each packet *uAnytun reads, from the TUN/TAP device, it will send out multiple UDP packets. All of those to the same host but with different destination ports. Using policy-based routing mechanisms these packets can now be seperated and sent out on several interfaces. -The server-side will then pick the first of the packets that arrives and discards all others. +The server-side will then pick the first of the packets that arrive and discards all others. For this to work the size of the sequence window (*-w*) must not be set to 0. As soon as the server-side learns the remote endpoints of all or some of the links it will as well send multiple UDP packets for each payload packet. @@ -281,12 +282,12 @@ P2P Setup between two unicast enpoints: Host A: ^^^^^^^ -uanytun -r hostb.example.com -t tun -n 192.168.123.1/30 -c aes-ctr-256 -k aes-ctr-256 \ +uanytun -r hostb.example.com -t tun -n 192.168.123.1/30 -c aes-ctr-256 -k aes-ctr-256 -E have_a_very_safe_and_productive_day -e left Host B: ^^^^^^^ -uanytun -r hosta.example.com -t tun -n 192.168.123.2/30 -c aes-ctr-256 -k aes-ctr-256 \ +uanytun -r hosta.example.com -t tun -n 192.168.123.2/30 -c aes-ctr-256 -k aes-ctr-256 -E have_a_very_safe_and_productive_day -e right One unicast and one anycast tunnel endpoint: -- cgit v1.2.3