உள்ளடக்கத்திற்குச் செல்
Localtonet Localtonet டாஷ்போர்டு

இந்தப் பக்கம் இன்னும் தமிழ் மொழியில் கிடைக்கவில்லை. ஆங்கிலத்தில் காட்டப்படுகிறது.

Carry TCP and UDP in one tunnel

இப்பக்கத்திற்கு உதவி
இந்தப் பக்கத்தில் 7 பிரிவுகள்
  1. When to use it
  2. Before you start
  3. Steps
  4. Open the TCP - UDP page
  5. Fill in the form
  6. Start the tunnel and share the endpoint
  7. What is different from a TCP tunnel
  8. On the Free plan
  9. Troubleshooting
  10. Related pages

A UDP - TCP tunnel forwards both protocols through one tunnel and one server port. Use it when a service needs TCP and UDP on the same port, for example a game server.

When to use it #

Your serviceCreate
Uses only TCP, such as SSH, a database or a web serverA TCP tunnel
Uses only UDPA UDP tunnel
Uses TCP and UDP on the same port number, such as Minecraft Bedrock Edition, or a DNS server that answers on port 53 over bothA UDP - TCP tunnel

With one mixed tunnel, clients use a single host name and a single port for both protocols. Two separate tunnels would each get their own server port, so the TCP and the UDP side would no longer share a port number.

Before you start #

  • The Localtonet client is installed on the device and connected with an AuthToken. If it is not, follow the Quick start.
  • Your service listens on the same local port for TCP and UDP. The tunnel has one Local port field for both.

Steps #

  1. Open the TCP - UDP page #

    Open My Tunnels › TCP - UDP and select Create TCP - UDP Tunnel.

  2. Fill in the form #

    FieldWhat to enter
    ProtocolUDP - TCP
    Device tokenThe token used by the Localtonet app on your device.
    Server regionChoose a region close to your device for lower latency.
    Local IP address127.0.0.1 when the service runs on the same device as the client.
    Local portThe port your service listens on for both protocols.
    URL type and DomainRandom subdomain on localto.net works right away. Custom subdomain needs Balance.

    Select Create tunnel.

  3. Start the tunnel and share the endpoint #

    Select the start button in the Actions column. The URL column shows the endpoint as <SUBDOMAIN>.localto.net:<SERVER_PORT>. The Protocol Type column shows UDP_TCP. Clients use the same host and port whether they connect over TCP or over UDP.

What is different from a TCP tunnel #

TopicUDP - TCP tunnel
Server port and Is Reserved?One server port serves both protocols. It behaves as on the TCP page: assigned at the first start, and fixed across restarts only when it is reserved, which needs Balance.
Is SslStream? and Proxy Protocol?Offered, as for TCP. They act on the TCP connections of the tunnel. UDP packets are forwarded as they are.
Show SSH CommandNot offered. Starting a tunnel with plain SSH works for HTTP and TCP tunnels only.
Other settingsThe same as for TCP. See the settings table on the TCP page.

On the Free plan #

The tunnel counts as one tunnel. Like TCP and UDP tunnels it stops after 30 minutes on the Free plan, and you select Start to begin another session. The server port is not reserved without Balance. See Plans and Balance.

Troubleshooting #

One protocol works, the other does not

The tunnel forwards both protocols to the same local port. Check that your service really listens on that port for TCP and for UDP. If the service uses different port numbers for the two protocols, create a separate TCP tunnel and UDP tunnel, one for each port.

The endpoint stopped working after a restart

The server port was not reserved and changed. Copy the new endpoint from the URL column, or reserve the port as described under Reserved port on the TCP page.

இந்தப் பக்கம் குறித்து உதவி வேண்டுமா? சமூகத்திடம் கேளுங்கள் அல்லது ஆதரவு டிக்கெட்டைத் திறங்கள்.

ஆதரவு