v0.69.1

hongfz16/EVA3Dv0.69.1Jun 1, 2026by fatedier

AI Summary

This release extends the v2 wire protocol support to UDP-based proxies, including SUDP and XTCP, ensuring consistent payload framing across different transport types. It introduces improved compatibility for mixed deployment environments and ensures message consistency. Users are advised to upgrade both proxy and visitor instances simultaneously when enabling v2 protocol for SUDP.

Key Highlights

`transport.wireProtocol = "v2"` now applies to UDP-based proxy payloads, including ordinary UDP and SUDP.
Improved SUDP compatibility allows frps to bridge payloads between v1 and v2 clients in mixed deployments.
XTCP work connection `NatHoleSid` messages now strictly follow the selected `transport.wireProtocol`.
Users must upgrade both sides simultaneously when enabling v2 protocol for SUDP to avoid connectivity issues.

New Features

UDP-based proxy payloads now support the v2 wire protocol for consistent framing.
Enhanced SUDP bridging capability for mixed v1 and v2 deployments.
XTCP `NatHoleSid` messages are now aligned with the selected wire protocol.

Full Release Notes

## 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.wireProtocol` deployments, allowing frps to bridge payloads between v1/default and v2 SUDP clients.
* XTCP work connection `NatHoleSid` messages now follow the selected `transport.wireProtocol`.

## Compatibility Notes

* When enabling `transport.wireProtocol = "v2"` for SUDP, upgrade both the proxy and visitor frpc instances first, or keep them on `v1` until both sides are upgraded.