ginuerzh 62265b424a fix(handler/socks): bind UDP associate relay socket to BND.ADDR source IP (issue #763) ...

The client-facing UDP relay listener (cc) in handleUDP was bound to the
wildcard address, so replies sent from it used the kernel-selected source
IP (the interface's primary IP), which mismatches the BND.ADDR advertised
to the client (the TCP control connection's local IP). Per RFC 1928 6,
compliant clients drop such replies, breaking SOCKS5 UDP associate under
multiple IP aliases where metadata.interface differs from the primary IP.

Bind cc to the TCP control connection's local IP so its reply source IP
always matches BND.ADDR. The outbound relay socket (pc) already binds the
interface IP via Router.Dial -> dialer.ListenUDP(laddr).

2026-06-13 22:59:42 +08:00

..

bind.go

add context for conn

2025-08-04 19:29:38 +08:00

connect.go

add service option for plugin

2025-08-29 23:36:31 +08:00

handler.go

fix: add status field to service list/detail APIs, unify observeStats retry pattern, fix router bugs

2026-06-03 22:12:08 +08:00

mbind.go

add context for conn

2025-08-04 19:29:38 +08:00

metadata.go

fix(handler/forward): split readTimeout from pipe idleTimeout to prevent 15s download abort

2026-05-31 17:05:21 +08:00

selector.go

fix #866: SOCKS5 nil ptr TLSConfig in selector

2026-06-03 20:17:20 +08:00

udp_tun.go

fix(handler/socks5): accumulate UDP traffic metrics into recorder (issue #45)

2026-06-05 21:16:16 +08:00

udp.go

fix(handler/socks): bind UDP associate relay socket to BND.ADDR source IP (issue #763)

2026-06-13 22:59:42 +08:00