Tinc 1.0.26 on Mac OS X

Mike Purvis mpurvis at clearpathrobotics.com
Thu Feb 25 19:55:59 CET 2016


Hey all,

I'm trying to use tinc 1.0.26 from Homebrew on Mac OS X 10.10.5, and having
some trouble. Is anyone successfully doing this?

Here's my config:

$ sudo cat /etc/tinc/robotvpn/tinc.conf
Name = elendur
Mode = switch
AddressFamily = ipv4
Interface = tincdev0
Compression = 1
ConnectTo = robot_ph_cpe22_04

And here's the invocation:

$ sudo tincd -D -c /etc/tinc/robotvpn -d
tincd 1.0.26 (Nov  2 2015 06:12:50) starting, debug level 1
/dev/tap0 is a Generic BSD tap device
/etc/tinc/robotvpn/tinc-up: line 3: avahi-autoipd: command not found
Usage: ip route list
       ip route get ADDRESS
       ip route { add | del } ROUTE
ROUTE := PREFIX [ nexthop NH ]
Script tinc-up exited with non-zero status 1
Listening on 0.0.0.0 port 655
Ready
Trying to connect to robot_ph_cpe22_04 (10.27.200.104 port 655)
Connected to robot_ph_cpe22_04 (10.27.200.104 port 655)
Connection with robot_ph_cpe22_04 (10.27.200.104 port 655) activated
Error while writing to Generic BSD tap device /dev/tap0: Input/output error
Error while writing to Generic BSD tap device /dev/tap0: Input/output error
Error while writing to Generic BSD tap device /dev/tap0: Input/output error

I know I'm missing Avahi, and I'll have to deal with name resolution
separately (this config originated on Ubuntu), but I'm trying to understand
what is going on with the BSD tap device issues. Previously, tincd wasn't
able to create the tap0 device at all, but I installed TunTap
<http://tuntaposx.sourceforge.net/>, and now it does create it:

$ ifconfig tap0
tap0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 0e:27:1d:a7:4e:a1
media: autoselect
status: active
open (pid 28939)

I tried bypassing the Avahi config and just assigning it an IP manually,
but it doesn't seem able to communicate.

Any pointers what's going on here? Much appreciated,

Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20160225/5334f97d/attachment.html>


More information about the tinc mailing list