Am 20.06.13 15:32, schrieb Jonathan K. Bullard:
> A minor problem is that for each of the 255 attempts to get a utun
> device (device #0 through device #254), it generates the following
> warning message:
> Opening utun (ioctl(CTLIOCGINFO)): No such file or directory
> It's ugly, but cosmetic.
On Thu, Jun 20, 2013 at 4:58 AM, Arne Schwabe wrote:
> I have a OS X 10.6 VM with Xcode 3.2.6 installed and this VM has the
> if/utun.h header. I probably was added somewhere between 10.6.0 and 10.6.8.
Ah. Thanks for mentioning this. That makes sense.
> I changed the M_ERR to M_WARN. It should
Mac OS X 10.7+ natively supports tun devices (called utun). The "standard"
utun.ko driver is sometimes problematic (e.g. VmWare Fusion 5 and tun.ko do not
work together).
When OpenVPN is compiled with utun support it will if no dev-node is given
first try to use utun and if that is not availabl
