Hi Maxim,
Not much to it: avahi-autoipd -D $INTERFACE # ifconfig $INTERFACE 169.254.45.23 netmask 255.255.0.0 up ip route add 172.20.0.0/16 dev $INTERFACE Mac OS X doesn't have "ip" by default, so I also installed the Homebrew package "iproute2mac", which provides an emulation of "ip" on top of the legacy ifconfig/route calls. The commented-out ifconfig line was my attempt to replace avahi-autoipd with a fixed IP, just for demonstration purposes. But I get the same result using ifconfig to set the IP address. On 25 February 2016 at 23:40, Maxim Vorontsov <[email protected]> wrote: > Hi. > > May you show your tinc-up script? And subnet-up, host-up if you have they > at all. > > On February 25, 2016 9:55:59 PM GMT+03:00, Mike Purvis < > [email protected]> wrote: > >> 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 >> >> ------------------------------ >> >> tinc mailing list >> [email protected] >> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc >> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > _______________________________________________ > tinc mailing list > [email protected] > http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc > >
_______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
