Clodo

Without, "windows-driver wintun" without quotes. The stable 2.18 includes the same tapctl.exe of OpenVPN, and runs automatically the "tapctl.exe create --hwid wintun" if no wintun adapter is available. But we know there are some issues under investigation.

A new beta version released here addresses an urgent issue on older macOS and Custom DNS under Windows. Other feedback is under investigation. Thanks to all.

No, sorry. You need to be able to download the 2.18.9. What package? .deb ? what you mean with "18%", apt-get ? curl? your browser download? You can try other kind of package, like portable or AppImage? Thx

The download 2.4.8 installer for Windows 7/8/8.1 from OpenVPN website has exactly the same tap-windows.exe (575288 bytes) of Eddie 2.18.9 Windows 7/8. The issue is anyway under investigation, thanks

Confirmed, will be fixed as soon as possible.

Yes, my fault, forgotten to update when deploy an urgent fix, hash recomputed now. Thx.

Honestly, no... We use the original wintun packaging/deployment, and the original tunctl.exe from OpenVPN for creating adapter, but there are a lots of issues in a lots of Win version (never uninstall, fail to create adapter etc).... We are working on testing to identify all the issues related to new wintun driver, please be patient.

Cannot reproduce. Maybe you clicked the "Name" column header? Try to click the "Score" column header. If the issue still occurs, please provide a screenshot to understand, it's the first time we see this issue. Thx.

I personally tested 2.18.8 with rPI4-raspbian-buster without any issue (with sudo or without). I think your issue is somehow specific, so i write to you a private-message to understand and fix. Please continue in PM, thx.

OT: Thank you 😘. I live in Lombardia, the epicenter. It's a disaster here.

Great to know it works as expected. I think you also manually add the directive "windows-driver wintun", in next version this will be automatic if wintun driver is detected. Thx of the feedback, i will check this.

We updated the Windows build (without changing version number) to identify better the following issues (Windows only): - Unable to find driver path 'C:\WINDOWS' - Fixed - VCRUNTIME140.dll (reported by @rdbrn) - Fixed - Options error: Unrecognized option (reported by @Telos , @kiwi, @blaHbluBB) - Fixed

I confirm this issue. It doesn't happen every time. When it happens, it's infinite and you need to manually press key N. It will be fixed soon, sorry.

Hi to all, the latest Eddie 2.18.8 experimental released today, works with wintun, please test if interested. Go to https://openvpn.net/community-downloads/, at bottom "OpenVPN 2.5_git wintun technology preview", click the "here" link and install. If you already have the right "openvpn.exe", use it directly: Eddie will install the wintun driver when needed, and also create the adapter. Eddie -> Settings -> Advanced -> OpenVPN Custom Path -> choose your "openvpn.exe" from 2.5, if already installed probably it is "C:\Program Files\OpenVPN\bin\openvpn.exe". At this point, Eddie will use OpenVPN 2.5 (but still with standard TUN driver). Eddie -> Settings -> OVPN directives -> Custom directives, add "windows-driver wintun". At this point, Eddie will use the OpenVPN 2.5 with the newest Wintun driver.

@rgrdgr @funkoholic Now the latency tests have a feedback also in CLI edition, are faster (more concurrency threads), and specify a --server skip the latency test. @rgrdgr the bug about routes in cmdline is fixed, please retry.