haskal
/
iodine
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

updated manpage

This commit is contained in:
Erik Ekman 2009-01-10 20:53:09 +00:00 committed by Erik Ekman
parent 8906264a0a
commit b5eda882a1
1 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
man/iodine.8
View File

@ -11,6 +11,8 @@ iodine, iodined \- tunnel IPv4 over DNS
.I user .I user
.B ] [-P .B ] [-P
.I password .I password
.B ] [-m
.I fragsize
.B ] [-t .B ] [-t
.I chrootdir .I chrootdir
.B ] [-d .B ] [-d
@ -85,6 +87,11 @@ and otherwise tunX.
Use 'password' to authenticate. If not used, Use 'password' to authenticate. If not used,
.B stdin .B stdin
will be used as input. Only the first 32 characters will be used. will be used as input. Only the first 32 characters will be used.
.SS Client Options:
.TP
.B -m fragsize
Maximum downstream fragsize. Not setting this will cause the client to probe
the maximum accepted downstream packet size.
.SS Server Options: .SS Server Options:
.TP .TP
.B -c .B -c
@ -214,10 +221,8 @@ replace the default gateway with the servers IP address within the DNS tunnel,
and configure the server to do NAT. and configure the server to do NAT.
.TP .TP
.B MTU issues: .B MTU issues:
Some relaying DNS servers enforce a 512 byte packet limit. All larger packets are These issues should be solved now, with automatic fragmentation of downstream
simply dropped. If you can ping through the tunnel but not login via SSH, this is packets. There should be no need to set the MTU explicitly on the server.
most likely the case. Set the MTU on the server to 220 to ensure that all packets
are less than 512 bytes. This will however greatly affect performance.
.SH BUGS .SH BUGS
File bugs at http://dev.kryo.se/iodine/ File bugs at http://dev.kryo.se/iodine/
.SH AUTHORS .SH AUTHORS