The setup library

Localtonet camera access without port forwarding

On this page

Localtonet runs a client on an always-on device in your camera network. The client opens an outbound connection to a Localtonet relay, which gives one camera service a public address without a router port forward. You still choose the service, protect it with a strong camera login and test it from another network.

Localtonet camera access without port forwarding. CameraViewer editorial cover with the house and camera lens logo.

How a Localtonet tunnel reaches your camera

Localtonet logo

Port forwarding opens an inbound path through your router. Localtonet reverses the direction. Its client runs on a computer or supported device that can already reach the camera. In the words of Localtonet's camera guide, "the client establishes an outbound connection to a Localtonet relay server." The relay then gives the camera service a public address.

That design puts three parts in the path: the camera, the client device and Localtonet's relay. Each one has to stay up. The guide states that the endpoint "is usable only while the selected client is connected and the tunnel is running." A laptop that sleeps or a mini PC that loses Wi-Fi ends remote access, even while the camera stays powered.

Pick a client device that stays on and stays on the camera network. The Localtonet documentation lists clients for Windows, macOS, Linux, Docker and Android. Its installable DEB and RPM packages for Linux require systemd 247 or newer and OpenSSL 3; portable Linux builds are listed separately. Give the camera a reserved local address in your router, because a tunnel keeps pointing at the old address if the camera's address changes.

Start with a local address that already works

A tunnel forwards one address and port. It cannot fix a wrong stream path or a codec the viewer lacks. Get the camera working on your home network first.

Write down the camera's local address, port and stream path, and keep the username and password out of that note. Localtonet's guide warns that "camera ports are not universal," so take the port from the camera's documentation or a working local setup. You can paste a credential-free version into our stream address checker to inspect the format before you build the tunnel. The checker runs in your browser and makes no connection to the camera. If you still need to assemble the address, the RTSP URL builder and the RTSP setup guide cover the pieces.

Match the tunnel type to the camera service

Localtonet's documentation describes HTTP/s, TCP, UDP and combined UDP/TCP tunnels, along with TLS, file server and proxy options. The camera guide asks readers to start with "the smallest documented service required for the task." Here is how we read its advice for common camera services.

Camera serviceTunnel typePublic sideWhat to check
Web settings pageHTTPHTTPS addressThe page may load video or controls from other ports or private addresses
RTSP stream over TCPTCPHost and portYour viewer must accept a custom host and port, media must stay on TCP, and a free TCP tunnel has a 30-minute timeout
RTSP with UDP mediaNo simple matchDepends on designMedia ports are negotiated per session, so switch the viewer to RTSP over TCP or use a VPN
ONVIF discoveryNoneNot reproducedEnter the public host and port by hand, and expect trouble if the camera returns private stream addresses

Create one tunnel for the one service you need. A remote viewer that only plays the stream does not need the settings page exposed as well.

Decide who can reach each endpoint

Your camera's login is the one guard every tunnel type keeps. Localtonet's guide says to "keep authentication enabled, use unique credentials, expose only necessary services," and to replace default credentials before creating remote access. Use a camera account that can view but not change settings, if the camera offers one.

HTTP tunnels can add a second gate. Localtonet's single sign-on documentation describes "a security layer in front of your HTTP tunnel." Visitors sign in through a provider such as Google, GitHub or Microsoft, or with a username and password, before any request reaches the camera page. Localtonet's homepage lists a username-and-password option in the free plan and SSO in the pay-as-you-go plan.

TCP and UDP tunnels give a public host and port. We found that sign-in layer documented for HTTP tunnels only. Treat an RTSP stream on a TCP tunnel as reachable by anyone who finds the host and port, with the camera login as its only check unless you add IP whitelisting, which limits which source addresses can connect. The homepage lists IP whitelisting among its pay-as-you-go features, and Localtonet's team told us it is available as an additional option for TCP-based RTSP streams. If your phone's network address changes often, a VPN route may suit an RTSP stream better than an open port.

Two more items belong to you. Protect the Localtonet AuthToken, which the camera guide says identifies the client device and should never appear in screenshots, scripts or support posts. Know that your video passes through Localtonet's relay. The homepage describes an encrypted tunnel from your device to Localtonet's servers. Past the relay, a plain rtsp:// stream travels as the camera sends it, without the TLS-protected rtsps scheme defined in RFC 7826. That leg can carry the camera login too, so use a password you use nowhere else. Read Localtonet's terms and privacy policy before you send a camera feed through any third-party service.

Check the plan limits against how you watch

