Direct connection via VPN

V

vamp

Member
Hello there,

Me again... :)

So i try the program via VPN (I use Tailscale) but seems it not use direct connection. The two device able to access each other with local IP adresses. Other similar app (like a simple RDP connection) are working via VPN.

It would be good to fix it.
 
mirillis

mirillis

Administrator
Staff member
Does the connection work using Connect Anywhere? Maybe you need to set fixed P2P ports for direct connection? It should work (I think some users connect using VPN). If RDP works then the problem is 99% related with ports.
 
mirillis

mirillis

Administrator
Staff member
You can use Wireshark to check the RDP connection what ports are used and then set the same Inbound/Outbound ports in Remotly server and also Outbound port in Android app.
 
V

vamp

Member
Not working... I try to set fix port and also try to set it up the RDP port but go to Connect Anywhere any case. (with Connect Anywhere, it working )

I try to disable firewall on windows but not help at all.
 
mirillis

mirillis

Administrator
Staff member
Hmmm.. that is very strange. We will need to reproduce this in our labs using Tailscale. There are no limitations on our side.
 
V

vamp

Member
mirillis said:
Hmmm.. that is very strange. We will need to reproduce this in our labs using Tailscale.
Click to expand...

I also tried it via plain wireguard (Tailscale also use under the hood) but also not working.
I tried it via android client if help.

Also found a interesting thing. if i set custom port on windows host and set the full different port on android client, the direct connecton work normal, if both machine are same LAN network (without VPN, normal LAN)

Seems if it same LAN, this settings are not do anything, or it bugged and not work android or windows side?
 
mirillis

mirillis

Administrator
Staff member
In LAN the direct connection should always work without any problems. I have never had any problem with direct connection in LAN.
Is there a problem when you set the same ports on Android and PC server?
 
V

vamp

Member
mirillis said:
In LAN the direct connection should always work without any problems. I have never had any problem with direct connection in LAN.
Is there a problem when you set the same ports on Android and PC server?
Click to expand...

i set on windows here:

1688243587311.png

On android, not important what port are set it (42016.42017, 42020...) it work direct connect, if the two device are same LAN.

Seems that android side this settings are not working.
 
mirillis

mirillis

Administrator
Staff member
They work on Android, I use it at home. I need to set a port on Android and then port forward it on my router to connect to our lab. Without setting this port (in this case I use the default 42015) I cannot connect. So it must work. Setting this in local network should not matter. It is intended for port forwarding to allow Direct Connection between networks where routers have firewalls.
 
V

vamp

Member
mirillis said:
They work on Android, I use it at home. I need to set a port on Android and then port forward it on my router to connect to our lab. Without setting this port (in this case I use the default 42015) I cannot connect. So it must work. Setting this in local network should not matter. It is intended for port forwarding to allow Direct Connection between networks where routers have firewalls.
Click to expand...

i will try it with port forward. but not understand.... If i use VPN, not need this.

Edit:

Tried it, no VPN only port forward (42015) on my firewall. Not working. I dont understand...
1688246385077.png
 
Last edited:
mirillis

mirillis

Administrator
Staff member
Are you connecting from 2 different networks? Port forwarding has no sense in the same network.

We will figure it out. But it must work as I use it everyday.

My setup is as follows:
HOME: 1 Router with firewall connected (cable docsis). On this router I have port forwarded 42015 to my Android device with 192.168.10.102 IP.
On the Android app I set the port to 42015 (without it it will not work).
MIRILLIS LAB1: Several routers connected in cascade before reaching Nvidia RTX PC. On the PC I do not force any ports.
 
V

vamp

Member
mirillis said:
Are you connecting from 2 different networks? Port forwarding has no sense in the same network.

We will figure it out. But it must work as I use it everyday.

My setup is as follows:
HOME: 1 Router with firewall connected (cable docsis). On this router I have port forwarded 42015 to my Android device with 192.168.10.102 IP.
On the Android app I set the port to 42015 (without it it will not work).
MIRILLIS LAB1: Several routers connected in cascade before reaching Nvidia RTX PC. On the PC I do not force any ports.
Click to expand...

My test:

My android phone on a regular mobile internet.

My PC are a different network, a optical cable net.

on PC side, i set the firewall (it is NAT on my cabel network) to forward 42015 port to my 192.168.31.102 IP address (it is my PC)

But it is basically not so important, because of my phone and my PC are same VPN, all this things are not really needed, if i use Tailscale or any other VPN sollution.
 
mirillis

mirillis

Administrator
Staff member
I'm also sometimes connecting using mobile network. But in this case direct connection works from time to time (i think it depends on the BTS i'm currently using, if it does not block p2p it works). So i'm also having a similar test case. I will now need to check with VPN.
 
mirillis

mirillis

Administrator
Staff member
BTW soon you will be able to install your own relay server so that direct connection and connect anywhere will work with almost identical latency. This will solve all problems.
 
V

vamp

Member
Meantime i try Sunshine and Parsec again, via Tailscale VPN. It working as escepted. So i think something are working strange on Remotly network discovery, if we use VPN.
 
mirillis

mirillis

Administrator
Staff member
We will try to sort this out as soon as possible. If it works for them it must work for us.
 
V

vamp

Member
Ethernet and Vmware workstation virtual network cards
Maybe there is more than one and Remotly is not using the one it should.
Click to expand...

But it also problem, if my devices are same LAN? In this case, Remotly work well.

Code: 
Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : localdomain
   Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::48fb:1234:ec86:5b8f%18(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.31.102(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 2023. július 2., vasárnap 1:17:14
   Lease Expires . . . . . . . . . . : 2023. július 2., vasárnap 3:17:08
   Default Gateway . . . . . . . . . : 192.168.31.1
   DHCP Server . . . . . . . . . . . : 192.168.31.1
   DHCPv6 IAID . . . . . . . . . . . : 313302551
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-48-C3-F4-AC-9E-17-4D-60-4B
   DNS Servers . . . . . . . . . . . : 192.168.31.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::64e0:4ad9:2714:554f%17(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.26.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 83906646
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-48-C3-F4-AC-9E-17-4D-60-4B
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet8:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::b47c:d671:1610:21ea%2(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.208.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 134238294
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-48-C3-F4-AC-9E-17-4D-60-4B
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled
 
You must log in or register to reply here.
Top