summaryrefslogtreecommitdiff
path: root/curvetun.8
diff options
context:
space:
mode:
authorKartik Mistry <kartik@debian.org>2013-05-30 12:05:37 +0530
committerDaniel Borkmann <dborkman@redhat.com>2013-05-30 09:56:55 +0200
commite146460e755773534ac13a9fa88e1d963fcee4cc (patch)
treeeb7aeb1837b93635fdda66df7a74118936d3a67e /curvetun.8
parent7bac55be33621dc5a382c8bd518d8120098c6cde (diff)
man: manpages hyphen and spelling mistakes
Some fixes all over, part 1. Signed-off-by: Kartik Mistry <kartik@debian.org> Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Diffstat (limited to 'curvetun.8')
-rw-r--r--curvetun.820
1 files changed, 10 insertions, 10 deletions
diff --git a/curvetun.8 b/curvetun.8
index b95d9e9..37da371 100644
--- a/curvetun.8
+++ b/curvetun.8
@@ -63,7 +63,7 @@ mandatory. This option is for servers only.
.SS -t <server>, --stun <server>
If needed, this options enables an STUN lookup in order to show public IP/port
mapping and to punch a hole into the firewall. In case you are unsure what STUN
-server to use, simply use ``--stun stunserver.org''.
+server to use, simply use ``\-\-stun stunserver.org''.
.PP
.SS -c[=alias], --client[=alias]
Starts curvetun in client mode and connects to the given connection alias that is
@@ -260,7 +260,7 @@ the admin then adds this entry into his ``clients'' file like:
.PP
The server admin can check, if the server has registered it properly by
.PP
- server$ curvetun -C
+ server$ curvetun \-C
.PP
which prints all parsed clients from ``~/.curvetun/clients''. This process could
easily be automated/scripted with f.e. Perl and LDAP.
@@ -271,13 +271,13 @@ the server.
.PP
We assume in this example that the tunnel server has a public IP i.e. 1.2.3.4,
runs on port 6666 and uses UDP as a carrier protocol. In case you are behind
-a NAT, you can use curvetun's ``--stun'' option for starting the server, to
+a NAT, you can use curvetun's ``\-\-stun'' option for starting the server, to
obtain your mapping. However, in this example we continue with 1.2.3.4 and 6666,
UDP.
.PP
First, the server needs to export its key to the client, as
.PP
- server$ curvetun -x
+ server$ curvetun \-x
.PP
where it prints sth like:
.PP
@@ -296,17 +296,17 @@ in the config like
.PP
where the client can check its config via:
.PP
- client$ curvetun -S
+ client$ curvetun \-S
.PP
Okay, assuming we've made it, then we start the server with:
.PP
- server$ curvetun -s -p 6666 -u
+ server$ curvetun \-s \-p 6666 \-u
server# ifconfig curves0 up
server# ifconfig curves0 10.0.0.1/24
.PP
Then, we start the client with:
.PP
- client$ curvetun -c=myfirstserver
+ client$ curvetun \-c=myfirstserver
client# ifconfig curvec0 up
client# ifconfig curvec0 10.0.0.2/24
.PP
@@ -323,9 +323,9 @@ Server side's public IP on eth0 is i.e. 1.2.3.4:
server# ifconfig curves0 up
server# ifconfig curves0 10.0.0.1/24
server# echo 1 > /proc/sys/net/ipv4/ip_forward
- server# iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
- server# iptables -A FORWARD -i eth0 -o curves0 -m state --state RELATED,ESTABLISHED -j ACCEPT
- server# iptables -A FORWARD -i curves0 -o eth0 -j ACCEPT
+ server# iptables \-t nat \-A POSTROUTING \-o eth0 \-j MASQUERADE
+ server# iptables \-A FORWARD \-i eth0 \-o curves0 \-m state \-\-state RELATED,ESTABLISHED \-j ACCEPT
+ server# iptables \-A FORWARD \-i curves0 \-o eth0 \-j ACCEPT
.PP
Client side's IP on eth0 is i.e. 5.6.7.8:
.PP