FST Cloud IPv6 Tunnel Broker

IPv6 for networks that don't have it yet. You keep your IPv4 provider; we give you an IPv6 tunnel and a routed IPv6 prefix out of 2602:f848::/40 (AS16509 / AWS us-west-2, Oregon). For IPv6-only hosts behind the tunnel we also run DNS64 and NAT64.

What you get

• A tunnel over IPv4: 6in4 (protocol 41), GRE (protocol 47) or WireGuard (UDP 51820, works behind any NAT).
• A point-to-point /112 and a routed /96 for your own hosts, reverse DNS delegation on request.
• DNS64 at 2602:f848::1:0:0:53 and NAT64 (prefix 2602:f848::1:64:0:0/96) for your IPv6-only hosts.
• NTP at ntp.tunnel.fst.gs.
• Dynamic IPv4? Point your router at the update URL (same format as other brokers):
  https://ipv4.tunnel.fst.gs/nic/update?tunnel=ID&key=KEY

Customers only ever get IPv6. The IPv4 addresses of the service are shared: each 6in4/GRE server endpoint carries many tunnels, and hosts behind the same NAT are put on different endpoints so their tunnels don't collide.

Linux example (6in4)

ip tunnel add fcl6 mode sit local YOUR_IPV4 remote SERVER_IPV4 ttl 64
ip link set fcl6 up mtu 1480
ip -6 addr add CLIENT_IPV6/112 dev fcl6
ip -6 route add default via SERVER_IPV6 dev fcl6

Behind NAT, use your private address as local and tell us the NAT's public address. GRE is the same with mode gre and MTU 1476.

Order

Tunnels are ordered at fst.gs (IPv6 Tunnel). Questions: noc@fst.gs.

Service status: status.tunnel.fst.gs

Acceptable use

Outbound SMTP (TCP 25) is blocked by default. Abuse reports to noc@fst.gs; for NAT64 include address, port and time and we can trace it to the tunnel.

FST Cloud LLC, 30 N Gould St Ste 100, Sheridan, WY 82801, USA