rustdesk / rustdesk/rustdesk-server
Two different IP ranges fail
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10.4k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
The program does not work when using two different IP ranges.
Describe the environment
Rustdesk seever 1.1.12
Ubuntu 22.04, Ubuntu 24 ...
Mikrotik container
How to Reproduce the bug
I set up an Ubuntu server and installed the server version of the program on it.
My server has two network cards with different IP ranges.
192.168.1.1/24
192.168.2.1/24
On each side of these two networks there are different computers with different IPs. For example:
192.168.1.2
192.168.2.2
All computers connect to the server successfully but there is one problem that they can only connect to the remote control within their own network range and not the opposite network.
Expected behavior
All computers must be able to connect to each other because a server is installed between them and they are all connected to the server.
Additional context
I have completed the installation tutorial via the link below.
https://rustdesk.com/docs/en/self-host/rustdesk-server-oss/install/
Server with two network cards with the following IPs:
192.168.1.1
192.168.2.1
Two computer networks with the following IP ranges:
First Network 192.168.1.2-254
two Network 192.168.2.2-254
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
Start with the RustDesk Server OSS installation tutorial linked in the issue and reproduce the two-network-card setup on Ubuntu. Trace the server's connection handling for clients on 192.168.1.0/24 and 192.168.2.0/24. Done means computers on either range can connect to remote computers on the opposite range.
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
- Mostly clear
- Newbie friendliness
- 28/100