39NETWORKS CONTROL PLANE

Route a real block of IPv6 space to your network.

Connect a public endpoint to a 39Networks broker location and receive a routed IPv6 allocation over an automatically managed tunnel. The standard service provides a /127 transport link and a customer /56.

Open the service manager Contact the NOC

Routed /56 IPv6Automated provisioningAnti-spoofingLive status

tunnel-request

protocol       GRE
outer endpoint  Your public IPv4
transport link  39Networks /127
routed prefix   Customer /56
node agent      APPLY → VERIFY → ACTIVE

ONE PORTAL, MULTIPLE NETWORK SERVICES

IPv6 access for routers, laboratories, servers and remote sites

Use 39Networks address space where native IPv6 is unavailable or unsuitable. The customer portal records the endpoint, allocates addressing, produces router-specific configuration and sends signed desired state to the selected Linux broker node. No customer or server root password is stored in the website.

IPv6 tunnel connectivity

Request GRE, SIT, IP6IP6, WireGuard, GRETAP, VXLAN or L2TPv3 using an IPv4 or IPv6 outer endpoint.

/127 point-to-point transport
/56 routed allocation by default
Configurable MTU and bandwidth limits

Ready-to-use configurations

Download the customer-side configuration after approval and node verification.

Linux and systemd-networkd
MikroTik RouterOS and VyOS
OpenWrt templates

IPv4 and IPv6 transit

Approved accounts can establish BGP over the tunnel and advertise authorised prefixes.

Default, full-table or no-route modes
Maximum-prefix enforcement
Documented traffic-engineering communities

Routing security

Customer announcements remain pending until the origin and route policy have been checked.

RPKI origin validation
IRR route-object review
Generated BIRD import filters

Address management

Allocated space, static addresses and reverse DNS are managed from the same account.

Non-overlapping IPv4/IPv6 pools
Static service addresses
Validated PTR requests

Anycast services

Eligible accounts can announce one service address through several healthy tunnel endpoints.

ICMP, TCP, HTTP or HTTPS checks
Automatic route withdrawal
Per-location health visibility

HOW IT WORKS

From request to routed prefix

1
Choose a location and protocolEnter your public tunnel endpoint and requested allocation size.
2
Network operations approves the requestIPAM reserves the transport network and routed customer prefix.
3
The broker node applies desired stateThe Linux agent configures the interface, routes, shaping and nftables source validation.
4
Download your router configurationBring up the customer end and monitor state and counters in the portal.

DESIGNED FOR CONTROLLED OPERATION

Provisioning without management SSH from the website

Each broker server makes outbound HTTPS reconciliation requests using a credential scoped to that node. Desired state is signed and validated before the agent calls Linux networking tools. Per-tunnel nftables rules block spoofed sources outside the assigned transport and routed prefixes.

READY WHEN YOUR SERVER IS

Open the 39Networks service manager

Create your account, review available locations and submit a tunnel request. Services remain pending until a production broker node and routed address pool are available.

Open portal