Why IPsec site-to-site fails behind CGNAT
Classic site-to-site VPNs (IPsec on a firewall such as OPNsense, pfSense, FortiGate or SonicWall) need at least one side to accept an incoming connection on a public IP. With CGNAT, your "public" address is shared with other customers and the ISP drops unsolicited inbound traffic. If both sites are behind CGNAT, neither side can be reached.
A quick check: if the WAN address on your router starts with 100.64 to 100.127, or doesn't match what a "what is my IP" site shows, you're behind CGNAT.
Your realistic options
1. Pay for a static public IP
Many ISPs offer one for a monthly fee. It fixes the problem for one site, but it's not always available (especially on 5G or fixed wireless) and the VPN port is now exposed to the internet.
2. Run your own cloud VM as a hub
Rent a small VM with a public IP and have both offices dial out to it. It works, but you now patch, monitor and secure a server, and pay for it.
3. Use an outbound-only relay service
A small connector at each office dials out to a managed cloud edge, and traffic between sites flows through it. Nothing is exposed and no public IP is needed. This is the approach Arx Cloud uses.
How Arx Cloud connects your offices
- LAN connector at each site on any always-on machine. Outbound only, works on CGNAT, 5G and fixed wireless.
- Whole-subnet access, so printers, file shares and line-of-business apps work, not just individual computers.
- Overlapping subnets handled automatically if both sites use the same range.
- 12 global edge locations on port 443, so it also works from hotel and guest Wifi for remote staff.
- Plus web filtering and AI data-leak protection for staff in the same app.