ddidderr/softlan-vpn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: align lifecycle test output

Browse Source 
Update the lifecycle sanity check to match the client output shape. Gateway
state changes are reflected in the periodic `client diagnostics:` line, and the
user-facing missing-gateway diagnostic is printed as a warning.

This keeps the manual Windows E2E guide from asking the tester to find exact
standalone lines that the current client does not emit.

Test Plan:
- git diff --check
- git diff --cached --check

Refs: MVP E2E handoff
This commit is contained in:
ddidderr
2026-05-22 08:25:36 +02:00
parent 1a98b8c4a7
commit 40be47af27
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TESTING.md
+6 -4
View File
@@ -288,8 +288,8 @@ Expected client output:
```text ```text
relay event: LAN gateway disconnected (peer ..., Normal) relay event: LAN gateway disconnected (peer ..., Normal)
gateway connected no client diagnostics: relay reachable yes gateway connected no ...
Waiting for LAN gateway Warning: Waiting for LAN gateway
``` ```
2. Start the gateway again with the same relay, room, cert, and interface. 2. Start the gateway again with the same relay, room, cert, and interface.
@@ -298,11 +298,13 @@ Expected client output:
```text ```text
relay event: LAN gateway connected as peer ... relay event: LAN gateway connected as peer ...
gateway connected yes client diagnostics: relay reachable yes gateway connected yes ...
Connected to LAN gateway Connected to LAN gateway
``` ```
After the reconnect, repeat one quick `ping -S <tap-ip> <lan-host-ip>`. The diagnostics line is periodic, so it may appear up to one diagnostics
interval after the lifecycle event. After reconnect, repeat one quick
`ping -S <tap-ip> <lan-host-ip>`.
## Useful Log Signals ## Useful Log Signals