Host a self-hosted server behind CGNAT or Starlink using IPv6
Behind carrier-grade NAT you cannot forward IPv4 ports, but GameVox uses your IPv6 address automatically once inbound IPv6 is allowed.
Allow inbound IPv6 to your server. Behind carrier-grade NAT (CGNAT) your IPv4 address is shared, so port forwarding cannot work. These connections usually have a real IPv6 address, and the server finds and uses it on its own.
T-Mobile Home Internet, Starlink and most mobile broadband use CGNAT. No port forwarding, UPnP or DMZ setting gets IPv4 traffic in.
Allow inbound IPv6
IPv6 has no NAT, so there is nothing to forward. Add allow rules on your router's IPv6 firewall for the server machine:
| Protocol | Port | Carries |
|---|---|---|
| TCP | 8088 | Chat, files, voice handshake |
| UDP | 7070 | Voice and video |
| TCP (optional) | 7070 | Voice fallback when UDP is blocked |
Use your own ports if you changed TCP_PORT or UDP_PORT. Check the machine's own firewall too. Windows Defender Firewall and ufw treat IPv6 separately from IPv4.
Keep the address stable
Windows and most Linux distros rotate temporary IPv6 addresses, often daily. GameVox follows the change, but a firewall rule for yesterday's address stops matching. Write the rule for your whole LAN /64, limited to the GameVox ports, or turn off privacy addresses on the server.
Windows, in an Administrator PowerShell, then reboot:
netsh interface ipv6 set privacy state=disabled store=persistent
netsh interface ipv6 set global randomizeidentifiers=disabled store=persistent Linux, in /etc/sysctl.conf:
net.ipv6.conf.all.use_tempaddr=0 Starlink
The stock Starlink router blocks all inbound IPv6 and has no firewall settings, so you need your own router.
- You need a Gen 2 or Gen 3 Starlink router (Gen 1 has no IPv6), plus a router that supports DHCPv6 prefix delegation and IPv6 firewall rules.
- Set up your own router first. Then put the Starlink router in Bypass mode in the Starlink app. Starlink Wi-Fi turns off, and undoing bypass needs a factory reset.
- On your router's WAN, use DHCPv6 and request a /56 prefix. On the LAN, track the WAN interface and turn on router advertisements (SLAAC).
- Check that the server has a global IPv6 address starting with
2or3. - Add the allow rules above.
Without your own router, the options are a public IPv4 address from Starlink (some plans), a TURN relay, or a VPS tunnel.
Check it works
Open Server Settings > General > Network Diagnostics in the GameVox app.
| You see | Meaning |
|---|---|
| Address detected, reachable | Done. Members connect over IPv6. |
| Address detected, not reachable | Something blocks inbound traffic. Check the router and machine firewalls. |
| No address | IPv6 is not reaching the machine. Check the router's IPv6 setup. |
An fd or fe80: address | The router hands out local addresses only. Prefix delegation is not working. |
GameVox re-checks about every 60 seconds after you fix a rule. Run gamevox-self-hosted-server --logs --follow to watch.
Members without IPv6
Members on IPv4-only networks (some workplaces, ISPs and many VPNs) cannot reach an IPv6-only server. For them, run a TURN relay such as coturn and set TURN_SERVER_URL, TURN_USERNAME and TURN_PASSWORD. See environment variables.
Docker
The container needs IPv6 itself. Use host networking or an IPv6-enabled Docker network.
Pin or turn off IPv6
Set PUBLIC_IPV6 to an address only if detection picks the wrong one, or to off to turn IPv6 off. Link-local, unique-local, 6to4 and Teredo addresses are rejected.