Quick Connect / Customer proof of concept
Plug in beside the equipment. Configure access remotely.
Our customer POC used a preconfigured Fibmesh Edge device connected to the existing LAN. The customer supplied Ethernet and power; Fibmesh remotely selected the target. The equipment kept its address and router. The POC demonstrated operator-configured remote access. Multiple servers can use distinct public port mappings on supported gateway software; confirm the mapping support needed for the deployment.
The connector forwards permitted incoming connections and their replies. It does not sit in the equipment’s ordinary outgoing path, provide LAN isolation or survive an ISP outage through an independent connection.
Read the NVR and server access story →The mechanism
Physical placement is the first design decision.
Join the network.
A connector can sit beside the resources it serves. With one Ethernet port it is not an inline firewall between two interfaces or an ISP-failover appliance.
Assess the forwarding position.
A two-port topology creates another installation possibility. Its forwarding modes, security behaviour, bypass and performance still require verified hardware and software.
Edge Industrial is a later direction for environments with different power, thermal and enclosure requirements. These concepts are not orderable models or approved specifications.
A concrete example
A site assessment, before a hardware order
Development concept
Choose the physical role
- Site network
- Edge connector
- Fibmesh fabric
- Edge Lite
- One Ethernet port · connector role
- Edge Secure
- Proposed two-port topology
- Edge Industrial
- Later development direction
- Release
- Hardware, software and support unverified
A one-port connector is not an inline firewall or ISP-failover appliance.
Start with the resources and topology. Identify whether the gateway joins a LAN or sits in a forwarding path, then assess power, local administration, updates and recovery. There are no approved orderable specifications or shipping claims on this website.
Placement
Record ports, uplink, destination networks, power and who can physically reach the unit.
Operation
Define the supported runtime, provisioning authority, updates, diagnostics and replacement process.
Release evidence
Require validated specifications, manufacturing availability, support terms and installation instructions for the specific model.
Questions before deployment
Hardware role, local execution and deployment evidence.
Port count changes the installation
The proposed Edge Lite has one port. A one-port connector attaches to a network; it cannot be treated as an inline firewall between two interfaces or an ISP-failover appliance.
The proposed Edge Secure has two ports. That creates a different physical deployment possibility, but two ports alone do not prove firewall throughput, inline safety, bypass behaviour or any certified security capability. Edge Industrial is a later direction, not a shipping variant.
Software policy still has an owner
Hardware hosts a local executor; workspace policy remains the source of intended connectivity. The gateway identity, credential, update path and operating responsibility must be explicit. Gateway credentials are distinct from endpoint credentials, and keys remain local by default.
Choose hardware based on the required product capability and supported release, rather than assuming every box activates every Fibmesh service. Private subnet access, public identity and default routing require separate assessment.
Evidence a deployment needs
An evaluated release needs approved specifications, supported power and network requirements, thermal limits, update and recovery guidance, measured performance, regional approvals where applicable, warranty and service terms. Those facts are not yet established by this development page.
There is no purchase, shipping or stocked-inventory promise. Do not plan a production installation from concept artwork or an unverified port description alone.
Evaluate the site before the enclosure
Document the network owner, installation location, destination resources and required physical topology. Compare a supported software gateway with the proposed hardware role. Then assess platform support and the region-specific deployment constraints.
For gateway-backed private resources, read Networks. For the broader deployment choices, use deployment options. Hardware availability remains subject to release assessment.