You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: