v0.69.1
Changed 3
- transport.wireProtocol = "v2" now applies to UDP-based proxy payloads including ordinary UDP and SUDP for consistent payload framing
- Improved SUDP compatibility during mixed transport.wireProtocol deployments to allow frps to bridge payloads between v1/default and v2 SUDP clients
- XTCP work connection NatHoleSid messages now follow the selected transport.wireProtocol
Features
transport.wireProtocol = "v2"now also applies to UDP-based proxy payloads, including ordinary UDP and SUDP, so their payload framing is consistent with the selected wire protocol.- Improved SUDP compatibility during mixed
transport.wireProtocoldeployments, allowing frps to bridge payloads between v1/default and v2 SUDP clients. - XTCP work connection
NatHoleSidmessages now follow the selectedtransport.wireProtocol.
Compatibility Notes
- When enabling
transport.wireProtocol = "v2"for SUDP, upgrade both the proxy and visitor frpc instances first, or keep them onv1until both sides are upgraded.