Guide

Game Server Not Reachable: CGNAT and DS-Lite

Your game server works on LAN but friends cannot connect? Identify CGNAT, DS-Lite, firewall and router problems, and understand which fixes can work.

Gaming computer in a desk setup with networking equipment
Source: Coop Legends

Overview

A game server can work perfectly on its own computer and throughout your home network yet remain unreachable to friends on the internet. The cause is not always a wrong game port. With carrier-grade NAT (CGNAT) or DS-Lite, the crucial IPv4 address translation may happen at your internet provider, outside your own router.

This guide walks through troubleshooting in a practical order, helping you distinguish a server problem from a host firewall, router forwarding rule, or internet connection limitation.

September 5, 2026.

Test locally before investigating the internet connection

Before examining public IP addresses or DS-Lite, make sure the game server works inside your local network.

  1. Start the server and check its log for a successful launch.
  2. Connect from the same machine using the game's supported local method, if available.
  3. Try connecting from a second device on the same home network using the server's LAN address.
  4. Only then test from a separate internet connection outside your home.

If the LAN test already fails, obtaining a public IPv4 address or changing router forwarding rules will not fix the immediate problem. Check the running server process, network binding, compatible game versions, and the host firewall first.

Identify which network layer is failing

TestObserved resultLikely area to investigate
Server launchError in the logInstallation, configuration, or runtime dependencies
Local works, LAN does notSecond home-network device cannot connectHost firewall, network profile, or binding address
LAN works, internet does notPlayers outside the network fail to connectRouter/NAT, wrong forwarding destination, CGNAT, or DS-Lite
Only the server browser failsDirect connection may still workDiscovery/query port or platform registration

Public IPv4, private IPv4, and CGNAT

With conventional home NAT, your router receives a public IPv4 address and can forward inbound traffic to a computer on your LAN. With carrier-grade NAT, an internet provider instead shares a public IPv4 address among multiple customer connections.

IETF RFC 6598 reserves 100.64.0.0/10—from 100.64.0.0 through 100.127.255.255—as shared address space. Those addresses are not globally routable. If the IPv4 WAN address shown by your router falls within this range, that is strong evidence of CGNAT.

Other nonpublic WAN addresses may also mean there is another NAT device upstream. The key limitation is that a forwarding rule in your own router controls only the address translation performed by that router.

What changes under DS-Lite?

CGNAT and DS-Lite are not identical. CGNAT is a general term for carrier-side network address translation. DS-Lite is a particular architecture specified in IETF RFC 6333: IPv4 packets are carried over IPv6 to an address-family transition router (AFTR), where the provider performs IPv4 NAT for multiple customers.

As a result, a home router does not have the same direct control over inbound IPv4 connections that it has when it receives its own public IPv4 address. A normal forwarding rule cannot configure the upstream AFTR by itself.

Important exception: FRITZ!'s DS-Lite documentation explains that Port Control Protocol (PCP) can request a port mapping from the internet provider when the provider supports it. Thus DS-Lite does not make incoming IPv4 connections impossible in every setup.

Conversely, finding CGNAT does not automatically mean your provider uses DS-Lite; carrier NAT can be deployed through several different network architectures.

How to check your connection

  1. Open your router's internet or WAN status page.
  2. Look for a public IPv4 address, a shared/CGNAT address, or a DS-Lite indicator.
  3. On a FRITZ!Box, the relevant connection information is generally available in the internet status or online monitor details; exact labels depend on the model and firmware.
  4. If the router has its own public IPv4 address, inspect its port-forwarding rule and verify the target server's current LAN address.
  5. If your connection uses CGNAT or DS-Lite, ask your provider which options it offers for incoming connections.

An external port test must match the transport protocol of the game. A TCP port scanner cannot verify a service that accepts only UDP. Use a relevant game client or the developer's official server-query method from outside your home network whenever possible.

Realistic options when you have CGNAT or DS-Lite

There is no universal router setting that bypasses provider NAT. Depending on your provider and game, these options may help:

  • PCP with DS-Lite: Some providers allow PCP-based port mappings at their network edge, as documented by FRITZ!. Confirm support with your provider.
  • Public IPv4 or native dual stack: If available from your provider, this lets you manage conventional IPv4 forwarding yourself.
  • Direct IPv6 access: This may work when the server software, game client, platform, and each player's connection support the required IPv6 setup.
  • Built-in platform relay or P2P: Certain games do not require direct inbound connections. Valve's Steam Datagram Relay supports both P2P and dedicated-server connections.
  • External hosting: A VPS or managed game server with suitable public connectivity moves the server away from your home connection.

Which option makes sense depends on the game and provider. An external server is useful only if the game supports independently hosted server software.

Port forwarding still fails with a public IPv4 address

If your router has its own public IPv4 address, CGNAT is not automatically the cause. Check:

  • Does the forwarding rule point to the server's current local address?
  • Do port number and protocol match the current server configuration?
  • Does the host firewall allow that traffic?
  • Is the server running and listening on the expected interface?
  • Are the gameplay, query, and administrative ports separate?

For targeted firewall and router instructions, see the game server port-forwarding guide.

Keep a short diagnostic record

Record four results during troubleshooting: locally reachable, reachable on the LAN, public IPv4 available, and external connection successful. These observations usually narrow the problem down to one network layer, without changing the firewall, router, and game server simultaneously.

When contacting your internet provider, explain that you need incoming connections to a self-hosted service. Asking whether you have your own publicly reachable IPv4 address or whether the line uses CGNAT/DS-Lite is more specific than reporting only that a game server does not work.

A router WAN IPv4 address in the shared range 100.64.0.0/10 is a strong indicator. Also check the router status and your provider's connection information; other nonpublic WAN addresses can indicate upstream NAT.

No. RFC 6598 reserves that range for carrier-grade NAT shared addressing. DS-Lite is a particular IPv4-over-IPv6 architecture using an AFTR at the provider. The address alone does not establish DS-Lite.

The IPv4 NAT function operates in the provider's AFTR. A forwarding rule in your home router cannot configure it directly, although provider support for PCP may allow a requested mapping.

PCP stands for Port Control Protocol. With a compatible router and an internet provider that supports PCP, the router may request an inbound mapping at the provider's network edge.

Sometimes, but the server, game client, online platform, and other players' internet connections must support the required IPv6 access. Verify support for the specific game.

No. External hosting helps only where the game supports separately hosted server software or another suitable server architecture.