-.B \-\-dev\-node tun
-. When not specifying a
+.B \-\-dev\-node tun\fR.
+When not specifying a
Should do the trick.
--
Thomas
On January 23, 2014 at 1:12:41 PM, Arne Schwabe (a...@rfc2549.org) wrote:
Am 21.06.13 12:48, schrieb Arne Schwabe:
> +to select a specific utun instance. To force usin
Am 21.06.13 12:48, schrieb Arne Schwabe:
> +to select a specific utun instance. To force using the tun.kext (/dev/tunX)
> use
> +.B \-\-dev\-node tun
> +. When not specifying a
> +.B \-\-dev\-node
> +option openvpn will first try to open utun, and fall back to tun.kext.
I just noticed that this do
On Fri, Jun 21, 2013 at 6:48 AM, Arne Schwabe wrote:
> 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-n
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
