OVHcloud IPv6 Proxy Setup: /64 Routing, Gateway Quirks, and MeshProx

Part of our IPv6 proxy management guide series.

OVHcloud VPS and dedicated servers are common in EU fleets. Like Hetzner and Vultr, most OVH machines receive a routed IPv6 block — but OVH's documentation and panel terminology create confusion around /64 vs /128 netmasks. This guide clarifies what OVH actually routes and how to run MeshProx on top.

What OVH assigns

Per OVH's IPv6 VPS guide, each service gets:

• YOUR_IPV6 — primary global address
• IPv6_GATEWAY — upstream router (often outside a naive /128 mask)
• A block described in the panel as /128 in some docs, /64 on dedicated servers

Community reports on OVH's docs repository note a recurring issue: if you configure /128, the gateway may fall outside your on-link subnet, breaking default routing. Many working Debian/Ubuntu configs use /64 on the interface even when the panel says /128 — this places the gateway inside the same prefix and restores connectivity.

Takeaway: If IPv6 works internally but fails from the public internet, try changing the interface prefix from /128 to /64 before debugging proxy software.

2026 infrastructure change (isolated /64)

OVH's infrastructure roadmap documents a transitional move toward dedicated /64 isolation per VPS (RFC 6177 alignment). As of early 2026:

• VPS instances may receive an isolated /128 within a dedicated /64 segment — reducing "noisy neighbor" reputation bleed
• Full customer-managed /64 with many addresses is still on the long-term roadmap (issue #120)

For MeshProx operators this means: verify your instance's actual routed prefix in the OVH panel before assuming billion-address AnyIP rotation. Some plans still behave like a single-address /128; others route a full /64 suitable for AnyIP binding.

Manual network baseline (Debian/Ubuntu)

If you need to fix IPv6 before MeshProx preflight:

``text # /etc/network/interfaces (example — replace with panel values) iface eth0 inet6 static address YOUR_IPV6 netmask 64 post-up /sbin/ip -6 route add IPV6_GATEWAY dev eth0 post-up /sbin/ip -6 route add default via IPV6_GATEWAY dev eth0 ``

OVH also documents netplan and NetworkManager variants in the same guide. Ensure ICMPv6 is allowed — neighbor discovery depends on it.

For advanced routing (containers, firewalls), operator blogs like SAwkNerd's OVH IPv6 write-up explain how OVH places gateways relative to /56 and /64 — useful if you run nested networking, but not required for a simple MeshProx host.

MeshProx onboarding

1. Confirm IPv6 works: ping6 -c 3 ipv6.google.com
2. Servers → Add server (IPv4 for SSH, upload key)
3. Preflight — detects global range, opens UFW TCP 20000–60000
4. Install agent → Verify proxy (SOCKS5 smoke test)

If preflight reports no usable range:

• Re-check netmask (/64 vs /128)
• Reboot after netplan/interfaces changes (OVH docs recommend this)
• Open a ticket confirming whether a routed /64 is available on your plan

OVH vs Hetzner for proxies

| Factor | OVH VPS | Hetzner Cloud | |--------|---------|---------------| | Typical IPv6 | Routed block; plan-dependent | Routed /64 on CX/CPX | | EU presence | Strong FR/DE/PL | Strong DE/FI | | Docs clarity | /128 vs /64 confusion | Generally consistent | | MeshProx fit | Excellent when /64 routes | Excellent default choice |

See Hetzner setup for side-by-side economics.

Troubleshooting

| Symptom | Fix | |---------|-----| | IPv6 ping fails externally | Try /64 netmask; verify gateway routes | | Agent OK, proxy timeout | UFW — re-run preflight Fix on firewall check | | Only one exit IPv6 works | May be isolated /128 plan — check roadmap limits | | /64 blocked by target | New VPS/region; see rate limit guide |

Next steps

• Multi-VPS pool with failover → pool setup
• Scraping at scale → IPv6 rate limits
• Compare costs → self-hosted vs residential