bp811 As the title asks. We are looking at creating an always up VPN tunnel that runs on our workstations. This would be a management tunnel, specifically for supporting remote management tools when machines are out of the office / traveling. This would be separate from the end user VPN tunnel an employee might connect to if needed. We are using the open source client. In principle this works and I have tested it, but the rub is that each VPN tunnel needs its own tun / virtual interface in Windows. I can create an additional interface to support two tunnels. I have tested this and it works. The "dev tun" line in the client's config file dynamically chooses an available virtual interface. I would like to control which virtual interface is used, if that's possible. First question, is that possible? Second question, if so, what directives do I use in the config file to do this? I have not found anything in the online documentation that answers this question.
Pippin Hi, take a look at --dev and --dev-type in manual 2.5: https://build.openvpn.net/man/openvpn-2.5/openvpn.8.html
Pippin Forget my answer, its Windows 🙂 Please take a look here: https://community.openvpn.net/openvpn/wiki/ManagingWindowsTAPDrivers#WindowsTAPdevicenaming rename the TAP adapter icon to something like "my-tun" and reference it using the --dev-node option in OpenVPN
bp811 Pippin wrote Forget my answer, its Windows 🙂 Please take a look here: https://community.openvpn.net/openvpn/wiki/ManagingWindowsTAPDrivers#WindowsTAPdevicenaming rename the TAP adapter icon to something like "my-tun" and reference it using the --dev-node option in OpenVPN Works like a charm, thanks
