Skip to content

Fix socks5 outbound UDP ASSOCIATE - #3841

Open
asoul-rec wants to merge 1 commit into
v2fly:masterfrom
asoul-rec:patch-socks5udp
Open

asoul-rec wants to merge 1 commit into
v2fly:masterfrom
asoul-rec:patch-socks5udp

Conversation

@asoul-rec

@asoul-rec asoul-rec commented Oct 7, 2026 •

Copy link
Copy Markdown

RFC 1928 defines the UDP ASSOCIATE address and port as the client's expected UDP source endpoint. When that endpoint is not known yet, both fields must be zero. Sending the final destination is unexpected. Use 0.0.0.0:0 for UDP ASSOCIATE while preserving the request destination for subsequent UDP packets and leaving TCP CONNECT unchanged.

Use Codex to add handshake regression coverage for IPv4, IPv6, and domain targets, including relay reply parsing and preservation of the original request.

Fixes #3842

RFC 1928 defines the UDP ASSOCIATE address and port as the client's
expected UDP source endpoint. When that endpoint is not known yet,
both fields must be zero. Sending the final destination is unexpected.
Use 0.0.0.0:0 for UDP ASSOCIATE while preserving the request destination
for subsequent UDP packets and leaving TCP CONNECT unchanged.

Use Codex to add handshake regression coverage for IPv4, IPv6, and domain targets,
including relay reply parsing and preservation of the original request.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] SOCKS5 UDP ASSOCIATE发送错误的client ip/port字段

1 participant