search for: tuntaposx

...001 > dpsf/tinc-up #!/bin/sh ifconfig $INTERFACE 10.0.0.13 netmask 255.255.255.0 > dpsf/tinc-down #!/bin/sh ifconfig $INTERFACE down I followed the port instructions to the T. Any tips are greatly appreciated! I don't know much (anything) about tun/tap, but from googling, I know that tuntaposx was installed by port, but maybe it's badly misconfigured? > sudo launchctl load -w /Library/LaunchDaemons/org.macports.tuntaposx.plist /opt/local/etc/LaunchDaemons/org.macports.tuntaposx/org.macports.tuntaposx.plist: Operation already in progress > /Library/LaunchDaemons/org.macports.t...

> kextload /Library/Extensions/tun.kext/ I didn't have a /Library/Extensions/tun.kext/ on my machine. I googled around, and downloaded and installed from http://tuntaposx.sourceforge.net/. Not sure why the macports install didn't work, but it seems I'm making progress. Now I get this: > sudo tincd -n dpsf -D -d3 tincd 1.0.21 (Feb 3 2015 20:09:36) starting, debug level 3 /dev/tun0 is a Generic BSD tun device Executing script tinc-up ifconfig: interface d...

Thanks very much! It's alive! For others who are having problems, this is a summary of the differences I needed between Linux and OS X: You'll need to install http://tuntaposx.sourceforge.net/ manually. On tinc.conf: > Linux Name = ntwigg2014linux AddressFamily = ipv4 Interface = dpsfVPN ConnectTo = dpserver001 > Mac Same, but remove the Interface line entirely On tinc-up: > Linux ifconfig $INTERFACE 10.0.0.12 netmask 255.255.255.0 > Mac ifconfig $INTERFACE...

...c on many Linux machines and thought it would be easy to set up on MacOSX too. Docs on setting tinc up on MacOSX are not bad but they don't cover setup of tun/tap devices and even don't mention any recommended drivers. I didn't have any tun or tap devices in /dev/ so I've installed tuntaposx from here http://tuntaposx.sourceforge.net. I saw this FAQ http://www.tinc-vpn.org/faq/#index5h3 and tried setting IP after starting `tincd -D`. I can communicate with one machine now by running `ifconfig 192.168.100.4 192.168.100.1` but only with it, not with others from the VPN. Could you please...

....0.0 hope that helps. > On Jan 7, 2016, at 3:25 PM, Ned Twigg <ned.twigg at diffplug.com> wrote: > > > kextload /Library/Extensions/tun.kext/ > > I didn't have a /Library/Extensions/tun.kext/ on my machine. I googled around, and downloaded and installed from http://tuntaposx.sourceforge.net/ <http://tuntaposx.sourceforge.net/>. Not sure why the macports install didn't work, but it seems I'm making progress. > > Now I get this: > > sudo tincd -n dpsf -D -d3 > tincd 1.0.21 (Feb 3 2015 20:09:36) starting, debug level 3 > /dev/tun0 is a G...

...:14AM -0800, Ned Twigg wrote: > > sudo tincd -n dpsf -D -d3 > tincd 1.0.21 (Feb 3 2015 20:09:36) starting, debug level 3 > Could not open /dev/tun0: No such file or directory > Terminating That sounds like the tun module is not loaded. If you didn't reboot since installing the tuntaposx modules, try running the following command: kextload /Library/Extensions/tun.kext/ Then try to start tinc again. > And here's the contents of my files in /opt/local/etc/tinc: > > > dpsf/tinc.conf > Name = ntwigg2009mac > AddressFamily = ipv4 > Interface = dpsfVPN > C...

...et of 98 bytes from gullinbursti (<white_ip> port 766) > Writing packet of 98 bytes to Generic BSD tap device But once I send any packet from the mini through the VPN (like ping or tcp connect attempt to any otner node) everything just starts to work as intended. Looks like some issue in tuntaposx that prevents the interface from work until a packet is sent to it. I use tinc-1.0.21 and the following config: > ConnectTo <host0> > ConnectTo <host1> > ConnectTo <host2> > ConnectTo <host3> > > GraphDumpFile = /tmp/tinc-pac.graph > Name = macmini >...

