rustdesk / rustdesk/rustdesk-server
Misleading connection readiness indicator while split-tunneling VPN on self hosted server
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10.4k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Bug Description
When my Self-hosted server started using VPN Split-tunneling (active on every port save 21115-9), the indicator light at the botttom left of the GUI on the client machine signals Not ready. However, the connection works perfectly.
How to Reproduce
Enable vpn split tunneling on a rustdesk server. Then check the client machine for the indicator at the bottom right.
Expected Behavior
Signaling Green - ready.
Operating system(s) on local (controlling) side and remote (controlled) side
OSX -> Ubuntu 24 Desktop
RustDesk Version(s) on local (controlling) side and remote (controlled) side
1.1.15 -> 1.1.15
Screenshots
Additional Context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with VPN split-tunneling enabled on a self-hosted RustDesk server, using the reported macOS-to-Ubuntu setup and RustDesk 1.1.15 on both sides. Trace how the client determines connection readiness when ports other than 21115-21119 use the VPN. Done means a working connection reports a green ready indicator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100