<div class="gmail_quote"><div>Urgh, sorry copied much. Below is cleaner.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><blockquote style="margin:0 0 0 40px;border:none;padding:0px">
Sorry all, having read the first advice from Dmitry properly, I see I was supposed to dig A on the server not the client.<div>
<br></div><div>I have done that and now connecting via the client (Windows this time), I receive;</div><div><br></div><div><div><br></div></div><div><div>C:\iodine\bin>iodine.exe -f -P test <a href="http://iodine.dnstunnel.co.cc" target="_blank">iodine.dnstunnel.co.cc</a></div>
</div><div><div>Opening device Local Area Connection 2</div></div><div><div>Opened UDP socket</div>
</div><div><div>Opened UDP socket</div></div><div><div>Opened UDP socket</div></div><div><div>Sending DNS queries for <a href="http://iodine.dnstunnel.co.cc" target="_blank">iodine.dnstunnel.co.cc</a> to 208.67.222.222</div>
</div><div class="im"><div><div>
Autodetecting DNS query type (use -T to override).</div></div><div><div>Using DNS type NULL queries</div></div><div><div>Version ok, both using protocol v 0x00000502. You are user #0</div></div></div><div><div>Enabling interface 'Local Area Connection 2'</div>
</div><div><div>Setting IP of interface 'Local Area Connection 2' to 10.0.0.2 (can take a few se</div></div><div><div>conds)...</div></div><div class="im"><div><div><br></div></div><div><div>Server tunnel IP is 10.0.0.1</div>
</div>
<div><div>Testing raw UDP data to the server (skip with -r)</div></div></div><div><div>Server is at 213.123.69.144, trying raw login: ....failed</div></div><div><div>Using EDNS0 extension</div></div><div class="im"><div>
<div>Switching upstream to codec Base128</div>
</div><div><div>Server switched upstream to codec Base128</div></div><div><div>No alternative downstream codec available, using default (Raw)</div></div><div><div>Switching to lazy mode for low-latency</div></div><div><div>
Server switched to lazy mode</div></div><div><div>Autoprobing max downstream fragment size... (skip with -m fragsize)</div></div></div><div><div>768 ok.. 1152 ok.. ...1344 not ok.. ...1248 not ok.. ...1200 not ok.. 1176 ok..</div>
</div><div><div>...1188 not ok.. will use 1176-2=1174</div></div><div><div>Setting downstream fragment size to max 1174...</div></div><div><div>Connection setup complete, transmitting data.</div></div><div><div>Hmm, getting some out-of-sequence DNS replies. Setting interval to 1 (use -I1 ne</div>
</div><div><div>xt time on this network). If data traffic still has large hiccups, try if -L0 wo</div></div><div><div>rks better.</div></div></blockquote><div><div><br></div><div>I'm still confused by how I connect this tunnel which seems to be active via local area connection 2 in this case, to my browser. I want to use this to tunnel my way around paywall restrictions.</div>
<div><br></div><div>Thanks,</div><div><br></div><font color="#888888"><div>Chris</div></font><div><div></div><div class="h5"><br><div class="gmail_quote">On 16 May 2011 11:35, Chris Parker <span dir="ltr"><<a href="mailto:cockneyparker@btinternet.com" target="_blank">cockneyparker@btinternet.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div><div class="gmail_quote">So as for my wants, I wish to be able to pipe all my browser traffic through this tunnel and at the moment I believe that I am actually connecting via the 'external' internet connection I have.<div>
<br></div><div>dig A ns.iodine etc done and results in.</div>
<div><br></div><div><div>macbook-pro:~ ecrime2$ dig A <a href="http://ns.iodine.dnstunnel.co.cc" target="_blank">ns.iodine.dnstunnel.co.cc</a> => 192.168.0.101</div><div>macbook-pro:~ ecrime2$ dig A <a href="http://ns.iodine.dnstunnel.co.cc" target="_blank">ns.iodine.dnstunnel.co.cc</a></div>
<div><br></div><div>; <<>> DiG 9.6.0-APPLE-P2 <<>> A <a href="http://ns.iodine.dnstunnel.co.cc" target="_blank">ns.iodine.dnstunnel.co.cc</a></div><div>;; global options: +cmd</div><div>;; Got answer:</div>
<div>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6301</div>
<div>;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0</div><div><br></div><div>;; QUESTION SECTION:</div><div>;<a href="http://ns.iodine.dnstunnel.co.cc" target="_blank">ns.iodine.dnstunnel.co.cc</a>.<span style="white-space:pre-wrap"> </span>IN<span style="white-space:pre-wrap"> </span>A</div>
<div><br></div><div>;; ANSWER SECTION:</div><div><a href="http://ns.iodine.dnstunnel.co.cc" target="_blank">ns.iodine.dnstunnel.co.cc</a>. 3456<span style="white-space:pre-wrap"> </span>IN<span style="white-space:pre-wrap"> </span>A<span style="white-space:pre-wrap"> </span>192.168.0.101</div>
<div><br></div><div>;; Query time: 83 msec</div><div>;; SERVER: 81.142.204.118#53(81.142.204.118)</div><div>;; WHEN: Mon May 16 11:00:35 2011</div><div>;; MSG SIZE rcvd: 59</div><div><br></div><div>Any helpful suggestions / guidance?</div>
<div><br></div><font color="#888888"><div>Chris</div></font><div><div></div><div><br><div class="gmail_quote">On 16 May 2011 10:53, Dmitry Shyshkin <span dir="ltr"><<a href="mailto:dmitry.shyshkin@gmail.com" target="_blank">dmitry.shyshkin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#ffffff">
What to do next is depend on what you want from iodine tunnel. <br>
Your server should be already accessed trough iodine tunnel: try to
ping/telnet/ssh 10.0.0.1. <br>
<br>
Also iodined points to local address (dig A
<a href="http://ns.iodine.dnstunnel.Co.CC" target="_blank">ns.iodine.dnstunnel.Co.CC</a> => 192.168.0.101). Add '-n
213.123.69.144' to iodined options. I don't think that it is
important (you have already connected the client) but sometimes it
may be.<br>
<br>
Regards,<br>
Dmitry Shyshkin<div><div></div><div><br>
<br>
On 05/16/2011 12:28 PM, Chris Parker wrote:
</div></div><blockquote type="cite"><div><div></div><div>
<div>As this is my first email, first of all hello everyone, hope
you are all well.</div>
<div><br>
</div>
<div>Now to the problem at hand. I am running an Ubuntu Server
behind a Netgear WG384GT router and am currently connecting via
a MacBook Pro client. I have iodine installed and working on
both (I think) and have been able to make a successful
connection from client to server.</div>
<div><br>
</div>
<div>
<div>macbook-pro:bin ecri2$ sudo ./iodine -f -P xxx <a href="http://iodine.dnstunnel.co.cc" target="_blank">iodine.dnstunnel.co.cc</a></div>
<div>Password:</div>
<div>Opened /dev/tun0</div>
<div>Opened UDP socket</div>
<div>
Sending DNS queries for <a href="http://iodine.dnstunnel.co.cc" target="_blank">iodine.dnstunnel.co.cc</a>
to 81.142.204.118</div>
<div>Autodetecting DNS query type (use -T to override).</div>
<div>Using DNS type NULL queries</div>
<div>Version ok, both using protocol v 0x00000502. You are user
#0</div>
<div>Setting IP of tun0 to 10.0.0.2</div>
<div>Adding route <a href="http://10.0.0.2/27" target="_blank">10.0.0.2/27</a> to 10.0.0.2</div>
<div>add net <a href="http://10.0.0.2" target="_blank">10.0.0.2</a>:
gateway 10.0.0.2</div>
<div>Setting MTU of tun0 to 1130</div>
<div>Server tunnel IP is 10.0.0.1</div>
<div>Testing raw UDP data to the server (skip with -r)</div>
<div>Server is at 192.168.0.101, trying raw login: ....failed</div>
<div>iodine: Got FORMERR as reply: server does not understand
our request</div>
<div>DNS relay does not support EDNS0 extension</div>
<div>Switching upstream to codec Base128</div>
<div>Server switched upstream to codec Base128</div>
<div>No alternative downstream codec available, using default
(Raw)</div>
<div>Switching to lazy mode for low-latency</div>
<div>Server switched to lazy mode</div>
<div>Autoprobing max downstream fragment size... (skip with -m
fragsize)</div>
<div>...768 not ok.. ...384 not ok.. 192 ok.. ...288 not ok..
...240 not ok.. 216 ok.. 228 ok.. ...234 not ok.. ...231 not
ok.. ...230 not ok.. will use 228-2=226</div>
<div>Setting downstream fragment size to max 226...</div>
<div>Connection setup complete, transmitting data</div>
</div>
<div><br>
</div>
<div>So assuming that that is OK, what I need to know is what I
have to do next. I am guessing that I need to make the client
send its data via this tunnel, but I am confused and despite
hunting the web I have been unable to answer my question thus
far.</div>
<div><br>
</div>
<div>I am also keen to see whether my domains and DNS settings are
correct and can explain those. </div>
<div>I have a domain set up as follows;</div>
<blockquote style="margin:0pt 0pt 0pt 40px;border:medium none;padding:0px">
<div>
<div>Domain : <span style="white-space:pre-wrap"> </span><a href="http://dnstunnel.Co.CC" target="_blank">dnstunnel.Co.CC</a>
</div>
<div>Expires on : 2012-05-13</div>
</div>
<div>
<div>Service Type : <span style="white-space:pre-wrap"> </span>Name server (DNS)</div>
</div>
<div>
<div>Name server : <span style="white-space:pre-wrap"> </span><a href="http://freedns1.registrar-servers.com" target="_blank">freedns1.registrar-servers.com</a></div>
</div>
<div>
<div><a href="http://freedns2.registrar-servers.com" target="_blank">freedns2.registrar-servers.com</a></div>
</div>
<div>
<div><a href="http://freedns3.registrar-servers.com" target="_blank">freedns3.registrar-servers.com</a> </div>
</div>
</blockquote>
<div><br>
</div>
And then at namescheap (provider of the above NS) I have;
<div>
<div>Domain: <a href="http://dnstunnel.co.cc" target="_blank">dnstunnel.co.cc</a></div>
<div><span style="white-space:pre-wrap"> </span>HOST
NAME <span style="white-space:pre-wrap">
</span>IP ADDRESS/ URL <span style="white-space:pre-wrap"> </span> RECORD TYPE <span style="white-space:pre-wrap"> </span>MX
PREF <span style="white-space:pre-wrap">
</span>TTL </div>
</div>
<div>
<div> <span style="white-space:pre-wrap"> </span>@
<span style="white-space:pre-wrap"> </span>
<span style="white-space:pre-wrap"> </span>
<span style="white-space:pre-wrap"> </span>
n/a <span style="white-space:pre-wrap"> </span></div>
</div>
<div>
<div> <span style="white-space:pre-wrap"> </span>www
<span style="white-space:pre-wrap"> </span>
<span style="white-space:pre-wrap"> </span>
<span style="white-space:pre-wrap"> </span>
n/a <span style="white-space:pre-wrap"> </span></div>
<div> <span style="white-space:pre-wrap"> </span>SUB-DOMAIN
SETTINGS</div>
<div> <span style="white-space:pre-wrap"> </span>tunnel
213..123..69.144 A address <span style="white-space:pre-wrap"> </span> <span style="white-space:pre-wrap"> </span> <span style="white-space:pre-wrap"> </span>n/a
<span style="white-space:pre-wrap"> </span></div>
<div> <span style="white-space:pre-wrap"> </span>iodine
<a href="http://tunnel.dnstunnel.co.cc" target="_blank">tunnel.dnstunnel.co.cc</a> NS
record<span style="white-space:pre-wrap">
</span> <span style="white-space:pre-wrap"> </span> <span style="white-space:pre-wrap"> </span>n/a <span style="white-space:pre-wrap"> </span></div>
<div><br>
</div>
<div>Please help!</div>
</div>
</div></div><pre><fieldset></fieldset>
_______________________________________________
iodine-users mailing lists
<a href="mailto:iodine-users@lists.wpkg.org" target="_blank">iodine-users@lists.wpkg.org</a>
<a href="http://lists.wpkg.org/mailman/listinfo/iodine-users" target="_blank">http://lists.wpkg.org/mailman/listinfo/iodine-users</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
iodine-users mailing lists<br>
<a href="mailto:iodine-users@lists.wpkg.org" target="_blank">iodine-users@lists.wpkg.org</a><br>
<a href="http://lists.wpkg.org/mailman/listinfo/iodine-users" target="_blank">http://lists.wpkg.org/mailman/listinfo/iodine-users</a><br>
<br></blockquote></div><br></div></div></div>
</div><br>
</div></div></blockquote></div><br></div></div></div>
</blockquote></div><br>