ddidderr
2afdae44c6
The client now builds ClientDiagnostics snapshots from the connected session, known TAP state, route-pinning status, and tunnel counters. Windows prints one snapshot after TAP and relay-route setup, then repeats snapshots while bridging so frame/datagram counters and drops are visible during manual phase-1 tests. Non-Windows builds print the same relay and QUIC diagnostics with TAP fields marked unknown before waiting for Ctrl-C. TAP IP remains unknown until a later Windows adapter IP inspection slice wires that source of truth. Test Plan: - cargo fmt --check - cargo test -p lanparty-client-win - cargo clippy -p lanparty-client-win --all-targets -- -D warnings - cargo test --workspace - cargo clippy --workspace --all-targets -- -D warnings - git diff --check Refs: PLAN.md
18 lines
530 B
TOML
18 lines
530 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-ctrl = { path = "../lanparty-ctrl" }
|
|
lanparty-obs = { path = "../lanparty-obs" }
|
|
lanparty-proto = { path = "../lanparty-proto" }
|
|
tokio.workspace = true
|
|
|
|
[target.'cfg(windows)'.dependencies]
|
|
lanparty-client-route = { path = "../lanparty-client-route" }
|
|
lanparty-client-tap = { path = "../lanparty-client-tap" }
|