// glossary

Tunneling

Tunneling encapsulates one network protocol inside another, typically to traverse a firewall or NAT, or to add encryption.

Tunneling is a generic networking concept. SSH tunnels (ssh -L, ssh -R) carry arbitrary TCP through an SSH session. VPNs tunnel IP packets through TLS or WireGuard. Reverse tunnels carry HTTP/TCP from a public relay back to your localhost.

The 'tunnel' terminology comes from the encapsulation: traffic enters one side, gets wrapped in another protocol's framing, exits the other side, gets unwrapped. The wrapper protocol is typically chosen because the firewall in the middle allows it (HTTPS or SSH almost always pass).

Reverse-tunnel-as-a-service products like lrok and ngrok specifically tunnel HTTP/TCP between a public hostname and a private localhost. The 'reverse' indicates the agent (private side) initiates the connection, not the public side.

Read more

// shipping?

lrok gives your localhost a public HTTPS URL with a reserved subdomain on the free plan. Useful when this term comes up in a real integration:

$ curl -fsSL https://lrok.io/install.sh | sh
$ lrok http 3000

← all glossary terms