Lion OS X tinc issues.
Mike Bentzen
mike at bentzen.com.au
Wed Apr 11 22:57:53 CEST 2012
Hi Matthew,
Hmmm… I would like to see more of the logs.
Before you try to enable dhcp, are you able to set a static ip address on the adapter?
Can you ping your ubuntu machine from your laptop before enabling dhcp?
Reading that Input/Output error, I believe the tuntaposx drivers are not loaded or not configured.
Did you run: sudo port load tuntaposx after you installed the tuntaposx drivers?
Given your machine a reboot? :)
Mike
On 12/04/2012, at 2:05 AM, Matthew Tolle wrote:
>
> Tuntaposx is installed:
>
> # port installed
> The following ports are currently installed:
> lzo2 @2.05_1 (active)
> openssl @1.0.1_2 (active)
> openvpn2 @2.2.1_0 (active)
> tinc @1.0.18_0 (active)
> tuntaposx @20111101_0 (active)
> zlib @1.2.6_0 (active)
>
> 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:
>
> In one screen session I run: tincd --logfile=/var/log/tinc --debug=2 -n
> In a second screen session I've got tail -f /var/log/tinc going.
>
> Tunnel comes up. On the ubuntu side your see this;
>
> 2012-04-10 22:00:29 tinc.vpn[9267]: Trying to connect to laptop (185.193.32.20 port 655)
> 2012-04-10 22:00:29 tinc.vpn[9267]: Connected to laptop (185.193.30.32 port 655)
> 2012-04-10 22:00:29 tinc.vpn[9267]: Connection with laptop (185.193.30.32 port 655) activated
>
> On the laptop side it looks connected as well:
>
> 2012-04-10 22:00:56 tinc.vpn[57014]: tincd 1.0.18 (Apr 9 2012 13:14:47) starting, debug level 2
> 2012-04-10 22:00:56 tinc.vpn[57014]: /dev/tun0 is a Generic BSD tap device
> 2012-04-10 22:00:56 tinc.vpn[57014]: Executing script tinc-up
> 2012-04-10 22:00:56 tinc.vpn[57014]: Listening on 0.0.0.0 port 655
> 2012-04-10 22:00:56 tinc.vpn[57014]: Listening on :: port 655
> 2012-04-10 22:00:56 tinc.vpn[57014]: Ready
> 2012-04-10 22:01:33 tinc.vpn[57014]: Connection from 65.13.183.22 port 10503
> 2012-04-10 22:01:33 tinc.vpn[57014]: Connection with server (64.13.183.22 port 10503) activated
>
> I run the ipconfig set tun0 DHCP. That's when I get the errors.
>
> 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.
>
> Thanks,
>
> -Matt
>
>
> On Apr 11, 2012, at 4:33 AM, Mike Bentzen wrote:
>
>> Hi Matthew,
>>
>> The subnet variable is not needed in switch mode. You can remove this line from your laptop's hosts file.
>>
>> "Error while writing to Generic BSD tap device /dev/tun0: Input/output error"
>> 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.
>>
>> If you have installed tuntaposx try this:
>>
>> Open a terminal, and run tinc in debug mode:
>> :# tinc -n <vpn> -d5 -D
>> When tinc is running, try to bring up the tap0 adapter. Open another terminal and run the command:
>> :# ipconfig set tap0 dhcp
>>
>> Hopefully, you should not see the Input/Output error anymore.
>>
>> Kind Regards,
>> Mike
>>
>>
>> On 11/04/2012 3:10 PM, Matthew Tolle wrote:
>>>
>>>
>>>
>>> Hi Folks,
>>>
>>> This has been driving me nuts all day. I've been unable to google myself out of it. Maybe someone here can help?
>>>
>>> I followed the instructions from:
>>>
>>> http://www.tinc-vpn.org/examples/macbook-install/
>>>
>>> Ubuntu server <-> Ubuntu server works just fine with the same config. Ubuntu server <-> Mac laptop not so much.
>>>
>>> The error I'm getting is:
>>>
>>> 2012-04-10 21:48:44 tinc.l3vpn[52621]: Error while writing to Generic BSD tap device /dev/tun0: Input/output error
>>> 2012-04-10 21:48:44 tinc.l3vpn[52621]: Error while writing to Generic BSD tap device /dev/tun0: Input/output error
>>> <lot of the same spew…>
>>>
>>> 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.
>>>
>>> Both sides seems happily connected before issuing the DHCP command.
>>>
>>> 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:
>>>
>>> vpn Link encap:Ethernet HWaddr 4e:31:65:e7:32:f6
>>> inet6 addr: fe80::4c32:66ff:fec6:32e7/64 Scope:Link
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:1034 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:529919 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:500
>>> RX bytes:87139 (87.1 KB) TX bytes:56253688 (56.2 MB)
>>>
>>> standard kinds of goodness. On the Mac side it seems slim on info:
>>>
>>> tun0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>>> open (pid 57014)
>>>
>>> Makes me think that the tun/tap device is wonky?
>>>
>>> The Tun/Tap stuff I got from port as per the instructions.
>>>
>>> Configs:
>>>
>>> # cat tinc.conf
>>> Name = laptop
>>> Mode = switch
>>>
>>> # cat hosts/laptop
>>> Subnet = 10.20.20.0/24
>>> Address = 10.20.20.38
>>>
>>> -----BEGIN RSA PUBLIC KEY-----
>>> <blahblahblah>
>>>
>>> # cat hosts/server
>>>
>>> -----BEGIN RSA PUBLIC KEY-----
>>> <blahblahblah>
>>>
>>> I figure it's something very simple that I'm missing. Can someone save my sanity please?
>>>
>>> Thanks,
>>>
>>> -Matt
>>>
>>>
>>>
>>> _______________________________________________
>>> tinc mailing list
>>> tinc at tinc-vpn.org
>>> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>>
>> _______________________________________________
>> tinc mailing list
>> tinc at tinc-vpn.org
>> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20120412/d1fd91e9/attachment-0001.html>
More information about the tinc
mailing list