Equipment at real locations
The useful system is often the one already installed.
A security installer maintains a recorder at a customer site. An MSP needs a server’s management interface. A signage company supports players in several stores. A software vendor needs its cloud application to reach a local service.
When that equipment cannot run Fibmesh itself, a supported gateway can provide the connection. Our Fibmesh Edge customer POC demonstrated the plug-in deployment pattern for existing equipment.
Encrypted tunnel to the connector
Forwarding + NAT
Existing router and gateway
Choose access by the job
Private maintenance and public services need different boundaries.
Private access through Networks
Give approved staff or service teams access to the intended resources. Use this path for administration, storage, printers and equipment maintenance. Resources behind the gateway retain their LAN addresses; they are not automatically enrolled devices.
Explore Networks →Public reachability through Public IPs
Use a public destination when an external application requires one. Select the service and permitted sources. The equipment’s authentication remains essential.
Explore Gateway IPs →Choose how to join
Run an agent where you can. Use a gateway where you cannot.
- Supported compute or embedded host
- Use its own app or agent where supported. Its enrollment and private identity belong to that device.
- Existing LAN equipment
- Use Quick Connect for selected remote access without changing the equipment’s default gateway. Confirm LAN reachability and a stable target address.
- A protected equipment network
- Assess a routed gateway when outbound controls or isolation are required. Traffic must pass through that gateway; two Ethernet ports alone do not establish supported policy enforcement.
Printers and scanners may need application drivers or discovery support; routed reachability does not automatically extend local broadcasts. Continuous video and large transfers need a bandwidth assessment.
For vendors, integrators and MSPs
Make customer-site access repeatable.
Standardise the installation around a known connector, an approved resource and a named operator. Separate customers’ resources and access grants. A field technician should know what to plug in; the remote team should know what it is permitted to reach.
Multiple services can share a gateway’s public IPv4 address through distinct port mappings on supported software. Our POC demonstrated the operator-assisted connection pattern; self-service fleet claiming and multi-target portal management remain development work.
Connectivity for vendors and OEMs →Start with one site
Bring the equipment model and the access problem.
We’ll assess the protocol, local network, required users and supported deployment method.
Discuss equipment connectivity →