On 6 April 2015 at 15:56, Vladimir "Equidamoid" Shapranov <equidamoid at gmail.com> wrote: > Looks like some issue in tuntaposx that prevents the interface from work > until a packet is sent to it. Nope. The issue is that tinc is currently not smart enough to directly read the MAC address of the TAP device for BSD-style devices (of which tuntaposx is one). Therefore you need to send at least one packet through it so tha...

Hello everyone! I have a PowerMac running 10.6.8 and I'd love to get it connected to my VPN. However, even by compiling tuntaposx by hand on the said MacPro, I see that the kernel module is apparently built for x86_64 systems: macintosh MacOS ?? pwd /Library/Extensions/tun.kext/Contents/MacOS macintosh MacOS ?? file tun tun: Mach-O 64-bit kext bundle x86_64 Because YES! The system is running on an i386 (not stricto sens...

...feature of ssh between two Linux machines, and it works beautifully! As a result, I have come to prefer a workflow that uses an L2 tunnel, but I can't seem to find a long-term solution for this workflow on macOS. At the moment, tap devices on macOS can be generated using a kernel extension like tuntaposx <http://tuntaposx.sourceforge.net/>; however, all kernel extensions were deprecated recently and will likely be removed in a future macOS release this fall. An alternative to tap devices on macOS is something called a feth interface. Luckily, the ZeroTierOne project released a program <ht...

...m macports is 32-bit If found that in the downloads(1) page: September 13, 2009: Change linker options to produce 64 bit kext bundle for Snow Leopard. Removing the hardcoded arch from the Makefiles breaks the compilation, so I eventually picked version 20090905. And it works :) (1) http://tuntaposx.sourceforge.net/download.xhtml

Hi, I am trying to install tinc on a mac. When starting tinc a /dev/tun0 is created, on linux a device is created with a custom name, something like 'ci00001'. How can i achieve the same result on a mac ? Perry -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20130921/3acfb278/attachment.html>

...go. I already feel like I'm going to break it somehow. I am kind of surprised that there is no kind of package management system like dpkg being used. Anyway.. Looking at the macosx tinc wiki page on tinc-vpn.org, and it seems to be somewhat incomplete. I have a few questions. I installed the tuntaposx driver and set up the machine to connect to the network. Connected, and all good. I am running tinc in switch mode, and have a dhcp server giving out addresses. When tinc connects, it does not receive a dhcp address. In my tinc-up file, and running the command manually: $ sudo ipconfig tun0 set dh...

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

...'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'...

...ave 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 by...

...>>>> 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 >&g...

Hello everyone! I have a PowerMac running 10.6.8 and I'd love to get it connected to my VPN. However, even by compiling tuntaposx by hand on the said MacPro, I see that the kernel module is apparently built for x86_64 systems: macintosh MacOS ?? pwd /Library/Extensions/tun.kext/Contents/MacOS macintosh MacOS ?? file tun tun: Mach-O 64-bit kext bundle x86_64 Because YES! The system is running on an i386 (not stricto sens...

...9;m pretty sure the tinc that builds from macports is 32-bit On Wed, Dec 10, 2014 at 10:37 AM, Anne-Gwenn Kettunen <anwen at asphodelium.eu> wrote: > Hello everyone! > > I have a PowerMac running 10.6.8 and I'd love to get it connected to my > VPN. However, even by compiling tuntaposx by hand on the said MacPro, I see > that the kernel module is apparently built for x86_64 systems: > > macintosh MacOS ?? pwd > /Library/Extensions/tun.kext/Contents/MacOS > macintosh MacOS ?? file tun > tun: Mach-O 64-bit kext bundle x86_64 > > > Because YES! The syste...

...d 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...