wtf is lunnel?

Lunnel is a tool that lets you expose a service running on your local computer to the public internet, even if your computer is behind a router or firewall that normally blocks outside access. It works as a "reverse proxy," meaning it creates a secure tunnel from your local machine to a public-facing server, so anyone on the internet can reach your local service through that server's address. The setup involves two pieces: a server program you run on a machine with a public IP address, and a client program you run on your local machine. You configure both with a file that tells them how to connect and what traffic to forward. The client reaches out to the server, establishes an encrypted connection, and then funnels traffic through that tunnel. The project supports several protocols including HTTP, HTTPS, TCP, UDP, and Unix sockets, and it can encrypt traffic with either AES or TLS. It also uses a connection pool and multiplexing (similar to HTTP/2) so that a single connection can handle many concurrent requests without wasting resources. A practical example from the documentation: you can run the client locally to expose your Docker daemon's HTTP API, then access it from a browser via a public domain. Another example shows proxying a small web game running in a local container so it's reachable from outside. This makes it useful for developers who want to demo a local app, test webhooks, or manage remote services without setting up complex networking infrastructure. One notable design choice is the automatic switching between TCP and KCP for tunnel transport, which is meant to keep connections stable under different network conditions. The README also mentions planned improvements like a dashboard interface and horizontal server scaling, but those aren't available yet. Configuration is straightforward YAML, though the docs note that tabs aren't allowed in the config file and must be replaced with spaces.