Hi. I also have the nstx daemon on the router but I was not able to compile the client on my Mac, that's why I resorted to iodined. Don't know about Windows, but I guess you're on the same case as me.
Posted: Tue Dec 21, 2010 4:31 Post subject: iodine/nstx/openvpn
Hi
great work compiling iodine buchinho was asking (if his still around) about speeds I have heard of 1mbit+
from iodine and nstx is rumored to be slow
the FASTER option is OpenVpn on udp port 53 perhaps requireing fragmented packets if it "appears blocked" (works great on 4g usa) did not work on uk network 3 when i tested it
so I tryed to set this up and ran in to some issues
as elypter mentioned "Does anyone know how to do dhcp hosting without dnsmasq, or better how iodine works together with dnsmasq."
it is possible to stop dnsmasq listening on all ports using an option --bind-interfaces
how ever this seems to result in dns querys not working any more (i found a better way is a simple port forward)
so i will now try to test iodine
it seems strange nstx some how works (if it does) because udp 53 is in use by dnsmasq maybe brainslayer or someone could explain how that happens?
search-tags: openvpn dns tunnel port 53 captive portal bypass nstx iodine wimax hacking
Posted: Mon Aug 01, 2011 19:35 Post subject: Can not
Presently I’m running Iodine server on my DD-WRT Linux router and connecting to it using the windows client running on Windows Vista. The connection is made successfully, as far as I can tell. However, when I try to ping the server (standard closing step in all the tutorials I could find) but sadly without the expected result.
In the server console nothing particular happens, in the client console the following can be seen:
Code:
Opening device LAN-verbinding
Opened UDP socket
Opened UDP socket
Sending DNS queries for iodine.domain.tld to 129.129.129.129
Autodetecting DNS query type (use -T to override).Opened UDP socket
Using DNS type NULL queries
Version ok, both using protocol v 0x00000502. You are user #0
Enabling interface 'LAN-verbinding'
Setting IP of interface 'LAN-verbinding' to 10.0.0.2 (can take a few seconds)...
Server tunnel IP is 10.0.0.1
Skipping raw mode
Using EDNS0 extension
Switching upstream to codec Base128
Server switched upstream to codec Base128
No alternative downstream codec available, using default (Raw)
Switching to lazy mode for low-latency
Server switched to lazy mode
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 not ok.. wi
ll use 1176-2=1174
Setting downstream fragment size to max 1174...
Connection setup complete, transmitting data.
chroot not available
Got SERVFAIL as reply: server failed or recursion timeout
Hmm, that's 2227172. Your data should still go through...
While investigating this issue I’ve tried a few things, but to no avail. It seems to me that the routing table is correct, that all traffic for the 10.x.x.x network should be routed over the new network device: LAN-verbinding 7.
