Bundle TAP-Windows installer and persist startup config
This commit is contained in:
@@ -46,17 +46,19 @@ Install dependencies, then start the Tauri development window:
|
||||
npm run tauri dev
|
||||
|
||||
The portable build creates `release/super-n2n-portable.zip`. It contains
|
||||
`n2n/edge.exe` and `n2n/supernode.exe`; on Windows Super N2N starts them with
|
||||
the relative paths `./n2n/edge.exe` and `./n2n/supernode.exe`.
|
||||
`n2n/edge.exe`, `n2n/supernode.exe`, and the official TAP-Windows installer in
|
||||
`drivers/tap-windows-9.24.7-I601-Win10.exe`; on Windows Super N2N starts the n2n
|
||||
programs with the relative paths `./n2n/edge.exe` and `./n2n/supernode.exe`.
|
||||
|
||||
### Windows TAP requirement
|
||||
|
||||
N2N uses an installed TAP-Windows virtual adapter; it does not create a new
|
||||
adapter itself. Super N2N automatically selects an available TAP-Windows
|
||||
adapter before starting Edge and reports a clear error when none is installed.
|
||||
The optional TAP device field is only needed to select a specific existing
|
||||
adapter. Connection settings, including advanced settings, are restored on the
|
||||
next application launch.
|
||||
adapter itself. Super N2N checks for an adapter on first launch, offers the
|
||||
bundled installer when one is missing, and automatically selects an available
|
||||
adapter before starting Edge. The optional TAP device field is only needed to
|
||||
select a specific existing adapter. Connection settings, including advanced
|
||||
settings, are stored beside `super-n2n.exe` in `super-n2n.config.json` and are
|
||||
restored on the next application launch.
|
||||
|
||||
## Gitea Actions
|
||||
|
||||
|
||||
Reference in New Issue
Block a user