SagerNet / SagerNet/sing-box

[Bug]: macOS Screen Sharing "High Performance" mode fails over sing-box Tailscale endpoint (Direct connection established)

Open
#4,155 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
38.1k
Forks
4.6k
Avg merge
19d 15h
Merged PRs (30d)
1

Description

Operating system

macOS

System version

26.5

Installation type

sing-box for macOS Graphical Client

If you are using a graphical client, please provide the version of the client.

1.14.0-alpha.25

Version

Description

When using sing-box with the Tailscale endpoint, macOS Screen Sharing cannot initiate "High Performance" mode between two remote Macs while "Standard" mode works.

However, using the official Tailscale client under the exact same network environment allows "High Performance" mode to function perfectly.

Image
Troubleshooting

To rule out performance and connection state bottlenecks, the following tests were conducted:

  1. NAT Traversal: Both official Tailscale and sing-box successfully established direct connections (p2p). No DERP relaying was involved.
  2. Throughput Test: iperf3 (both TCP and UDP) shows identical performance and bandwidth between the official client and sing-box. Speed or packet loss is not the bottleneck.
Reproduction
  1. two Macs located on different networks (across the WAN).
  2. configure sing-box on both Macs using the Tailscale endpoint configuration. Ensure a direct connection (STUN/hole-punching successful, no DERP relay).
  3. Launch the Screen Sharing app, try to select "High Performance" mode in the settings.
Logs
No suspicious logs found at TRACE level.
Supporter
Integrity requirements
  • I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
  • I confirm that I have provided the server and client configuration files and process that can be reproduced locally, instead of a complicated client configuration file that has been stripped of sensitive data.
  • I confirm that I have provided the simplest configuration that can be used to reproduce the error I reported, instead of depending on remote servers, TUN, graphical interface clients, or other closed-source software.
  • I confirm that I have provided the complete configuration files and logs, rather than just providing parts I think are useful out of confidence in my own intelligence.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the macOS Screen Sharing app, sing-box's Tailscale endpoint, and two Macs on different networks, then compare it with the official Tailscale client. Use the reported direct p2p connection and iperf3 results as controls; done means High Performance mode works without relying on DERP relaying.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, macos
Domain
networking, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.