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.
- The coordinator (안내소 — the meeting point). It is the phone book and front desk: which device has which name and public key, and where it is now. It checks the approval when a new device joins and tells each device the names, addresses and public keys of the others. Everyone must be able to find it, so it needs an always-on computer reachable from everywhere (for example a small rented server, a VPS). It knows names, public keys and approvals only — it never sees your data and your data never passes through it.
- The relay. When two devices both sit behind home routers (NAT), they sometimes cannot find each other's door. Only then, a device with a public address acts like a post office and forwards the already-locked bytes unchanged. It cannot open them, so it cannot read them.
- Direct connections. The default is device to device. The coordinator tells each side the other's outside address and both knock at once to open a path through their routers (hole punching). When that works it is the fastest; the relay is the fallback.
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.
- 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.
- 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.
- 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). - 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). - 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.
- Send nearby — sending files to a device on the same network. It is not in this version yet; until then use
scpwith 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.
- The device makes a key pair (the private key never leaves it).
- It asks the coordinator "may I join?". The coordinator answers with a QR address and an 8-character code.
- The coordinator registers this device's name, address and public key, and the device receives the list of the others.
- 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.
- The coordinator only points the way. A guide who shows the road does not carry the traveler's luggage. Your data travels only between devices and never passes the coordinator, so a hacked coordinator leaks no content and a slow one does not slow transfers.
- Once connected, each device remembers the other's address and key, so if the coordinator goes down briefly, devices that are already linked keep working. Only new devices joining and changed addresses are paused.
- Everyone runs their own coordinator, so no account at someone else's service is needed, and your network survives if any service disappears.
- WireGuard is a short specification, so NanumOS speaks it directly in the kernel. The protocol with the coordinator is only a subset of the Go Wire client's — what works today is listed under "Technical details".
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
- Coordinator (안내소, 조정 서버): knows who is where. When a new device joins it checks the approval and tells each device the names, addresses and public keys of the others, refreshed every 30 seconds. Your data does not pass through it. If it goes down, devices that are already linked keep working — only new joins and changed addresses pause.
- Relay (우회로, 중계 서버): used only when a direct path cannot be opened; a device with a public address does it. If a relay goes down only the devices going through it drop; direct links are unaffected.
- Direct is the default, relay the last resort. For two devices behind home routers the coordinator tells each the other's outside address and both knock at once to open a path (hole punching). Carrier-shared addresses and routers that change the address every time (symmetric NAT) are hard and use the relay. A relay nearby is fast; a faraway one lengthens the round trip.
- Keys and privacy. The private key never leaves the device (
/etc/wire/config, root only). The coordinator knows public keys, names and addresses only. A relay forwards already-encrypted bytes, so it cannot read them. The assistant also never sees keys or a peer's outside address, only the way (direct/relay) and the time. - Per device it is one of Direct, Relay (via which device), or No path — no path means the device is off, or has no public address or open port for a relay to reach.
Try it yourself
- Open the Wire app and join a network with two or more devices online (step 3 above).
- In "My devices" look at the Direct / Relay badge of each device. Devices on the same home Wi-Fi show Direct.
- 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.
- Tap a device, choose "Terminal", and type
ping NAMEin 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 bywire 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/startand/join/poll(passkey approval, 10-minute expiry), signed/register(Ed25519),/peersevery 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-managedblock in/etc/hosts(name → address),wire status|join|up|down|leave|ssh-config,wgandwg-quick(WireGuard by hand, no coordinator),/proc/wire(state and numbers, no keys; in mesh modecoord=,sync_age_s=,sync_error=,peer.N=name address direct|relay|none via last-seconds rtt-ms; while joiningjoin=,join_url,join_code,join_left_s,join_error; when offjoined=,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 (
wireandwg-quickcannot both be on), one network at a time. Auto-start at boot isauto 1in/etc/wire/config.
NanumOS 0.1.8349 · 2026-11-16