<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>Hi Mike,</div><div><br></div><div>When I get home tonight I'll try and recreate it and provide more logs. </div><div><br></div><div>I did not do a "port load tuntaposx". I did reboot. I'll try the load as well to see if that makes a difference. </div><div><br></div><div>Thanks,</div><div><br></div><div>-Matt</div><br><div><div>On Apr 11, 2012, at 1:57 PM, Mike Bentzen wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Matthew,<div><br></div><div>Hmmm… I would like to see more of the logs.<div><br></div><div>Before you try to enable dhcp, are you able to set a static ip address on the adapter?</div><div>Can you ping your ubuntu machine from your laptop before enabling dhcp?</div><div><br></div><div>Reading that Input/Output error, I believe the tuntaposx drivers are not loaded or not configured.</div><div>Did you run: sudo port <em>load tuntaposx </em>after you installed the tuntaposx drivers?</div><div>Given your machine a reboot? :)</div><div><br></div><div>Mike</div><div><br></div><div><br></div><div><br><div><div>On 12/04/2012, at 2:05 AM, Matthew Tolle wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>Tuntaposx is installed:</div><div><br></div><div><div># port installed</div><div>The following ports are currently installed:</div><div> lzo2 @2.05_1 (active)</div><div> openssl @1.0.1_2 (active)</div><div> openvpn2 @2.2.1_0 (active)</div><div> tinc @1.0.18_0 (active)</div><div> tuntaposx @20111101_0 (active)</div><div> zlib @1.2.6_0 (active)</div></div><div><br></div><div>The commands you have below are more or less what I've been doing. My scroll back doesn't go far enough back for me to cut and paste the output. I can run it again when I get home tonight and send you more details if it helps. The basics are:</div><div><br></div><div>In one screen session I run: tincd --logfile=/var/log/tinc --debug=2 -n </div><div>In a second screen session I've got tail -f /var/log/tinc going. </div><div><br></div><div>Tunnel comes up. On the ubuntu side your see this;</div><div><br></div><div><div>2012-04-10 22:00:29 tinc.vpn[9267]: Trying to connect to laptop (185.193.32.20 port 655)</div><div>2012-04-10 22:00:29 tinc.vpn[9267]: Connected to laptop (185.193.30.32 port 655)</div><div>2012-04-10 22:00:29 tinc.vpn[9267]: Connection with laptop (185.193.30.32 port 655) activated</div></div><div><br></div><div>On the laptop side it looks connected as well:</div><div><br></div><div><div>2012-04-10 22:00:56 tinc.vpn[57014]: tincd 1.0.18 (Apr 9 2012 13:14:47) starting, debug level 2</div><div>2012-04-10 22:00:56 tinc.vpn[57014]: /dev/tun0 is a Generic BSD tap device</div><div>2012-04-10 22:00:56 tinc.vpn[57014]: Executing script tinc-up</div><div>2012-04-10 22:00:56 tinc.vpn[57014]: Listening on 0.0.0.0 port 655</div><div>2012-04-10 22:00:56 tinc.vpn[57014]: Listening on :: port 655</div><div>2012-04-10 22:00:56 tinc.vpn[57014]: Ready</div><div>2012-04-10 22:01:33 tinc.vpn[57014]: Connection from 65.13.183.22 port 10503</div><div>2012-04-10 22:01:33 tinc.vpn[57014]: Connection with server (64.13.183.22 port 10503) activated</div></div><div><br></div><div>I run the ipconfig set tun0 DHCP. That's when I get the errors. </div><div><br></div><div>I've tried waiting for a few minutes after the tunnels is up to see if things need to settle down before I run the DHCP command. Doesn't make a difference. </div><div><br></div><div>Thanks,</div><div><br></div><div>-Matt</div><div><br></div><br><div><div>On Apr 11, 2012, at 4:33 AM, Mike Bentzen wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
Hi Matthew,<br>
<br>
The subnet variable is not needed in switch mode. You can remove
this line from your laptop's hosts file.<br>
<br>
"Error while writing to Generic BSD tap device /dev/tun0:
Input/output error"<br>
This means that tinc cannot write to the network interface. It
usually means that the interfaces don't exist (i.e. tuntaposx isn't
installed) or it isn't configured.<br>
<br>
If you have installed tuntaposx try this:<br>
<br>
Open a terminal, and run tinc in debug mode:<br>
:# tinc -n <vpn> -d5 -D<br>
When tinc is running, try to bring up the tap0 adapter. Open another
terminal and run the command:<br>
:# ipconfig set tap0 dhcp<br>
<br>
Hopefully, you should not see the Input/Output error anymore.<br>
<br>
Kind Regards,<br>
Mike<br>
<br>
<br>
On 11/04/2012 3:10 PM, Matthew Tolle wrote:
<blockquote cite="mid:AE04AB05-C627-465E-9013-805C18B57BA6@night.com" type="cite">
<div><br>
</div>
<div><br>
</div>
<div>Hi Folks,</div>
<div><br>
</div>
<div>This has been driving me nuts all day. I've been unable to
google myself out of it. Maybe someone here can help?</div>
<div><br>
</div>
<div>
<div>I followed the instructions from: </div>
<div><br>
</div>
<div><a moz-do-not-send="true" href="http://www.tinc-vpn.org/examples/macbook-install/">http://www.tinc-vpn.org/examples/macbook-install/</a></div>
</div>
<div><br>
</div>
<div>Ubuntu server <-> Ubuntu server works just fine with
the same config. Ubuntu server <-> Mac laptop not so
much. </div>
<div><br>
</div>
<div>The error I'm getting is:</div>
<div><br>
</div>
<div>
<div>2012-04-10 21:48:44 tinc.l3vpn[52621]: Error while writing
to Generic BSD tap device /dev/tun0: Input/output error</div>
<div>2012-04-10 21:48:44 tinc.l3vpn[52621]: Error while writing
to Generic BSD tap device /dev/tun0: Input/output error</div>
</div>
<div><lot of the same spew…></div>
<div><br>
</div>
<div>The error pops up after I try to get DHCP going over the
link. (ipconfig set tun0 DHCP). Not that it works before I try
and do that. </div>
<div><br>
</div>
<div>Both sides seems happily connected before issuing the DHCP
command.</div>
<div><br>
</div>
<div>I've tried just about everything I can think of for the
configs. Switch on, off, bridging on and off on the server
side.. nothing seems to work. I do find it odd that under linux
the virtual device looks like this: </div>
<div><br>
</div>
<div>
<div>vpn Link encap:Ethernet HWaddr 4e:31:65:e7:32:f6 </div>
<div> inet6 addr: fe80::4c32:66ff:fec6:32e7/64
Scope:Link</div>
<div> UP BROADCAST RUNNING MULTICAST MTU:1500
Metric:1</div>
<div> RX packets:1034 errors:0 dropped:0 overruns:0
frame:0</div>
<div> TX packets:529919 errors:0 dropped:0 overruns:0
carrier:0</div>
<div> collisions:0 txqueuelen:500 </div>
<div> RX bytes:87139 (87.1 KB) TX bytes:56253688 (56.2
MB)</div>
</div>
<div><br>
</div>
<div>standard kinds of goodness. On the Mac side it seems slim on
info:</div>
<div><br>
</div>
<div>
<div>tun0:
flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu
1500</div>
<div> open (pid 57014)</div>
</div>
<div><br>
</div>
<div>Makes me think that the tun/tap device is wonky? </div>
<div><br>
</div>
<div>The Tun/Tap stuff I got from port as per the instructions. </div>
<div><br>
</div>
<div>Configs: </div>
<div><br>
</div>
<div>
<div># cat tinc.conf </div>
<div>Name = laptop</div>
<div>Mode = switch</div>
</div>
<div><br>
</div>
<div>
<div># cat hosts/laptop </div>
<div>Subnet = 10.20.20.0/24</div>
<div>Address = 10.20.20.38</div>
<div><br>
</div>
<div>-----BEGIN RSA PUBLIC KEY-----</div>
</div>
<div><blahblahblah></div>
<div><br>
</div>
<div>
<div># cat hosts/server</div>
<div><br>
</div>
<div>-----BEGIN RSA PUBLIC KEY-----</div>
</div>
<div><blahblahblah></div>
<div> </div>
<div>I figure it's something very simple that I'm missing. Can
someone save my sanity please? </div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>-Matt</div>
<div><br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
tinc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tinc@tinc-vpn.org">tinc@tinc-vpn.org</a>
<a class="moz-txt-link-freetext" href="http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc">http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>tinc mailing list<br><a href="mailto:tinc@tinc-vpn.org">tinc@tinc-vpn.org</a><br><a href="http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc">http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc</a><br></blockquote></div><br></div>_______________________________________________<br>tinc mailing list<br><a href="mailto:tinc@tinc-vpn.org">tinc@tinc-vpn.org</a><br><a href="http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc">http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc</a><br></blockquote></div><br></div></div></div>_______________________________________________<br>tinc mailing list<br><a href="mailto:tinc@tinc-vpn.org">tinc@tinc-vpn.org</a><br>http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc<br></blockquote></div><br></body></html>