The network terms, in plain language.

A short reference for the words used across Fibmesh setup guides, product explanations and connection status.

Read the platform overview →

Look up the terms used in setup, access decisions and connection status. Definitions are grouped by the part of the platform they describe.

33 terms · Four reference sections

Identity and access

8 terms

Scroll horizontally when needed. Focus the table and use the arrow keys.

TermMeaning
WorkspaceThe organisation’s scope for members, resources and policy.
EnrollmentThe process that gives a device or gateway an identity in a workspace.
Device IDAn identifier for an enrolled resource. It is not a password or proof of authorisation by itself.
Access groupA way to organise private membership and permissions. Joining more groups does not create a new device address for each group.
Private addressAn address used within the private network rather than as a public internet destination.
CGNAT rangeShared IPv4 address space, 100.64.0.0/10, used for Networks private addressing. Using this range does not itself mean all Fibmesh services perform NAT.
Private IPv6IPv6 addressing for private network participation, distinct from a publicly routed IPv6 allocation.
Private DNSNames for authorised private resources. Resolving a name does not grant network or application access.

Devices and delivery

8 terms

Scroll horizontally when needed. Focus the table and use the arrow keys.

TermMeaning
EndpointA participating laptop, phone, server or other supported device.
AgentSoftware that handles enrollment, policy and status on a supported host.
GatewayA resource that carries approved traffic between network boundaries, for example into an office LAN.
ConnectorIn Publish, the customer-side software that reaches the app and connects it to the Fibmesh gateway through a tunnel.
Node / exitFibmesh infrastructure used to carry a connection or deliver traffic to the internet.
WireGuardThe currently supported tunnel protocol. It encrypts traffic between its tunnel endpoints, not every later hop to an internet service.
Compatibility ModeA manually managed WireGuard profile with fewer lifecycle and diagnostic features than native enrollment.
P2PA direct peer-to-peer path between participants. Planned for Networks; current paths use Fibmesh nodes.

Addresses and traffic

10 terms

Scroll horizontally when needed. Focus the table and use the arrow keys.

TermMeaning
InboundA connection started by the other side, such as an internet visitor opening your server.
OutboundA connection started by your device. “Outbound” is also the name of Fibmesh’s internet-routing product.
Return pathThe route used for replies. Inbound-only access still needs its responses to return correctly.
Selected outboundA Public IP routing choice: selected destinations use Fibmesh; unrelated destinations use the existing ISP.
Full tunnelEligible internet traffic follows the chosen tunnel. Local routes, OS exceptions, DNS and unsupported address families need explicit handling.
NATAddress translation. A gateway can translate traffic for LAN devices; direct routed Public IP delivery does not require that same translation model.
Routed subnetA block of public addresses delivered to a supported gateway, from which workloads can use separate addresses.
Prefix lengthThe number after the slash in an address block. For IPv6, /48 is a larger block than /64. Fibmesh Routed Subnets supports separately allocated IPv6 prefixes from /48 through /64.
Dual stackBoth IPv4 and IPv6. An IPv6-only allocation does not automatically provide IPv4 connectivity.
AllowlistA list of permitted sources or destinations. Source-IP approval does not replace an application login.

Configuration and status

7 terms

Scroll horizontally when needed. Focus the table and use the arrow keys.

TermMeaning
PolicyThe approved rules describing what a resource should be able to do.
Desired stateThe configuration the backend intends the resource to apply.
Observed stateThe configuration or result the resource last reported.
Latest SyncThe recent exchange of intended policy and reported results. Check its time and outcome.
Control planeThe systems that manage identity, policy and configuration.
Data planeThe path carrying application traffic. Policy governs this path; it is not an extra physical hop.
RevocationRemoval of an identity’s permission or credentials. Verify that affected resources have applied the change.