How it works

This section is still under development.

schematic

Your IoT device connects to the tnnl server over HTTPS using the tnnl-client. You can then access your device seamlessly through the tnnl server.

    
    graph TD;
        server["tnnl Server"]
        subgraph "IoT Device"
        connector["tnnl-client"]
        end
    subgraph "User";
        client["Web Browser"]
        ssh["SSH Client"]
    end
    server -. "https (TLS)" .- connector
    server -. "https (TLS)" .- client
    server -. "SOCKS" .- ssh

Since you usually do not want everyone to view your device over the internet you have fine-grained access control via the tnnl Administrator. The intuitive web interface allows you to…

  • … show the connection status of all your devices
  • … temporarily enable/disable incoming connections completely
  • … add password protection to the connection

Bridge mode

In some situations you might want to use a device like a notebook as a bridge between your IoT device and the tnnl sever.

    
graph TD
    server["tnnl Server"]
    subgraph "IoT Device"
        connector["tnnl-client"]
    end
    subgraph "Consumer"
        client["Web Browser"]
        ssh["SSH Client"]
    end
    subgraph "Service PC"
        browser["tnnl-bridge"]
    end;
    server -. " https (TLS)" .- browser
    browser -. "https  (TLS) / http" .- connector
    server -. "https (TLS)" .- client
    server -. "SOCKS" .- ssh

To run the tnnl-bridge all you need is a web browser. See Usage for more information.