Fibmesh Networks / Devices & gateways
Use a supported app or agent on the device itself, or a gateway for resources that need to keep their existing setup. Choose around what needs to connect.
Compare the two approaches Deployment guide · Confirm platform and deployment support during assisted setup.01 / Choose where Fibmesh runs
Enrol the endpoint that runs Fibmesh. For equipment behind a gateway, approve the resource path separately.
For a working computer, mobile client or server that can run supported Fibmesh software.
A device can be a working client, a resource host, or both where its platform and policy permit.
For approved office, branch or cloud resources that keep their existing network setup.
A supported router, host or virtual machine can fill the gateway role. Hardware and software support must be confirmed.
02 / Know what is enrolled
A route does not turn every device in a range into a managed endpoint, install software on it or replace its authentication.
Understand identity, addresses & permissions →03 / Connect an existing network
The gateway needs to reach the resource locally. The resource’s reply also needs a supported path back to the remote device.
100.96.1.24Enrolled working device10.20.0.2Enrolled site connector10.20.0.20Existing LAN resourceThe office gateway is the site connector. The Fibmesh routing node is part of the service. WireGuard protects the configured tunnel legs; retain application encryption for the final LAN hop.
Choose the host or subnet needed for the job. Check for address clashes with home, office, cloud and other VPN networks.
Use a return route through the gateway, or a supported source-NAT arrangement. Source NAT can hide the remote device’s source IP from the resource; it does not replace routing.
Selected incoming private access does not require making the gateway every LAN device’s default router. Outgoing internet traffic must actually be routed through it; plugging in a device does not redirect the network.
04 / Match the method to the resource
Choose a device type to see the approach and the checks that matter.
Check released platforms →Confirm the exact operating-system release, installation rights, existing VPNs and route and DNS behaviour.
Confirm app availability, VPN permissions, background behaviour, sleep and reconnection after Wi-Fi or cellular changes. A mobile client is not assumed to be an always-on server or site gateway.
Confirm service ownership, the host firewall, application listener and unattended operation on the deployed release. A server can host a resource and connect to another private service where its platform and policy permit.
Check destination routes, overlapping address ranges, provider and local firewalls, and replies back through the gateway. The gateway needs local access to the destination and a working internet uplink.
Confirm a stable LAN address, required protocols, application credentials and driver support. A verified native agent may be an alternative where available; printers and scanners can need separate discovery and driver setup.
Check the container network namespace, required privileges, address translation and reachability from the tunnel host to the container. Container support depends on the actual host and network configuration.
This checklist does not establish a released client for every platform. WireGuard support on a router alone does not establish full managed Fibmesh compatibility.
05 / Choose the connection method
WireGuard is the currently supported tunnel protocol. A managed Fibmesh client also handles identity, policy and observed state through its supported local service. Private keys stay on the endpoint by default.
A manual profile is Compatibility Mode, subject to workspace policy. It does not imply the same policy updates, diagnostics or lifecycle behaviour as a managed native endpoint. Confirm limitations and the removal procedure before choosing it for a router or appliance.
Before choosing the setup
Not necessarily. Networks carries approved IP traffic; it is not a shared Ethernet segment. Configure a compatible printer by address or supported name and install its driver where needed. Discovery broadcasts, USB-only devices and vendor-specific scanning workflows need separate assessment.
The supported client initiates its tunnel towards Fibmesh. Home-router port forwarding is not normally required for this gateway-based path. The local network must permit the required tunnel traffic; restrictive firewalls or blocked UDP still need assessment.
That depends on the operating system, routes and DNS settings. Some platforms restrict simultaneous VPNs. Check both clients and test overlapping private ranges before relying on the combination.
Next / Getting started
Start with one person and one private resource. Confirm the supported client or gateway, then verify access in both directions.