A found tunnel carries its MTU to the mesh #28

2026-09-26T20:40:01Z

jschoubben commented

2026-09-26 20:40:01 +00:00

Second gap from the shanks session: the mesh had no MTU concept, so a take silently moved a tuned tunnel (shanks's wg0 sets MTU = 1380) to the 1420 default — invisible to ping, fatal to TLS handshakes and transfers over that path. The host now parses MTU from the found [Interface] and reports it; the controller side (separate PR) carries it into the generated config. Zero when the config named none. Test covers both.

Second gap from the shanks session: the mesh had no MTU concept, so a take silently moved a tuned tunnel (shanks's wg0 sets `MTU = 1380`) to the 1420 default — invisible to ping, fatal to TLS handshakes and transfers over that path. The host now parses MTU from the found `[Interface]` and reports it; the controller side (separate PR) carries it into the generated config. Zero when the config named none. Test covers both.

jschoubben added 1 commit 2026-09-26 20:40:02 +00:00

A found tunnel carries its MTU to the mesh 8e2a1e762d

The host parses MTU from the found [Interface] and reports it, so the
mesh's interface can come up with the same MTU when it takes the tunnel
over. A path tuned to 1380 regresses to the 1420 default otherwise —
invisible to ping, fatal to TLS handshakes and transfers over that path
(novox/hq: the mesh had no MTU concept). Zero when the config named
none, and the mesh writes no MTU line then.

jschoubben merged commit 808e93a477 into main

2026-09-26 20:40:09 +00:00

jschoubben deleted branch feat/a-taken-tunnel-carries-its-mtu

2026-09-26 20:40:09 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#28