--- a/doc/anytun.8.txt +++ b/doc/anytun.8.txt @@ -109,7 +109,7 @@ packets. In case of anycast tunnel endpoints, the anycast IP has to be used. In case of unicast endpoints, the address is usually derived correctly from the routing - table. The default is to not use a special inteface and just + table. The default is to not use a special interface and just bind on all interfaces. *-p, --port ''*:: @@ -145,7 +145,7 @@ of multiple anycast hosts. The unicast IP address of the anycast host can be used here. This is needed for communication with the other anycast hosts. The default is to - not use a special inteface and just bind on all interfaces. However + not use a special interface and just bind on all interfaces. However this is only the case if synchronisation is active see *--sync-port*. *-S, --sync-port ''*:: @@ -210,7 +210,7 @@ the multiplex id to use. default: 0 *-s, --sender-id ''*:: - Each anycast tunnel endpoint needs a uniqe sender id + Each anycast tunnel endpoint needs a unique sender id (1, 2, 3, ...). It is needed to distinguish the senders in case of replay attacks. This option can be ignored on unicast endpoints. default: 0 --- a/doc/anytun.8 +++ b/doc/anytun.8 @@ -150,7 +150,7 @@ .PP \fB\-i, \-\-interface \fR\fB\fI\fR\fR .RS 4 -This IP address is used as the sender address for outgoing packets\&. In case of anycast tunnel endpoints, the anycast IP has to be used\&. In case of unicast endpoints, the address is usually derived correctly from the routing table\&. The default is to not use a special inteface and just bind on all interfaces\&. +This IP address is used as the sender address for outgoing packets\&. In case of anycast tunnel endpoints, the anycast IP has to be used\&. In case of unicast endpoints, the address is usually derived correctly from the routing table\&. The default is to not use a special interface and just bind on all interfaces\&. .RE .PP \fB\-p, \-\-port \fR\fB\fI\fR\fR @@ -182,7 +182,7 @@ .RS 4 local unicast(sync) ip address to bind to -This option is only needed for tunnel endpoints consisting of multiple anycast hosts\&. The unicast IP address of the anycast host can be used here\&. This is needed for communication with the other anycast hosts\&. The default is to not use a special inteface and just bind on all interfaces\&. However this is only the case if synchronisation is active see +This option is only needed for tunnel endpoints consisting of multiple anycast hosts\&. The unicast IP address of the anycast host can be used here\&. This is needed for communication with the other anycast hosts\&. The default is to not use a special interface and just bind on all interfaces\&. However this is only the case if synchronisation is active see \fB\-\-sync\-port\fR\&. .RE .PP @@ -255,7 +255,7 @@ .PP \fB\-s, \-\-sender\-id \fR\fB\fI\fR\fR .RS 4 -Each anycast tunnel endpoint needs a uniqe sender id (1, 2, 3, \&...)\&. It is needed to distinguish the senders in case of replay attacks\&. This option can be ignored on unicast endpoints\&. default: 0 +Each anycast tunnel endpoint needs a unique sender id (1, 2, 3, \&...)\&. It is needed to distinguish the senders in case of replay attacks\&. This option can be ignored on unicast endpoints\&. default: 0 .RE .PP \fB\-w, \-\-window\-size \fR\fB\fI\fR\fR