Question Carrier Grade Network Address Translation

Please provide comments and solutions that are helpful to the author of this topic.

7Oz-64

Level 4
Thread author
Well-known
Jan 16, 2023
151
446
268
What do you think of CGNAT option if available from your ISP ?
I know that you can share the same IP with lot's of others customers, what happened if other customers doing prohibited things ?, sure each client uses a personalized port. If you use domotics like camera ip.........it could be a problem.

Capture d’écran du 2026-07-18 08-43-38.pngCapture d’écran du 2026-07-18 08-44-03.png
 
What do you think of CGNAT option if available from your ISP ?
I know that you can share the same IP with lot's of others customers, what happened if other customers doing prohibited things ?, sure each client uses a personalized port. If you use domotics like camera ip.........it could be a problem.

View attachment 298893View attachment 298894
CGNAT is generally safe and common, but it has some practical disadvantages.

With Carrier-Grade NAT, multiple customers share one public IPv4 address. Your ISP differentiates connections by using different source ports and keeps translation logs showing which customer had a particular port at a specific time.

If another customer using the same public IP performs prohibited or abusive activity, the service provider or website should normally be able to identify the actual customer from the IP address, timestamp, and source port. However, automated systems may initially flag or rate-limit the shared public IP, so you could occasionally encounter:

  • CAPTCHAs or temporary blocks
  • Reduced reputation for some websites or online services
  • Problems with certain multiplayer games, peer-to-peer applications, or VoIP services
  • Difficulty hosting services directly from your home connection

The main technical limitation is inbound connectivity. Because the public IP belongs to the ISP’s NAT system, normal port forwarding on your own router will not make a camera, NAS, or home server reachable from the Internet. This can affect remote access to:

  • IP cameras and video recorders
  • Home automation systems
  • NAS devices
  • Self-hosted websites, VPN servers, and game servers

Some ISP-provided camera or smart-home systems still work because the devices establish outbound connections to the vendor’s cloud service. That is different from directly connecting to the device through your own public IP.

Possible solutions include:

  • Requesting a public IPv4 address or static IPv4 address from the ISP; this may cost extra.
  • Using IPv6, if the ISP provides it and the device, router, and firewall are configured correctly.
  • Using a reputable VPN or overlay network that supports incoming access, such as a properly configured private mesh VPN.
  • Using the manufacturer’s cloud relay, while reviewing its security and privacy implications.

CGNAT can also make troubleshooting more difficult because online IP-checking websites show the shared public address rather than an address dedicated to your connection. It does not, by itself, mean that your traffic is visible to other customers; customer separation is handled by the ISP’s NAT infrastructure.

For security, avoid exposing cameras or home automation devices directly to the Internet whenever possible. Keep their firmware updated, use unique passwords and multi-factor authentication where available, and prefer VPN-based remote access over forwarding camera or administrative ports.

Overall, CGNAT is usually unimportant for ordinary browsing and streaming, but it can be a significant limitation if you need reliable inbound connections, port forwarding, or self-hosted services. IPv6 or an ISP-provided public IPv4 address are the cleanest solutions.
 
  • Thanks
Reactions: 7Oz-64
@Bot
CGNAT enabled : speed at 70mb/s
CGNAT disabled : speed at 130mb/s
CGNAT itself normally should not reduce speed from 130 Mbps to 70 Mbps.

CGNAT adds another translation layer, but on a properly provisioned ISP network it should usually have little noticeable effect on download speed. A large difference suggests that another setting or network condition changed at the same time.

Possible explanations include:

  • The ISP applies a different bandwidth profile when CGNAT is enabled.
  • CGNAT traffic uses a congested or poorly performing gateway.
  • The public-IP and CGNAT services use different routing paths.
  • The modem or router changes configuration, such as IPv4/IPv6 mode, MTU, or connection type.
  • The speed tests were performed against different servers or at different times.
  • The ISP’s CGNAT gateway is overloaded.
  • The result is affected by Wi-Fi, background traffic, or an inconsistent test method.

To verify it, test under controlled conditions:

  • Use a wired Ethernet connection directly to the router.
  • Use the same speed-test server for both tests.
  • Run several tests at different times, including off-peak hours.
  • Check whether the WAN address is private or within the CGNAT range 100.64.0.0/10 when CGNAT is enabled.
  • Compare latency, upload speed, packet loss, and download speed—not only one test result.
  • Confirm whether IPv6, MTU, router firmware, and QoS settings change between the two modes.

If the difference remains consistent, record the test results and contact the ISP. Tell them that the same connection reaches approximately 130 Mbps with a public IPv4 address but only approximately 70 Mbps through CGNAT, and ask whether the CGNAT gateway or service profile is bandwidth-limited.

Therefore, your observation can be real, but it is probably caused by the ISP’s CGNAT implementation, routing, or provisioning rather than CGNAT as a technology inherently cutting the speed in half.
 
  • Thanks
Reactions: 7Oz-64