Blankwonder 说明 Surge 入站访问的兼容配置及屏幕共享限制
在 Surge TestFlight Feed 的测试版更新说明中，Blankwonder 提醒：Tailscale 与 WireGuard 入站连接参数 accept-incoming 已改名为 allow-peer-access，旧参数仍会被读取以保持兼容。受 Apple 屏幕共享高性能模式特殊通信机制影响，即使启用 allow-peer-access，该模式仍无法使用，专门的绕过方案尚在研究。该帖还说明，Snell v6 的 UDP 数据可紧随隧道命令发送，无需等待服务端响应，从而加快 QUIC 连接，但要求服务端为 v6。
频道原文@SurgeTestFlightFeedBeta Updates
Incoming Connections for Tailscale and WireGuard
- The old parameter accept-incoming has been renamed to allow-peer-access, but it will still be read for compatibility.
- Fixed the issue where incoming UDP packets could not be forwarded when the destination address is the local machine.
- Please note that due to its unusual communication mechanism, Apple Screen Sharing's high-performance mode cannot be used even if allow-peer-access is enabled. We are looking into a dedicated workaround for this.
Ruleset Editor
- You can now disable individual rules in a ruleset with the Enable/Disable swipe action. Disabled rules are saved as commented-out lines.
Improvements
- Snell v6: UDP data is now sent right after the tunnel command, without waiting a round trip for the server's response. QUIC over Snell v6 connects noticeably faster. This requires a v6 server.
- Adaptive QUIC Block: detection now starts only on new QUIC handshakes. Before, packets from QUIC connections that already existed (for example, ones opened before Surge started) could be wrongly remembered as allowed. They are now blocked so that the app starts a new handshake.
- DTLS, WireGuard, STUN and other non-QUIC UDP traffic on port 443 is no longer treated as QUIC, so block-quic no longer affects it.
- When a SOCKS5 proxy rejects a connection, Surge now shows the reason the server gave (such as connection refused or host unreachable) instead of an "invalid response" error.
- Ponte: a device no longer stays stuck in "LAN-only mode" when its record was captured while its remote channels were restarting. Surge refreshes the device list before giving up, and the error message now explains why.
- [Mac] Resolved the issue of needing to repeatedly reactivate when using multiple users or multiple operating systems on the same device. For details, please refer to the knowledge base licensing FAQ to learn about the corresponding methods.
Fixes
- Fixed requests failing with 503 when a server sends a body after a 304 or another response that should have no body (for example, ASUSWRT-Merlin routers).
- [iOS] Fixed high memory use on MITM HTTP/2 connections when the client reads slowly. This could push the network extension past its memory limit.
- [iOS] Fixed a possible network extension crash when viewing the Logbook with very large script records.
- [iOS] Fixed the external resource view sometimes being presented twice.
- [iOS] Fixed text fields in sheets being covered by the keyboard in some sheet sizes, and the space left for the keyboard not always being removed after it was dismissed.
- [iOS] Optimized the keyboard layout for iPhone Duo.