IPsec Configuration Example - Tenant/NAT
IPsec tunnel configuration example within a VergeOS tenant using the dedicated UI IP address with NAT rules for directing tunnel traffic.
The following example configures an IPsec peer within a VergeOS tenant. In this example, the dedicated IP address used for accessing the tenant UI is also used for the IPsec tunnel, with NAT rules in place to direct tunnel traffic appropriately.
Host Configuration
Assigning the UI address to a tenant automatically creates rules on the host system (external and tenant networks) to channel traffic appropriately. No further configuration should be needed on the host.
VPN Network Configuration

Phase 1

Phase 2

Default VPN Network Rules
Default Firewall Rules - The following necessary firewall rules are created automatically when a VPN network is created:
Allow IKE: Accept incoming UDP traffic on port 500 to My Router IP
Allow IPsec NAT-Traversal: Accept incoming UDP traffic on port 4500 to My Router IP
Allow ESP: Accept incoming ESP protocol traffic to My Router IP
Allow AH: Accept incoming AH protocol traffic to My Router IP

Additional VPN Network Rules
Additional rules need to be created on our new VPN network:
VPN NAT Rule: 
Default Route Rule: 
VPN SNAT Rule: 
External Network Rules
Translate rules are necessary on the tenant's external network, to send IPsec traffic to the VPN network:
External UDP NAT Rule: 
External ESP NAT Rule: 
External AH NAT Rule: 
Connecting Internal Networks to the VPN
Routing can be configured between the VPN network and other internal networks to provide tunnel access to those networks; see How to Configure Routing Between Networks.
Last updated
Was this helpful?