NanumOS

Wire — the network that joins your devices

What it is

Wire is your own private network that joins your devices (laptop, phone, servers, NAS) as if they were all in one house, wherever they are. Think of one building where every device has its own room number: at a cafe or at home, you say the name of the "living-room computer" and that door opens. Nobody else can enter. Only devices that you (or the person who runs the network) approved can join.

What to do now: if a network already exists, press "Join a network I already have" in the Wire app. If not, skip it — NanumOS works fully without Wire.

Basics — a private network, WireGuard, and three roles

A private network. The internet is a big city and each device is a house in a different neighborhood. A private network lays a tunnel only you can use between those houses, so a faraway device can be reached like the one next door. Everything inside the tunnel is locked, so nobody on the way can read it.

WireGuard. The current standard way to lock that tunnel. Each device makes a pair of keys (one public, one private); when two devices swap only their public keys, an encrypted tunnel opens between them. The rules are few and the code is small, so it is fast and easy to check. NanumOS's Wire speaks real WireGuard — it is checked against other WireGuard programs by handshake and transfer tests. Swapping keys by hand gets tiring as devices are added, so a separate meeting point does that job.

Three roles, and why each exists.

Services of the same shape

How to use it

The same screens appear in two places — the Wire app and Settings › Wire. The Wire icon in the top menu bar turns it on and off and lists your devices at a glance.

  1. Top — a big Connect / Disconnect switch and "Connected · 10.98.x.x". Disconnecting only steps out for a while (you stay a member); connecting again brings everything back.
  2. My devices — each device shows an online dot and "n min ago", its name, an OS icon, its address (tap to copy), a "this device" tag and a Direct / Relay badge. Tap a device for Show screen (remote screen), Terminal (ssh), Send a file and Copy address.
  3. Make a new network — for someone without a coordinator yet: on an always-on Linux computer run one line, wire init (there is a copy button).
  4. Add a device — when this device is already in, it shows how another device joins (one wire up --server … line and a QR of it).
  5. Remove this device from the network — a confirm card comes first (Cancel is the default). After removal this device forgets its key; joining again needs a fresh approval.
  6. Send nearby — sending files to a device on the same network. It is not in this version yet; until then use scp with the names Wire gives you.

The "Wire network" row in the checkup (os_check) shows on/off, my address, the coordinator's state and the device count.

How it works

The order in which a device joins.

  1. The device makes a key pair (the private key never leaves it).
  2. It asks the coordinator "may I join?". The coordinator answers with a QR address and an 8-character code.
  3. The coordinator registers this device's name, address and public key, and the device receives the list of the others.
  4. The two devices try to connect directly, and fall back to a relay if that fails. The list is fetched again every 30 seconds.

Why it is built this way.

Good to know. Without a coordinator, WireGuard devices still work if you swap keys by hand (wg and wg-quick can do it). The coordinator only takes that chore over; it does not make the tunnel safer.

Coordinator, relay, keys — at a glance

Try it yourself

  1. Open the Wire app and join a network with two or more devices online (step 3 above).
  2. In "My devices" look at the Direct / Relay badge of each device. Devices on the same home Wi-Fi show Direct.
  3. Move one device to phone data (away from home) and watch whether its badge changes after a moment. If it turns to Relay the round trip may be a little longer.
  4. Tap a device, choose "Terminal", and type ping NAME in the window that opens.
Technical details
  • Protocol: WireGuard-compatible (Noise_IKpsk2, X25519, ChaCha20-Poly1305, BLAKE2s). In NanumOS it lives in the kernel as wire0 (checked against other WireGuard programs by handshake and transfer tests). The mesh address is in a private address range (shown by wire status), MSS 1380, keepalive 25 s.
  • Ports: coordinator TCP 8790 (default, configurable, plain HTTP only in this version) · nodes and relays UDP 51820 (default; a NanumOS node uses the port it got when joining).
  • Coordinator protocol (the part NanumOS supports): easy join /join/start and /join/poll (passkey approval, 10-minute expiry), signed /register (Ed25519), /peers every 30 s (10 s after a failure), name registration. Each device reports its endpoints (outside, same-router, opened port) and chooses direct or relay. Not yet: NanumOS starting the hole punch itself, automatic port opening, access rules (ACL), route advertisement, exit node, a key-rotation command, TLS. Phone and Linux nodes do punch.
  • Files and commands: /etc/wire/config (root 0600), the # wire-managed block in /etc/hosts (name → address), wire status|join|up|down|leave|ssh-config, wg and wg-quick (WireGuard by hand, no coordinator), /proc/wire (state and numbers, no keys; in mesh mode coord=, sync_age_s=, sync_error=, peer.N=name address direct|relay|none via last-seconds rtt-ms; while joining join=, join_url, join_code, join_left_s, join_error; when off joined=, default_server).
  • Assistant tools: wire_status (read-only) · wire_join (QR card, no approval card) · wire_leave (confirm card) · the os_check "Wire network" row · explanations from os_help.
  • Limits: one tunnel at a time (wire and wg-quick cannot both be on), one network at a time. Auto-start at boot is auto 1 in /etc/wire/config.

NanumOS 0.1.8349 · 2026-11-16