TCP-Tunneling

[carrickwater]

Can someone please explian this to me.  https://support.anydesk.com/TCP-Tunneling I posted some days ago on a thread I made about creating my own home VPN server, and I think this can work, but I don't understand it properly. Thank you.

[Akolyte]

On one of the projects I admin, we use AnyDesk on a lot of servers, and it works quite well.  I believe this TCP tunneling would be similar to using an SSH tunnel (if you have used it) to tunnel applications eg: using VNC over an ssh tunnel.  I'm not 100% certain but because it's AnyDesk the tunnel will probably be able to bypass firewalls and be convenient in that way I suppose. 

 

To explain this, it's more like creating direct tunnels for applications rather than using a VPN.  If you only wanted that remote access to let's say, VNC into a computer on the network, this would be good, as you could create a tunnel yourip:5010 -- serverIP:5800. Which now means you can connect to serverIP/AndeskID:5010.  

 

I think for general purposes, I do not recommend using this. It seems overly complicated, and should only be used if: 

• You use AnyDesk for many servers already, and cannot install or configure new remote access software/methods because of policy or access limitations. 
• You would like to use one service (eg: FTP, VNC) between two computers only and potentially through a firewall. 

 

My personal advice, as I recently recommended in another networking post, is SoftEther or ZeroTier.  If you would like to learn a lot about networking, you can also set up OpenVPN, or a SSH Jumphost. 

 

If you need any help with any of these, or if I can help further in any way, just gimme a ping. 

[ddennis002]

1 hour ago, carrickwater said:

Can someone please explian this to me.  https://support.anydesk.com/TCP-Tunneling I posted some days ago on a thread I made about creating my own home VPN server, and I think this can work, but I don't understand it properly. Thank you.

I recommend you watch this video. This will explain how TCP tunneling works, most likely this isn't what you want.

 

I have used TCP tunneling on certain open networks out in public that block VPN's from connecting. So you can use TCP tunneling to encase the VPN traffic into a legit TCP request to server or service that isn't blocked by the network or ISP ect. Once the receiving server receives your legit request and unpacks it and sees that that traffic is intended for that server and forwards the payload to the intending server.

 

 

[carrickwater]

1 hour ago, Akolyte said:

On one of the projects I admin, we use AnyDesk on a lot of servers, and it works quite well.  I believe this TCP tunneling would be similar to using an SSH tunnel (if you have used it) to tunnel applications eg: using VNC over an ssh tunnel.  I'm not 100% certain but because it's AnyDesk the tunnel will probably be able to bypass firewalls and be convenient in that way I suppose. 

 

To explain this, it's more like creating direct tunnels for applications rather than using a VPN.  If you only wanted that remote access to let's say, VNC into a computer on the network, this would be good, as you could create a tunnel yourip:5010 -- serverIP:5800. Which now means you can connect to serverIP/AndeskID:5010.  

 

I think for general purposes, I do not recommend using this. It seems overly complicated, and should only be used if: 

• You use AnyDesk for many servers already, and cannot install or configure new remote access software/methods because of policy or access limitations. 
• You would like to use one service (eg: FTP, VNC) between two computers only and potentially through a firewall. 

 

My personal advice, as I recently recommended in another networking post, is SoftEther or ZeroTier.  If you would like to learn a lot about networking, you can also set up OpenVPN, or a SSH Jumphost. 

 

If you need any help with any of these, or if I can help further in any way, just gimme a ping. 

I'll be sure to do that, since I was having problems with SoftEther, that's why I looked at this.