Fibmesh Edge / A physical deployment option
Connect the equipment you already have.
Quick Connect brings selected remote access to existing LAN equipment through a preconfigured device. Our Edge customer POC informs a hardware range that remains in development.
Explore deployment options ↗Development hardware. No shipping specifications or purchase commitments.
01 / Quick Connect · Customer proof of concept
Beside the equipment. Within the existing LAN.
The customer supplied Ethernet and power for a preconfigured Fibmesh Edge device. An operator remotely selected one target. The equipment kept its local address and router.
One target. Two different traffic paths.
Illustrative placementPermitted incoming access and its replies
- Remote clientRequests access
- FibmeshConfigured tunnel path
- Edge deviceOne Ethernet port on the LAN
- Selected targetExisting LAN address
Ordinary new outgoing traffic keeps the ISP path
- LAN equipmentStarts a new connection
- Existing routerRetains its usual role
- Access ISPExisting internet connection
Give the reply a complete route.
LAN-side source NAT can make the target send replies back to the connector, while hiding the original client source. The connector also needs an appropriate tunnel routing policy; NAT alone does not select that return path.
Keep the POC scope precise.
Multiple servers can use distinct protocol and public-port mappings on supported gateway software where validated for the deployment. That is a separate gateway capability, beyond the original single-target POC.
Quick Connect sits outside the equipment’s ordinary outgoing path. It provides neither LAN isolation nor independent recovery from an ISP outage.
Read the NVR and server access story →02 / Proposed physical roles
Choose the placement before the enclosure.
Port count changes where a device can sit. The hardware, forwarding software and operating procedure still determine what that placement can safely do.
Edge Lite · Proposed one-port connector
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.
Edge Secure · Proposed two-port role
Assess the forwarding position.
A two-port topology creates another installation possibility. Forwarding modes, inline safety, bypass behaviour and measured performance require verified hardware and software. Port count establishes no security certification.
Edge Industrial is a later direction for different power, thermal and enclosure requirements, not a shipping variant. These concepts are not orderable models or approved specifications.
03 / An illustrative configuration
Start with the site and its operating owner.
Identify whether the gateway joins a LAN or sits in a forwarding path. Compare a supported software gateway with the proposed hardware role, then assess the exact environment.
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.
Placement
Record the destination resources, ports, uplink, networks, power and who can physically reach the unit.
Operation
Define the supported runtime, provisioning authority, local administration, updates, diagnostics and replacement process.
Release evidence
Require validated specifications, manufacturing availability, support terms and installation instructions for the specific model.
Evidence needed before release
- Hardware specifications and power, thermal and network constraints
- Update and recovery procedures, plus measured performance
- Regional approvals where applicable and manufacturing availability
- Warranty, service terms and a supported installation process
04 / Questions before deployment
Keep the hardware role and policy authority explicit.
A physical device hosts a local executor. Backend policy remains the source of intended connectivity; the product capability and supported release need their own assessment.
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; backend 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 private keys remain local by default.
Choose hardware based on the required product capability and supported release. A box does not automatically activate 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, manufacturing availability, warranty and service terms. Those facts are not yet established by this development page.
There is no purchase, shipping or stocked-inventory promise. A production installation needs verified release evidence and an agreed operating plan.
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.