Proxmox behind CGNAT or a router that blocks inbound: how to reach your VMs (tested)
If your internet provider shares one address between many customers (CGNAT, common on Starlink, 5G home internet and some fibre), nothing from the internet can start a connection to your Proxmox host or its VMs. A port forward on your own router does not help, because the address the world sees belongs to your provider, not to you.
Outgoing connections still work. That is what this page uses: the Proxmox host makes an outgoing tunnel to TunnelNet, and the public address lives at our end.
Pilot
Proxmox VE support is a pilot. It is not on sale yet. If you would like to try it, ask us.
Tested on
Date: 18 November 2026 · Host: Proxmox VE 8.4.21 on Debian 12, one node, a test machine in our lab, behind a NAT router with no port forwarding · Agent: pve-0.1.0
On the real service: the install, the tunnel, VM traffic leaving from the site's address, the kill switch, uninstall, and releasing the address.
We did not test on Starlink or real carrier CGNAT. We have no Starlink line. Our line was NAT without port forwarding, which behaves the same for inbound connections: you cannot forward a port. Also not tested: opening ports to a VM on the real service (see the full agent guide for that), clusters, IPv6 and speed. Addresses are documentation examples: 203.0.113.29 is your TunnelNet address and 198.51.100.77 the host's own line.
1. Install the agent
In the TunnelNet portal add a site, choose Proxmox VE as its router, and run the command from Router setup in the host's root shell. It finished in 14 seconds:
TunnelNet is set up: TEST-4863-pve carries the site now.
Put a VM on the network vmbr-tn with an address in 192.168.213.1/24's range and gateway 192.168.213.1,
then open its ports in the portal. Check any time with: tnet status
$ tnet status
Agent: running (version pve-0.1.0)
Tunnel: up, last handshake 1 s ago
Address: 203.0.113.29/32
Check-in: 9 s ago (ok)
Ports: 0
The tunnel came up through the NAT router with no change on the router. The full install, step by step, is in the TunnelNet agent for Proxmox guide, and the short version is Give a Proxmox VM a public IP without port forwarding.
Undo: /var/lib/tunnelnet/tn-pve uninstall.
2. The VMs use the public address; the host keeps its own line
Put a VM or container on the bridge vmbr-tn (address in 192.168.213.0/24, gateway 192.168.213.1). From inside it, ask any what-is-my-IP site, for example curl -s https://ifconfig.me:
01:52:07 CT 101 seen as: 203.0.113.29
01:52:08 host seen as: 198.51.100.77
Undo: set the VM's network device back to your usual bridge.
3. The kill switch
When the tunnel cannot be reached, VMs on vmbr-tn get no internet at all. They never fall back to your home line, so a VM that should only appear from the TunnelNet address cannot leak out from your own. We cut the tunnel two ways, by blocking it on the host and by taking the tunnel interface down:
01:52:47 before: CT 101 203.0.113.29 | host 198.51.100.77
01:52:52 hub unreachable: CT 101 none | host 198.51.100.77
01:53:34 back: CT 101 203.0.113.29
01:53:35 tunnel down: CT 101 none | host 198.51.100.77
01:54:06 back: CT 101 203.0.113.29
Each time it came back by itself, 16 to 18 seconds after the cut ended. The host itself kept its normal internet throughout.
4. Uninstall
$ /var/lib/tunnelnet/tn-pve uninstall
Left the TunnelNet network vmbr-tn in place: still used by ct 101,vm 102.
TunnelNet is removed from TEST-4863-pve.
The bridge is kept while VMs still use it, so nothing is deleted under them. The address stays on your site until you remove the site in the portal. We removed it, and the address was freed.
Limits
- One public address per site, shared by every VM on
vmbr-tn. - Outgoing mail on port 25 is blocked.
- Proxmox support is a pilot with no price yet.