ddidderr
e619866112
Add a Windows client --tap-instance-id option for selecting a specific TAP-Windows6 adapter by NetCfgInstanceId / InterfaceGuid. The client still opens the only installed TAP adapter automatically, but now refuses to choose an arbitrary adapter when multiple TAP-Windows6 adapters are present. This keeps the MVP test run from silently configuring and opening the wrong TAP adapter on machines that already have VPN or test TAP devices installed. The error lists available adapter instance ids so the operator can rerun with the intended value. Test Plan: - cargo fmt --check - cargo test -p lanparty-client-win - cargo test --workspace - cargo clippy --workspace --all-targets -- -D warnings - git diff --check Refs: PLAN.md Windows client TAP adapter responsibility
19 lines
574 B
TOML
19 lines
574 B
TOML
[package]
|
|
name = "lanparty-client-win"
|
|
version.workspace = true
|
|
edition.workspace = true
|
|
|
|
[dependencies]
|
|
anyhow.workspace = true
|
|
clap.workspace = true
|
|
lanparty-client-core = { path = "../lanparty-client-core" }
|
|
lanparty-client-tap = { path = "../lanparty-client-tap" }
|
|
lanparty-ctrl = { path = "../lanparty-ctrl" }
|
|
lanparty-net = { path = "../lanparty-net" }
|
|
lanparty-obs = { path = "../lanparty-obs" }
|
|
lanparty-proto = { path = "../lanparty-proto" }
|
|
tokio.workspace = true
|
|
|
|
[target.'cfg(windows)'.dependencies]
|
|
lanparty-client-route = { path = "../lanparty-client-route" }
|