Claude 6a60918cc6 fix(nests): connect over a resolved IPv4 address while keeping hostname SNI ...

After switching the dev harness to `localhost`, the QUIC handshake still
stalled and the relay logged nothing at all — packets weren't reaching
it. `localhost` resolves to ::1 first on most systems, and IPv6 loopback
isn't reliably routable (Docker's IPv6 UDP port-forwarding silently
blackholes), so the UDP socket was connecting into a hole.

QuicWebTransportFactory.connect now resolves the authority host to a
concrete address preferring IPv4 for the UDP socket target, while still
passing the original hostname as the TLS SNI server name — so SNI keeps
matching the server certificate and stays a legal RFC 6066 host_name.

https://claude.ai/code/session_01PoQupfdoKU3ryQwLwTeXeM

2026-05-14 21:51:35 +00:00

..

plans

fix(nestsclient): keep stream priority pack non-negative — Lite-03 priority bit-layout

2026-05-09 15:21:28 +00:00

specs

feat(nests): adopt deployed nostrnests schema (streaming/auth/live + paired 10112)

2026-04-29 19:32:53 +00:00

src

fix(nests): connect over a resolved IPv4 address while keeping hostname SNI

2026-05-14 21:51:35 +00:00

tests

ci(nests): defer cross-stack interop CI; document manual run

2026-05-07 23:18:31 +00:00

build.gradle.kts

diag(nests-interop): per-test moq-relay trace capture for routing race

2026-05-07 18:20:17 +00:00