All wintun adapters on this system are currently in use or disabled

[eewiz]

Hello All

Using v2.6.5 on Win 10.

If the OpenVPN server is disconnected using the GUI's disconnect button, OpenVPN server works correctly.
Any time the OpenVPN server dumps unceremoniously for whatever reason, for example, the client dumps and then the server times out or, something like this happens:

Code: Select all

2023-07-08 17:22:05 TLS Error: cannot locate HMAC in incoming packet from [AF_INET]185.200.116.37:37131
2023-07-08 19:18:12 TLS Error: cannot locate HMAC in incoming packet from [AF_INET]162.142.125.133:49890
2023-07-08 20:13:06 TLS Error: cannot locate HMAC in incoming packet from [AF_INET]198.235.24.128:56705
2023-07-08 22:13:11 MANAGEMENT: Client disconnected

The OpenVPN server cannot be connected again due to the following error:
"All wintun adapters on this system are currently in use or disabled."

When the OpenVPN server dumps unceremoniously, the wintun adapter is left in an weird state.
The labels on the wintun adapter in "Network Connections" say:
OpenVPN Wintun
OpenVPN Wintun
Wintun Userspace Tunnel

In "Network Connections", right-clicking the wintun adapter and using the "Disable" button produces the following error:
"It is not possible to disable the connection at this time.
This connection maybe using one or more protocols that do not support Plug and play,
or it may have been initiated by another user or the system account."
You can't disable and then re-enable the wintun adapter from the "Network Connections" dialog. Bummer.

From the "Device Manager", "Network Adapters", "Wintun Userspace Tunnel", "Driver" tab, the only related button say's "Enable Device".
Pressing the "Enable Device" button produces the following message:
Your hardware settings have changed. You must restart your computer for these changes to take effect.
Do you want to restart your computer now?
Not really, but at this point, I guess I have no choice.

I've already learned that I can skip all that rigamarole and just reboot.
But I thought I would try to find a workaround, to no avail.
O.K., post now then reboot.
What a royal PITA.

Does anyone know if v2.5.5 is similarly broken?

All for now

[eewiz]

More News,

Take a look at the following image:
https://ibb.co/GQNB42s

In reference to the Control Panel -> All Control Panel Items -> Windows Defender Firewall dialog:
As can be seen, the firewall is disabled to ensure that it is not what causes my site-to-site VPN failure.
Every time the OpenVPN server or client is connected there appears a new "OpenVPN Wintun" entry added to the "Active Private Networks:" list.
Whenever the server or client is subsequently disconnected, another new "OpenVPN Wintun" entry is added to the "Active Private Networks:" list.
Connect again and another new "OpenVPN Wintun" entry is added to the "Active Private Networks:" list.
Disconnect again and another new "OpenVPN Wintun" entry is added to the "Active Private Networks:" list.
These entries continue to accumulate and are not removed unless I navigate away from the Windows Defender Firewall dialog.
If unconnected, navigating away and then back removes all of the multitude of entries.
If connected, navigating away and then back removes all but one of the multitude of entries.
Which is then correct because the VPN server is UP.

Does anybody know what this SNAFU is all about?

All for now