Localtonet's homepage lists a free plan with one HTTP, TCP or UDP tunnel, 1 GB of data per month and a 30-minute tunnel timeout. Localtonet's team told us by email on November 7, 2026, that this automatic timeout applies to TCP, UDP, TLS and proxy tunnels, and that standard HTTP tunnels are exempt. For a camera, that means a free standard HTTP tunnel to the web settings page is exempt from the timeout. An RTSP stream on a free TCP tunnel is covered, so it may stop during longer viewing. Live video also uses data the whole time it plays. Those limits suit a short test. For regular viewing, compare your viewing time with the current plan list, which shows paid tunnels without a timeout. Plans change, so read the live page before you rely on any of these numbers.

Test from a different network

Leave your home Wi-Fi for the test. Mobile data on your phone works. Localtonet's guide explains that staying on the same network "does not prove that the public endpoint works."

Next steps:

  1. Confirm the Localtonet client shows connected and the tunnel shows running.
  2. Open only the public address Localtonet assigned.
  3. Check that the camera still asks for its login.
  4. Watch live video for several minutes, past the first frame.
  5. Close the viewer, reopen it and connect again.

Record each result in a short table with the network, address, stream path and outcome. If the login works but video fails, compare it with your local result and work through the connection troubleshooting steps.

When a VPN fits better

A tunnel suits one known service at one address. A VPN gives a phone a private route into the whole camera network. Localtonet offers its own VPN Manager, which its camera guide describes as a separate private mesh VPN feature. Our user-managed VPN guide covers that route and how to test it. Consider a VPN when you need several camera services, recorder access or ONVIF tools that accept a manual address, or when you would rather keep the stream off a public port.

The CameraViewer app is still in development. It targets direct connections to camera addresses you can reach, and it has not been tested with a Localtonet endpoint.

Common questions

Does a Localtonet tunnel replace the camera password?

No. Localtonet's camera guide tells readers to keep camera-side authentication enabled and replace default credentials before creating remote access. Its sign-in layer is documented for HTTP tunnels, so an RTSP stream on a TCP tunnel depends on the camera login unless you can also restrict source addresses.

Can I find my camera with ONVIF discovery through the tunnel?

No. Localtonet's guide says a tunnel to one unicast address and port does not reproduce the original multicast or broadcast domain. Enter the public host and port Localtonet assigns, if your viewer accepts a manual address. An ONVIF client can still fail if the camera replies with stream addresses on its private network.

Sources and limits

Sources (6 documents)
CameraViewer product team: CameraViewer development brief

Owner-supplied brief · App behavior not independently tested

Publication date: Not stated · Development brief

Simulator captures demonstrate manual RTSP setup, decoded H.264 fixture video, saving a camera and full-screen viewing.

Owner-supplied brief; screenshots have not been independently examined here. Test media demonstrates app behavior, not physical-camera compatibility.

Read the source ↗
Localtonet: Access an IP Camera Remotely Without Port Forwarding

Current source review pending

Publication date: Not stated · Manufacturer or standards documentation

The client establishes an outbound connection to a Localtonet relay server.

Provider guidance for its own tunnels. Not tested here with a physical camera, and no app connection through Localtonet is asserted.

Read the source ↗
Localtonet: Localtonet Documentation

Current source review pending

Publication date: Not stated · Manufacturer or standards documentation

you can use it to create HTTP/s, UDP, TCP, and UDP/TCP tunnels

Lists provider tunnel types, clients and package requirements. Does not establish camera compatibility or remote viewing results.

Read the source ↗
Localtonet: SSO (Single Sign-On)

Current source review pending

Publication date: Not stated · Manufacturer or standards documentation

Localtonet implements SSO as a security layer in front of your HTTP tunnel

Describes sign-in for HTTP tunnels; no equivalent layer for TCP or UDP was found. Plan availability comes from the homepage plan list.

Read the source ↗
Localtonet: Localtonet

Current source review pending

Publication date: Not stated · Manufacturer or standards documentation

30 min Tunnel Timeout

Provider plan list observed on the checked date; plans can change. The list does not name the tunnel types the timeout covers; Localtonet's team clarified by email on 2026-11-07 that it applies to TCP, UDP, TLS and proxy tunnels and that standard HTTP tunnels are exempt. Encryption is reported as the provider describes it, not independently verified; no price or performance claim.

Read the source ↗
IETF / RFC Editor: RFC 7826: Real-Time Streaming Protocol Version 2.0

Current source review pending

Publication date: 2016-12 · Manufacturer or standards documentation

the "rtsps" scheme identifier MUST be used to signal RTSP over TLS.

Protocol specification. Does not show which cameras or viewers support rtsps, or how any tunnel provider handles traffic.

Read the source ↗