feat(ctrl): report connection mode in welcome
PLAN.md calls out room modes such as relay, direct-p2p, and relay fallback so future transport choices can fit the protocol. Add an explicit ConnectionMode field to ServerWelcome and default it to relay for existing decoded welcomes. The relay still operates only in relay mode today. Client and gateway startup logs now print the selected mode, which makes the current relay path visible without changing routing or forwarding behavior. Test Plan: - cargo fmt --check - cargo test -p lanparty-ctrl server_welcome -- --nocapture - cargo test -p lanparty-client-win -p lanparty-gateway - cargo test --workspace - cargo clippy --workspace --all-targets -- -D warnings - git diff --check Refs: PLAN.md
This commit is contained in:
@@ -113,10 +113,11 @@ async fn main() -> Result<()> {
|
||||
|
||||
let session = connect_client(config).await?;
|
||||
println!(
|
||||
"lanparty-client-win connected as peer {} in room id {} with TAP MTU {}; LAN gateway connected {}",
|
||||
"lanparty-client-win connected as peer {} in room id {} with TAP MTU {} over {}; LAN gateway connected {}",
|
||||
session.welcome().peer_id(),
|
||||
session.welcome().room_id(),
|
||||
session.welcome().effective_tap_mtu(),
|
||||
session.welcome().mode(),
|
||||
yes_no(session.welcome().gateway_connected())
|
||||
);
|
||||
#[cfg(windows)]
|
||||
|
||||
Reference in New Issue
Block a user