TCP forwarding
Understand both ends, then connect.
01
Provider
Runs the service and creates the invitation.
View steps ↓02
Joining device
Joins and accesses the service through a local port.
View steps ↓Follow the connection
- 01
Provider · Test the service
Access the service locally on its computer. Verify the address, port and authentication.
Check: If local access fails, fix the service first.
- 02
Provider · Create an invitation
Enter the actual target under Advanced, create an invitation and confirm in the app.
Check: The target refers to the providing computer’s service.
- 03
Joining device · Connect
Choose an unused local port, scan or paste the invitation and open the app.
Check: The local access port need not match the target port.
- 04
Joining device · Access
Connect the service client to 127.0.0.1 at the configured local port. Use the original service protocol and credentials.
Check: Verify an actual response. Reconnect after changing settings.
If something goes wrong
Configuration and limits
Before you start
Verify the TCP service works on the providing computer first. A web service actually listening on 127.0.0.1:8080 can use that target. It is not the invitation link or the joining computer’s address.
Connect
The provider enters the target and creates an invitation. The other computer selects an unused local port and joins. Once connected, access that local port, e.g. http://127.0.0.1:2222 for a web service. The original protocol and authentication still apply.
Checks and limits
Each connection maps one TCP port, not all ports or UDP. There is no multi-port management within one session or automatic free-port selection. Settings apply to the next connection. Disconnecting ends the mapping.