ginuerzh 03f4b1291e fix(handler): use addr-family-specific network for SOCKS5 BIND (#621) ...

When the SOCKS5 BIND request carries an IPv4 address (e.g. 0.0.0.0:0),
pass the network as "tcp4"/"udp4" instead of "tcp"/"udp". On Linux,
net.Listen("tcp", "0.0.0.0:0") creates a dual-stack IPv6 socket
binding on [::]:port, so the bound address returned to the client
mismatches the actual listening socket. Same fix for CmdMuxBind and
CmdUDPTun. CmdConnect is left unchanged since dual-stack dialing is
correct for outbound connections.

2026-06-22 19:18:46 +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(handler): use addr-family-specific network for SOCKS5 BIND (#621)

2026-06-22 19:18:46 +08:00

mbind.go

add context for conn

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

metadata.go

feat(socks5): add udp.resolveDomain option for clients incompatible with ATYP=Domain

2026-06-21 15:12:53 +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

feat(socks5): add udp.resolveDomain option for clients incompatible with ATYP=Domain

2026-06-21 15:12:53 +08:00