Fibmesh OutboundAvailable
Route internet traffic through a Fibmesh exit over your existing connection. Add an agreed stable or dedicated source when external services require one.
The path first. The source second.
A regular exit changes the internet path. A stable or dedicated source adds specific address terms. Choose those terms deliberately.
Routing scopeFull tunnel for eligible internet traffic in all three options.
Regular exit selected. No fixed or exclusive source address is promised.
Use a supported Fibmesh exit for eligible internet traffic. Start here when the route matters and you do not need a reserved source address.
Use an agreed source address for an external API or business-system allowlist. Confirm the address before asking the provider to add it to a rule.
Choose an exclusive outgoing address when shared source identity does not fit your deployment. Confirm continuity separately if the address also needs to stay the same.
Planning examples only; no traffic is routed here. Stable describes continuity. Dedicated describes exclusivity. Neither assigns a public address directly to your device or opens incoming access.
Your connectionStill supplied by your access ISP.
Your internet exitProvided through Fibmesh.
Your source identityContinuity and exclusivity agreed separately.
An exit for the way you work
Where a service needs a recognised source, agree an exit that fits your team or workload. The access connection gets you online; Fibmesh provides the onward path.
Explore outbound allowlisting →Connect a supported device through the agreed exit as its underlying connection changes. Reconnecting may interrupt sessions; the service’s own login still applies.
Give a server or worker an agreed source for external API access. Check the impact on its other internet traffic before changing the default route.
Route a site through a supported gateway with deliberate LAN routing. Plugging a Fibmesh device into a spare router port does not redirect everyone’s traffic.
Choose by delivery
Both can provide an outgoing source that an external service recognises. Start with how you want to operate the connection.
Route a device’s eligible internet traffic through a Fibmesh exit using its routing profile. Agree a stable or dedicated source if needed.
Assign an address to supported infrastructure for incoming access, outgoing identity, or both. Choose the supported traffic policy separately.
A stable-source requirement does not require both products. If a Public IP assignment already covers your incoming and outgoing needs, another exit service may add nothing.
The current profile model uses full-tunnel routing. It does not offer an application picker or destination-by-destination rules. Check local, private and operating-system exceptions, DNS, IPv4 and IPv6 handling for the supported platform.
WireGuard protects traffic between the endpoint and the Fibmesh exit. That tunnel ends at the exit. Keep HTTPS or other application encryption and the destination’s authentication in place.
A profile record does not provision an exit or prove a healthy connection. Enabling a profile replaces the organisation’s active egress profile, so check who is affected before making the change.
Explore CLI & API scope →An eligible workspace, a supported client or gateway, a working internet connection and a provisioned exit. Confirm the serving region, address-family handling, DNS, source terms and recovery procedure during assisted setup.
No. Outbound is a separate product journey. Private access, public address delivery and application publishing have their own setup and policies.
Do not assume traffic will be blocked. A kill switch is not a verified current capability. Agree and test interruption behaviour before using an exit for traffic that must never take the ordinary ISP path.
The tunnel changes the route. It does not establish web filtering, malware inspection, a secure web gateway or anonymity. Continue to use application authentication, encryption and host firewall controls.
Your next connection
Tell us what needs to connect, where it runs and whether the destination requires a known source. We’ll confirm the exit and supported setup.
