TCP-Tunneling
TCP-Tunneling
This link talks about setting up a personal VPN server using TCP tunneling. It explains how to configure the necessary settings so that your own network traffic can securely pass through a tunnel. The article also addresses common questions and troubleshooting tips for users trying to implement this setup. If you're unsure, feel free to ask for clarification on any part.
On several projects I manage, AnyDesk is widely used across many servers. It performs reliably. I think TCP tunneling here resembles SSH tunneling—such as for VNC over an SSH connection. I’m not entirely sure, but since it’s AnyDesk, the tunnel might bypass firewalls and be more convenient. Essentially, it creates direct application tunnels instead of a full VPN. For example, to access VNC on a remote machine, you could set up a tunnel like yourip:5010 -- serverIP:5800, allowing connection to that specific server. I don’t recommend this approach for general use. It can become overly complex and is best reserved for situations where you already rely heavily on AnyDesk and can’t install other remote access tools due to policies or restrictions. If you’re interested in learning more about networking, consider setting up SoftEther, ZeroTier, OpenVPN, or SSH JumpHost. If you need assistance with any of these options, feel free to ask.
I suggest you view this video. It will clarify how TCP tunneling functions, though it might not be what you expected. I've applied TCP tunneling on specific public networks that prevent VPN connections. This method allows you to wrap VPN traffic within a standard TCP request to a server or service that isn't restricted by the network or ISP. After the receiving server processes your valid request and recognizes it as intended, it forwards the data to the proper destination.
I’ll make sure to try that, because I was struggling with SoftEther, which is why I checked this out.