Windows TUN device name

[leonardospeca]

Hi, I built by myself the OpenVPN Tap-windows, that offer the opportunity to change same information such:

dnl define the TAP version
define([PRODUCT_NAME], [TAP-Windows])
define([PRODUCT_PACKAGE_NAME], [tap-windows])
define([PRODUCT_PUBLISHER], [OpenVPN Technologies, Inc.])
define([PRODUCT_VERSION], [9.24.6])
define([PRODUCT_VERSION_RESOURCE], [9,24,6,601])
define([PRODUCT_TAP_WIN_COMPONENT_ID], [tap0901])
define([PRODUCT_TAP_WIN_MAJOR], [9])
define([PRODUCT_TAP_WIN_MINOR], [24])
define([PRODUCT_TAP_WIN_REVISION], [6])
define([PRODUCT_TAP_WIN_BUILD], [601])
define([PRODUCT_TAP_WIN_PROVIDER], [TAP-Windows Provider V9])
define([PRODUCT_TAP_WIN_CHARACTERISTICS], [0x1])
define([PRODUCT_TAP_WIN_DEVICE_DESCRIPTION], [TAP-Windows Adapter V9])
define([PRODUCT_TAP_WIN_RELDATE], [10/08/2020])

Anyway, when I install it, Windows call it Local Area Connection and I don't think I can change that name.

The only way to connect from edge is using this name, Local Area Connection.
It's possible to connect using as tun device name, the driver id, or the driver name, or something else that can be specify during the build of the driver?

Do you have other suggestions?
Thanks

[Logan007]

This must be some Windows default kicking in. I have just read about openVPN users themselves seemingly struggle with this naming convention developing rename scripts for use immediately after installation. So, maybe you need to bundle your install script with a rename script?

By the way, renaming the device using netsh as described at the bottom of this page seems to survive a reboot.

[Logan007]

Considered answered as no news, closing. Please re-open if required.