Hi TP-Link team,

I'd like to request support for Port Forwarding on VPN client interfaces, such as L2TP, IPSec, OpenVPN, and WireGuard, on Omada routers.

Why is this important?

In my case, I have a internet connection with a dynamic IP address.
To get a static public IP, I use an L2TP VPN client connection provided by my provider.

The VPN connection works perfectly, and I can route outgoing traffic from internal hosts through the VPN interface using Policy Routing.

However, I cannot forward incoming traffic (e.g. ports 80, 443, 25, 587, 993) to internal hosts, because the VPN interface is not available in the Port Forwarding (NAT) section. It is only selectable in ACL, Static Route and Policy Routing.

This limits the possibility to use VPN-based static IP setups for self-hosting and remote access scenarios.

Feature request:

Please make VPN client interfaces (L2TP, IPSec, OpenVPN, WireGuard) available as WAN interface in the Port Forwarding / NAT rules, just like the regular WAN interfaces.

Use case example:

• Router model: TP-Link Omada ER7412-M2
• WAN: dynamic IP (DSL)
• VPN: L2TP Client (static public IP from provider)
• Goal: Host a server such as reverse proxy, mail server, etc
• Problem: Incoming connections to the VPN public IP cannot be forwarded to internal servers

Allowing this feature would benefit many users who rely on VPN-based static IPs (for self-hosted services or remote access) especially in dynamic IP environments.

Thank you for considering this request!

Best regards