[PR #4827] [CLOSED] vnet: initial Windows support #5052

New issue

Closed

opened 2026-05-05 14:53:46 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 14:53:46 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/fatedier/frp/pull/4827
Author: @EZForever
Created: 6/5/2025
Status: ❌ Closed

Base: dev ← Head: vnet-windows

📝 Commits (1)

88cee39 vnet: initial Windows support

📊 Changes

2 files changed (+125 additions, -1 deletions)

View changed files

📝 pkg/vnet/tun_unsupported.go (+1 -1)
➕ pkg/vnet/tun_windows.go (+124 -0)

📄 Description

WHY

VirtualNet is a very promising feature, and the underlying TUN library (golang.zx2c4.com/wireguard/tun) already supports Windows, so... why not ;)

Additional Considerations

golang.zx2c4.com/wireguard/tun on Windows relies on wintun to do its job, namely the wintun.dll file from the prebuilt binaries package. Including it as a built-in dependency is out of question, since wintun is in C, and we need the (signed) prebuilt driver binaries anyway for dealing with Windows' driver signing enforcement. Maybe we could bundle it with Windows release builds, but that kinda breaks the zero-dependency promise. It is not a concerning problem right now since VirtualNet is still in Alpha stage and users are assumed to know what they're doing; we could just direct them to manually download the required binaries in the docs.

P.S. This is my first time coding in Go, so please forgive me for stupid mistakes in code.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/fatedier/frp/pull/4827 **Author:** [@EZForever](https://github.com/EZForever) **Created:** 6/5/2025 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `vnet-windows` --- ### 📝 Commits (1) - [`88cee39`](https://github.com/fatedier/frp/commit/88cee39bdbbeb0cfa558ddb62b8ce0e03bd7b9b1) vnet: initial Windows support ### 📊 Changes **2 files changed** (+125 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `pkg/vnet/tun_unsupported.go` (+1 -1) ➕ `pkg/vnet/tun_windows.go` (+124 -0) </details> ### 📄 Description ### WHY VirtualNet is a very promising feature, and the underlying TUN library (`golang.zx2c4.com/wireguard/tun`) already supports Windows, so... why not ;) ### Additional Considerations `golang.zx2c4.com/wireguard/tun` on Windows relies on [wintun](https://www.wintun.net/) to do its job, namely the `wintun.dll` file from the prebuilt binaries package. Including it as a built-in dependency is out of question, since wintun is in C, and we need the (signed) prebuilt driver binaries anyway for dealing with Windows' driver signing enforcement. Maybe we could bundle it with Windows release builds, but that kinda breaks the zero-dependency promise. It is not a concerning problem right now since VirtualNet is still in Alpha stage and users are assumed to know what they're doing; we could just direct them to manually download the required binaries in the docs. P.S. This is my first time coding in Go, so please forgive me for stupid mistakes in code. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>