From f47c750c98900cddd593407d52e9afc3a6328111 Mon Sep 17 00:00:00 2001 From: Erik Ekman Date: Sat, 1 Dec 2007 10:16:19 +0000 Subject: [PATCH] Escape dashes in man page --- man/iodine.8 | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/man/iodine.8 b/man/iodine.8 index 3720a50..1289191 100644 --- a/man/iodine.8 +++ b/man/iodine.8 @@ -124,13 +124,13 @@ the same on both the client and the server. .TP Try it out within your own LAN! Follow these simple steps: .TP -- On your server, run: ./iodined -f 10.0.0.1 test.asdf +- On your server, run: ./iodined \-f 10.0.0.1 test.asdf (If you already use the 10.0.0.0 network, use another internal net like 172.16.0.0) .TP - Enter a password .TP -- On the client, run: ./iodine -f 192.168.0.1 test.asdf +- On the client, run: ./iodine \-f 192.168.0.1 test.asdf (Replace 192.168.0.1 with the server's ip address) .TP - Enter the same password @@ -160,10 +160,10 @@ tunnel1 IN NS tunnel1host.mytunnel.com. Now any DNS querys for domains ending with tunnel1.mytunnnel.com will be sent to your server. Start iodined on the server. The first argument is the tunnel IP address (like 192.168.99.1) and the second is the assigned domain (in this -case tunnel1.mytunnel.com). The -f argument will keep iodined running in the +case tunnel1.mytunnel.com). The \-f argument will keep iodined running in the foreground, which helps when testing. iodined will start a virtual interface, and also start listening for DNS queries on UDP port 53. Either enter a -password on the commandline (-P pass) or after the server has started. Now +password on the commandline (\-P pass) or after the server has started. Now everything is ready for the client. .TP .B Client side: