ginuerzh 9292e0af3e fix(tunnel, forward): route tunneled hostname through hop filter.host ...

The tunnel bind conns (bindConn/bindUDPConn) now expose their metadata (the
tunneled hostname) via the xctx.Context interface, so the service accept loop
forwards it into the handler context. handleRawForwarding selects a hop node by
that hostname when a hop is configured, so a node with a matching filter.host is
picked; otherwise it falls back to dialing the hostname directly. Fixes
reverse-proxy-tunnel TCP routing (gost#898) where the docs example failed with
"node not available" because the mux path never set the host metadata.

2026-08-26 20:28:37 +08:00

..

bind.go

x: wire MetadataFeature (relay v0.7.0) for tunnel recording mode negotiation

2026-07-24 22:19:41 +08:00

conn_test.go

fix(tunnel, forward): route tunneled hostname through hop filter.host

2026-08-26 20:28:37 +08:00

conn.go

fix(tunnel, forward): route tunneled hostname through hop filter.host

2026-08-26 20:28:37 +08:00

connector.go

x: wire MetadataFeature (relay v0.7.0) for tunnel recording mode negotiation

2026-07-24 22:19:41 +08:00

listener.go

feat(mux): make mux layer pluggable and add Yamux backend

2026-07-13 23:12:27 +08:00

metadata.go

x: wire MetadataFeature (relay v0.7.0) for tunnel recording mode negotiation

2026-07-24 22:19:41 +08:00