Tips and tricks

Running together with BIND9

iodined must be started with "-p 5353" since 53/udp is used by BIND

and BIND must be configured to forward requests:

zone "i.xxx.yyy" {
 type forward;
 forwarders{
  127.0.0.1 port 5353;
 };
};

If this doesn't immediately work, you may need to enable recursive DNS queries.

In the Debian lenny version of bind9, you can do this by editing the "options{}" section of /etc/bind/named.conf.options. Insert into that section the line

allow-recursion { any; };

Running on another port

If your port 53 is taken on a specific interface by an application that does not use it, use -p on iodined to specify an alternate port (like -p 5353) and use for instance iptables (on Linux) to forward the traffic:

iptables -t nat -A PREROUTING -i eth0 -p udp --dport 53 -j DNAT --to :5353

(Sent in by Tom Schouten)

Routing script for OS X, Linux and FreeBSD

 http://www.doeshosting.com/code/NStun.sh
(by krzee)

iodine-jigger script from the debian package

 http://svn.toastfreeware.priv.at/wsvn/ToastfreewareDebian/iodine/trunk/debian/iodine-jigger

Routing script for WIN32

It's a shell script. You need  Unix Tools, and to set the path environnement variable. (Note, the script seems to be made for french version of Windows, you may need to adjust the strings)
To launch it, use the command "sh iodine.sh" . If you got a problem, launch with the command "sh -xv iodine.sh", and we will be able to help you on irc!
The server must have the "-c" option.
After closing the tunnel, you can restore routes with theses commands "ipconfig /release" + "ipconfig /renew".

iodine.sh :

DOMAIN=mytunnel.mydomain.com
PASSWORD=XXXXX

PATH="$PATH;./"
IODINE=`which iodine.exe`
GREP=`which grep`
CUT=`which cut`
RT=`which route`
IPCONFIG=`which ipconfig`
GATEWAY=`$IPCONFIG /all | grep "Passerelle" | cut -d ":" -f2`
DNS=`$IPCONFIG /all | grep "Serveurs DNS" | cut -d ":" -f2`

$RT delete 0.0.0.0
#$RT add $DNS MASK 255.255.255.255 $GATEWAY
$RT add $DNS $GATEWAY

$IODINE -fP $PASSWORD $DNS $DOMAIN