web-2 (BR2) often cannot reach the members' channel of web-1/web-3 while WireGuard handshakes work #119

New issue

Closed

opened 2026-10-09 01:42:53 -03:00 by marcos-mendez · 0 comments

marcos-mendez commented

2026-10-09 01:42:53 -03:00

(Migrated from github.com)

Real nodes, keel 0.23.7 (N3). member fd11:a58a:88ef::1 did not answer: [fd11:a58a:88ef::1]:51821 did not answer: timed out at 04:19, 04:21 and 04:37. The wg handshakes are fresh. Sync on web-2 then learns nothing. BR2 is the far site: check the channel's connect/read timeouts against decision 0050 (250 ms RTT with loss), the TLS handshake round trips, and MTU on the BR1-BR2 path (a large TLS record may need PMTU discovery across wg0).

Real nodes, keel 0.23.7 (N3). `member fd11:a58a:88ef::1 did not answer: [fd11:a58a:88ef::1]:51821 did not answer: timed out` at 04:19, 04:21 and 04:37. The wg handshakes are fresh. Sync on web-2 then learns nothing. BR2 is the far site: check the channel's connect/read timeouts against decision 0050 (250 ms RTT with loss), the TLS handshake round trips, and MTU on the BR1-BR2 path (a large TLS record may need PMTU discovery across wg0).