|
|
Thanks James,
I've renamed under Windows the TAP drivers to test1 and
test2, and now I use both --dev and --dev-node options, and
things now work: I can use both interfaces at the same time:
opevpn --dev test1 --dev-node test1 ...
opevpn --dev test2 --dev-node test2 ...
Thx,
John
On Tue, 6 Jan 2004, James Yonan wrote:
> Date: Tue, 6 Jan 2004 19:59:09 -0000
> From: James Yonan <jim@xxxxxxxxx>
> To: h105@xxxxxxx, openvpn-users@xxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [Openvpn-users] --dev vs --dev-node
>
> h105@xxxxxxx said:
>
> >
> >
> > Hi,
> >
> > I'm a bit confused with the purpose of --dev vs --dev-node.
> >
> > On Linux I'm using only --dev and things work fine (I've
> > --mktun'd a few interfaces ahead of time)
> >
> > But on Windows - what does --dev refer to, and what does
> > --dev-node refer to ?
>
> Think of --dev as selecting the tunnel type and unit number such as "tun" or
> "tap" or "tun5" and --dev-node selecting the device filename of the specific
> tun or tap device to use.
>
> On linux 2.4, you don't generally need to specify --dev-node because the
> default of "/dev/net/tun" is usually correct. So if you just say --dev tun on
> linux, it causes OpenVPN to automatically allocate a dynamic tun interface.
>
> On windows, --dev-node must be used because each tun/tap device has its own
> filename associated with it, in the part of the directory structure windows
> uses for devices (i.e. windows' /dev equivalent). This is because windows
> does not support dynamic device units.
>
> James
>
|