TunnelNet Guides

Give a Proxmox VM a public IP without port forwarding (tested)

2026-11-22

If your internet line shares one address between many customers, or you simply cannot forward ports on your router, nobody outside can reach a VM on your Proxmox host. This page shows a way that needs nothing from your router: the host makes an outgoing connection 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 (kernel 6.8.12-43-pve) 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 from the portal's command, the tunnel, VM traffic leaving from the site's address, uninstall, and releasing the address. On our own test copy of the service: picking the VM by name, and opening and closing ports. Not tested: clusters (one node only), a Proxmox ISO install, IPv6, speed. All addresses here are documentation examples: 203.0.113.29 is your TunnelNet address and 198.51.100.77 the host's own line. 192.168.213.0/24 is the agent's built-in VM network.

How it works

The Proxmox host keeps an outgoing tunnel to TunnelNet. The agent puts the VMs you choose on an isolated bridge, vmbr-tn, behind that tunnel. Visitors reach the ports you open on those VMs, and the VMs' own traffic leaves from the same address. The host's own login (port 22) and web screen (port 8006) are never reachable on it.

This page is the short version. The full walk-through, with the kill switch and a cluster note, is in the TunnelNet agent for Proxmox guide.

1. Make the install command

In the portal add a site, choose Proxmox VE as its router and open Router setup:

curl -fsSL https://tunnelnet.io/business/proxmox/install.sh | sh -s -- <your code>

The code works once and expires after 30 minutes.

Undo: remove the site in the portal.

2. Run it on the host

Paste the command into a root shell on the Proxmox host. Real output:

TunnelNet is set up on this gateway. Your site will show Connected in the portal shortly.
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
rc=0 seconds=14

About 50 seconds later, tnet status:

Agent:      running (version pve-0.1.0)
This node:  TEST-4863-pve, carries the site
Tunnel:     up, last handshake 1 s ago
Address:    203.0.113.29/32
Check-in:   9 s ago (ok)

Undo: /var/lib/tunnelnet/tn-pve uninstall.

3. Put the VM on vmbr-tn

In Proxmox open the VM, Hardware, Network Device, and choose the bridge vmbr-tn. Inside the VM use an address in 192.168.213.0/24 (we used 192.168.213.11/24) and the gateway 192.168.213.1. For a VM made with Proxmox cloud-init, this is the command we ran:

qm set 102 --net0 virtio,bridge=vmbr-tn --ipconfig0 ip=192.168.213.11/24,gw=192.168.213.1

What the outside world sees, from a container on the bridge and from the host:

CT 101 seen as: 203.0.113.29     <- the site's address
host seen as:   198.51.100.77    <- the host's own line, unchanged

Expect about 15 to 30 seconds with no internet right after the install, while the agent finishes its first check-in.

Undo: set the network device back to vmbr0.

4. Open a port to the VM

In the portal open Ports, pick the VM by name (ours was TEST-app102), a public port (8083) and the VM's port (8081). From an outside machine:

01:46:08 before opening: visitor -> site:8083: (no answer)
01:46:21 visitor -> site:8083: TEST-app102 says hello   (8 s after opening)
01:46:33 after closing:  visitor -> site:8083: no answer (12 s after closing)

The host's own ports 22 and 8006 gave no answer on the site's address.

Undo: delete the rule on the same page.

What went wrong for us

  • The first install refused. Our host's /etc/network/interfaces had no source /etc/network/interfaces.d/* line, because it was built from a cloud image. Adding that line fixed it.
  • The installer's advice was wrong at that point. It suggested making a bridge called vmbr-tn in Proxmox by hand. Proxmox only accepts names like vmbr1 there, so do not follow that advice; add the source line above instead. A clearer message is coming.

Limits

  • One public address per site, shared by every VM on vmbr-tn. Two VMs cannot both use public port 443.
  • A VM sees visitors as coming from TunnelNet, not from the visitor's own address.
  • Outgoing mail on port 25 is blocked.
  • Proxmox support is a pilot with no price yet.