Home-router NAT
A typical home router gives devices private LAN addresses and translates their outbound connections to a public address. Several devices can therefore share the same public IPv4 address.
Node networking
NAT and CGNAT for bandwidth-sharing nodes
NAT lets devices share a public IP address. Learn how it affects connections and what to check when a node goes offline.
Networking concepts
Three concepts to keep separate.
Private addresses, upstream translation, node status, and earnings describe different parts of the network and product experience.
Carrier-grade NAT (CGNAT)
Some access providers place another translation layer upstream, so multiple customer connections can share provider-managed public IPv4 space. The router alone cannot prove whether that upstream layer exists.
Network changes are separate from earnings
NAT type, public-address changes and online status describe network conditions. They do not by themselves determine traffic, recorded usage, or earnings.
Network-path checklist
Diagnose the path without weakening it.
Start by checking the device, router, and internet connection. Opening ports or changing firewall and VPN settings can expose the network; follow the installation guide before making those changes.
- 1
Confirm ordinary internet access works on the device before changing router settings.
- 2
Compare the device LAN address, router WAN information and provider documentation if you need to understand the local network path; do not infer CGNAT from one browser-visible value alone.
- 3
If a node disconnects after a router restart or network change, verify the AntGain process and authenticated device state before changing firewall or port-forwarding rules.
- 4
Use the current AntGain download path to confirm the installed platform/build is still supported.
- 5
Escalate provider-specific NAT questions to the ISP when the upstream address model is unclear rather than bypassing provider controls.
FAQ
NAT and CGNAT questions
Answers cover address translation, node status, traffic, and earnings without treating NAT type as a shortcut.
Does CGNAT automatically prevent an AntGain node from working?
Not necessarily. NAT behavior is only one part of the network path. Check the current supported AntGain release and your signed-in node status instead of relying on a generic CGNAT label.
Should I enable port forwarding or UPnP for AntGain?
Do not expose inbound ports or enable automatic router exposure merely because a node is offline or because your network uses NAT. Follow only current AntGain documentation that explicitly requires a network change for your deployment model.
Do several devices behind one public IP create several equally valuable nodes?
Several devices can share one public IP. Adding more devices does not by itself mean more traffic or earnings.
Does a public IPv4 address guarantee more traffic or earnings?
Traffic and earnings vary with demand and successfully recorded activity. Being online does not guarantee income.
Current release
Check your client before changing network settings.
Confirm the current release and your signed-in node status first.