network
Every Roomler documentation page tagged “network”.
Private network
A WireGuard-style encrypted mesh between all your machines — stable private addresses, names, direct connections through NAT, tunnels, exit nodes and SSH.
Private networkAddresses and MagicDNS
How each machine gets a stable private address on the mesh, how names work instead of numbers, and what happens to an address when a device is removed.
Private networkHow devices connect
The connection cascade — LAN, direct internet, NAT hole-punching, then relays — how Roomler picks a path, and how to see which one a pair is using.
Private networkSubnet routers
Expose a whole LAN through one enrolled machine, so your other devices can reach printers, NAS boxes, hypervisors and appliances that will never run an agent.
Private networkExit nodes
Route all of a device's internet traffic through a machine you trust — with split-default routing designed so it can never lock you out of your own box.
Private networkTunnels and port forwards
Forward a local port to a service on a remote machine — reach a database, an internal web app or an API without exposing anything to the internet.
Private networkSOCKS5 proxy
Run a local SOCKS5 proxy into a network only one of your machines can see — browse internal sites and reach many hosts without a forward for each one.
Private networkSSH without sshd
Get a real shell on any enrolled machine by its mesh address — with no sshd installed, no port bound and no firewall rule, on Linux, macOS and Windows.
Private networkOne machine in several organizations
Put a single machine in more than one Roomler workspace at once — how identity, addressing and host-global settings behave when organizations overlap.
Private networkEphemeral nodes
Devices that remove themselves — CI runners, containers and autoscaled workers that join the mesh on start and disappear cleanly when they stop.
Private networkThe connection cascade
How two machines choose a path — measured rather than guessed, never ratcheting down, and with a floor over TLS 443 that always connects.
ArchitectureNetwork access control
Control which machines may reach which machines on the mesh, on which ports and protocols — default-deny, enforced at both ends, and audited.
Security & access controlCannot connect, or the session is slow
Diagnose a session that will not start or feels sluggish — starting with the single most common cause, a VPN client that captured the local network.
TroubleshootingPorts and firewall
What Roomler needs to reach, what it never needs opened inbound, and the one port range that matters if you self-host video calls.
ReferenceRoomler vs Tailscale
An honest comparison — what Tailscale does better, where Roomler differs, and which of the two you should actually use.
How Roomler comparesRoomler vs NetBird
An honest comparison against the open-source overlay mesh with the best self-hosting story — what NetBird does better, and the one structural difference.
How Roomler compares