IPv6 Detection
Auto
ip -6 + default route
Traffic Transit
IPv4 → IPv6
lossless for clients
Upstream Format
[IPv6]:port
VLESS / Hysteria2 / Trojan
Cascade Modes
3 profiles
Auto / Prefer IPv6 / IPv4 Only

1. Why IPv6 Matters in Apium Cloud OS Cascade Architecture

Most corporate and residential networks still connect to VPN gateways over classic IPv4 — especially on mobile carriers or local ISPs where client-side IPv6 is unavailable or unstable. Meanwhile, across international backbones and data centers, IPv6 offers cleaner IP reputation, less congested peering routes, and significantly lower-cost VPS nodes.

Apium Cloud OS 26.11 introduces native IPv6 support for cascade connections: the server automatically detects global IPv6 connectivity, lets clients connect over standard IPv4, and forwards outbound cascade traffic to anti-DPI exit nodes (vless://, hy2://, trojan://, ss://, socks5://) over IPv6 or Dual-Stack.

2. Automatic Host Detection and Zero UI Clutter

Apium Cloud OS follows a zero-config approach and keeps the UI clean when a host has no IPv6:

  • Automatic host verification: on status checks, the backend verifies both ip -6 route show default and ip -6 -o addr show scope global, filtering out link-local (fe80::/10), ULA (fc00::/7), loopback (::1), tunnel interfaces (sb-tun*, ppp*, tun*, wg*), and tentative/deprecated addresses.
  • When IPv6 is not supported: all IPv6 cascade settings and the header badge remain completely hidden, and adding an IPv6-only upstream node is cleanly rejected at the API level.
  • When IPv6 is active on the server: a compact black IPv6 badge automatically appears in the top-left header right next to the server IPv4 pill. Hovering or clicking opens a popover with the full IPv6 address and a one-click copy button.

3. Lossless Internal IPv4 → IPv6 Transit

A core use case is bridging IPv4 client devices into an IPv6 cascade without changing anything on routers or workstations:

  1. Client ingress over IPv4: routers (Keenetic, MikroTik, OpenWrt), desktops, and mobile devices connect to your Apium Cloud OS entry node via standard IPv4 (L2TP/IPsec, MS-SSTP, VLESS, or Hysteria2).
  2. Gateway encapsulation: traffic enters the local sb-tun0 tunnel interface managed by sing-box. Clients do not need ISP-provided IPv6 or NAT64.
  3. IPv6 cascade egress: sing-box establishes an encrypted transport to the exit node via its bracketed IPv6 address [2a01:4f8:...]:443 (or IPv6-preferred DNS), handling MTU and routing transparently on the gateway.

4. Three IPv6 Routing Modes & Split Tunneling

When IPv6 is detected on the server, the Cascade tab unlocks an IP routing strategy selector:

  • Auto (Dual-Stack IPv4 + IPv6): balanced default mode using whichever stack fits the upstream node and DNS records.
  • Prefer IPv6 for exit nodes (prefer_ipv6): prioritizes AAAA records over A when resolving destinations, ideal for shifting traffic onto clean IPv6 subnets.
  • IPv4 Only (ipv4_only): disables IPv6 DNS resolution in the cascade without altering Linux network interfaces.

In Split Tunneling, ip_cidr rules automatically apply /128 masks for IPv6 addresses (instead of /32), and the upstream health checker formats [addr]:port sockets properly for IPv6 nodes.

5. Real-World Use Cases

Use CaseHow It Works with Apium Cloud OSKey Benefit
1. Bypassing congested IPv4 routes Clients connect to a nearby entry node over IPv4 while cascade traffic travels to VLESS Reality / Hy2 exit nodes over an IPv6 backbone. Lower packet loss, steadier peak-hour latency, and cleaner egress reputation.
2. Low-cost IPv6-only exit pools Add affordable IPv6-only VPS nodes into auto_failover or load_balance pools without paying extra for scarce IPv4 addresses. 2x–4x lower cost when scaling multi-region exit capacity.
3. Reaching IPv6 cloud & dev infrastructure Developers and DevOps teams on IPv4-only office/home networks gain seamless access to IPv6-enabled clusters, APIs, and CDNs. Zero reconfiguration required on local routers or endpoints.
4. Hybrid Dual-Stack Failover Combine IPv4 and IPv6 upstream nodes in one prioritized failover pool. High availability even if a carrier experiences routing issues on one IP family.

6. Who Benefits Most

  • Engineering, DevOps, and AI teams: reliable access to cloud consoles, container registries, Kubernetes clusters, and AI APIs from clean IPv6 subnets with fewer anti-bot challenges.
  • Infrastructure integrators & gateway operators: build scalable multi-hop cascades using budget IPv6-only exit VPS nodes behind a single IPv4 entry point.
  • Offices & router-based deployments: Keenetic, MikroTik, and OpenWrt networks can keep simple IPv4 LAN/WAN setups while the gateway leverages IPv6 upstream.
  • Admins who value zero-touch operations: deploy Apium Cloud OS on an IPv6-enabled VPS and the panel automatically surfaces the IPv6 badge and cascade controls.

7. Quick Start

To start using IPv6 cascades: 1) verify the black IPv6 badge appears next to your IPv4 address in the top header; 2) open the Cascade tab; 3) add an upstream URI such as vless://uuid@[2a01:4f8::1]:443?... or hy2://... and pick your preferred IPv6 routing mode.