like i said in my earlier post you need to set the password when you start iodined (-P be sure to use upercase P)or you get the error that you describe
and to set your acount on gadaddy if my memorry is right you need to enter the advenced mode to set your record manually
ok i got everything working. my next question would be.
after i get a connection from the dns tunnel.. how do i to ssh into my router what ip would i use??
do i use the dns tunnel server ip which is 10.0.0.1
or my home wan ip ?
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\user>"C:\Documents and Settings\user\Desktop\iodine-wi
ndow\iodine-0.5.1-win32\bin\iodine.exe" -f tunnel.guardianx.info
Enter password:
Opening device \\.\Global\{276E0EF8-832C-4422-8438-B83FE0B89205}.tap
Opened UDP socket
Opened UDP socket
Opened UDP socket
Version ok, both using protocol v 0x00000500. You are user #0
Enabling interface 'dns'
Setting IP of interface 'dns' to 10.0.0.2 (can take a few seconds)...
Ok.
Switching to Base64 codec
Server switched to codec Base64
Autoprobing max downstream fragment size... (skip with -m fragsize)
768 ok.. 1152 ok.. ...1344 not ok.. ...1248 not ok.. ...1200 not ok.. 1176 ok..
1188 ok.. will use 1188
Setting downstream fragment size to max 1188...
Sending queries for tunnel.guardianx.info to 207.69.188.185
Got SERVFAIL as reply
Got SERVFAIL as reply
Got SERVFAIL as reply
Got SERVFAIL as reply
i have no idea what is going on.
ok this is my output from the client side..
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\user>"C:\Documents and Settings\user\Desktop\iodine-wi
ndow\iodine-0.5.1-win32\bin\iodine.exe" -f tunnel.guardianx.info
Enter password:
Opening device \\.\Global\{06CA2A66-D965-4EB2-B864-C27C5DA32B0E}.tap
Opened UDP socket
Opened UDP socket
Opened UDP socket
Version ok, both using protocol v 0x00000500. You are user #0
Enabling interface 'dns'
Setting IP of interface 'dns' to 10.0.0.2 (can take a few seconds)...
Ok.
Switching to Base64 codec
Server switched to codec Base64
Autoprobing max downstream fragment size... (skip with -m fragsize)
768 ok.. 1152 ok.. ...1344 not ok.. ...1248 not ok.. ...1200 not ok.. 1176 ok..
1188 ok.. will use 1188
Setting downstream fragment size to max 1188...
Sending queries for tunnel.guardianx.info to 207.69.188.185
Got SERVFAIL as reply
but when i try to ping the server on the client with
ping 10.0.0.1 . i get no respond. that is werid because at the start it state that both version have using the same protocall and yet i cant ping the idodine tunnel..
my private network ip is 192.168.1.0 i'm not sure if this is program bug or what i did on my part.
my firewall is deactivated on my router maybe its source of your problem. Try to deactivate it and tell me if this solve your problem
u are right about the firewall after disabling the firewall i could ping the server and everything work.
does anyone know a way to allow the dns server to work without disable the firewall completely. how would i allow the firewall to fwd the ip between the dns server and the client without completely disabling the firewall
personnaly the firewall is not very usefull my isp block all the important port and i cant do nothing about it so disable it. But by miracle the port 53 is open so i can use iodine
Here's a cross-compile of iodine 0.6.0-rc1. For memory usage sake, it's been compiled with #define USERS 1 (check iodine's README), so it only supports one connection at a time. It's working perfectly on my WRT320N/E2000 (eko 14974 big).
My startup script (I'm using jffs):
Code:
if [ x`ps | grep "iodined" | grep -v grep` == "x" ]
then
export EXTIP=`wget -q http://checkip.dyndns.com/ -O- | sed '/^.*IP Address: /s/.* \(\([0-9.]\{1,4\}\)\{4\}\).*/\1/'`
/jffs/iodined -P <password> -n $EXTIP 10.0.123.1 <dns server name>
fi
I'm setting my external IP explicitly although I'm not sure it is really needed.
For those asking on how to disable DNSMasq:
- under Setup > Basic Setup, disable "Use DNSMasq for DHCP" + "Use DNSMasq for DNS"
- under Services > Services > DNSMasq - Disable
There's no need for the full stop if you're using something like freedns.afraid.org to setup your NS entry. Just set a new NS entry pointing to your A domain. Wait for a bit (it may take 1 day for the new NS entry to propagate) and it should work.