Akamai Linode IPv6 Proxy Setup: Routed /64, Network Helper, and MeshProx

Part of our IPv6 proxy management guide series.

Akamai Linode (formerly Linode) is one of the few providers that explicitly documents routed IPv6 /64 and /56 ranges for customer use — making it a strong MeshProx host alongside Hetzner and Vultr.

Two IPv6 models on Linode

Per Akamai's IPv6 overview:

1. SLAAC address (default)

Every Linode gets one autoconfigured global IPv6 via SLAAC. Good for a single server identity — not enough for thousand-port proxy fleets.

2. Routed /64 or /56 range (what you want)

A routed range is assigned to your account in a data center. From that block you configure individual addresses on a specific Linode. A /64 provides 2⁶⁴ addresses — the same scale as RFC 4291 LAN segments used in AnyIP proxy pools.

Akamai's IP management docs note:

• Default quota: one /64 per customer per data center (larger /56 via support ticket)
• Routed ranges require manual network configuration
• You must disable Network Helper before static/routed addressing

This is more operator work than Hetzner cloud-init defaults — but the resulting /64 is production-grade for MeshProx.

Step-by-step: add a /64

1. Cloud Manager → Linode → Add an IP → Add a /64 IPv6 range
2. Note the routed prefix (e.g. 2600:3c0f:...::/64)
3. Disable Network Helper on the Linode (required for manual config)
4. Follow manual network configuration for your distro:
5. - Keep SLAAC for the primary address if desired
6. - Add a local route for the /64 on your public interface
7. - Enable net.ipv6.ip_nonlocal_bind=1 for AnyIP-style binding

MeshProx's agent automates proxy-specific kernel routes and NDP during Install agent — you mainly need the /64 attached and IPv6 forwarding reachable before onboarding.

Firewall and ports

Linode Cloud Firewalls apply to public interfaces. Allow:

• TCP 22 from your admin IP (SSH)
• TCP 20000–60000 for MeshProx proxy listeners (or let preflight configure UFW on the host)

Akamai documents IPv6 firewall rules alongside IPv4 — use ::/0 where you would use 0.0.0.0/0.

MeshProx workflow

1. Add server in Servers with Linode IPv4 + SSH key
2. Preflight — validates /64, RAM, systemd, UFW
3. Install agent — systemd unit, outbound WSS to panel
4. Proxies → generate SOCKS5/HTTP batch → export CSV

For multi-Linode fleets, create a pool gateway (guide) — Akamai also documents IPv6 pools shared across Linodes in a data center for failover scenarios.

Linode vs DigitalOcean for IPv6 proxies

| Provider | IPv6 for proxies | MeshProx scale | |----------|------------------|----------------| | Linode | Optional routed /64 | Thousands of ports | | DigitalOcean | /124 (16 addresses) | Small tests only — see DO limits | | Hetzner | Default routed /64 | Thousands of ports |

Troubleshooting

• Preflight: no range → /64 not added in Cloud Manager, or Network Helper overwrote manual config
• Addresses don't respond → missing local route or NDP proxy; re-run agent install
• Slow egress → pick a region close to your targets; Linode's backbone is solid but not magic for subnet rate limits

Related guides

• How AnyIP works
• Vultr setup (similar US-focused option)
• Python integration