mrambossekandClaude Fable 5 ce1aaa332a server: send granted traffic from the address the session actually used ...

fmr binds two IPv4 addresses. connFor picked whichever socket of the right
family came first in the bind list, so a downtrain for a session established on
.150 went out from .151 — and every packet was dropped by the client's NAT,
which has no mapping for that pair. tcpdump on the server showed all 50 leaving;
the client saw none. Read as "100% downstream loss", which is the worst kind of
wrong: a confident measurement of something that never happened.

Sessions now record which of our own bound addresses received their traffic, and
granted sends (and delayed echo) go back out through that socket. The fallback
to a family match is kept for the case where nothing has been received yet, and
the test pins both paths — a single-homed lab can never reproduce this.

Also: the client-side halves of the same work — anonymizer (core-privacy), local
run archive with retention (core-archive), upload client, and the app's settings
and history screens.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-01 10:45:43 +02:00

..

debug/res

app: link.ra_source router identification + brand icons + DEV build variant

2026-08-01 09:35:54 +02:00

main

server: send granted traffic from the address the session actually used

2026-08-01 10:45:43 +02:00