Expose OpenVPN client tunnel as WAN interface and allow VLAN/SSID routing through it.
Hello TP-Link team,
I’d like to request a feature enhancement for the ER706W (Omada AX3000 Gigabit VPN Gateway), specifically regarding VPN client functionality.
Enable the ability to route traffic from specific VLANs or SSIDs through an active VPN client tunnel (e.g., OpenVPN, L2TP, PPTP). Ideally, the VPN tunnel should be exposed as a WAN-type interface so it can be used in:
• Policy Routing
• Link Backup
• Static Routes
• VLAN-to-VPN mapping
This would allow administrators to isolate traffic from a guest SSID or a secure VLAN and route it exclusively through a VPN tunnel, a common requirement in multi-tenant, remote access, or privacy-focused deployments.
While the ER706W supports VPN client mode (including OpenVPN), the tunnel is not exposed as a routable WAN interface. As a result:
• VPN client connections cannot be selected in policy routing rules.
• VLANs and SSIDs cannot be bound to VPN tunnels.
• The tunnel cannot be used in Link Backup or Load Balancing.
• CLI access does not expose OpenVPN interfaces or allow manual routing to the tunnel.
This limits the flexibility of the VPN client feature and prevents advanced routing scenarios that are increasingly common in modern deployments.
Suggested Enhancement:
• Treat VPN client tunnels as virtual WAN interfaces.
• Allow VLANs and SSIDs to be routed through these tunnels via policy routing or static routes.
• Expose tunnel interfaces in CLI for advanced users.
• Add GUI options to bind VLANs or SSIDs to VPN tunnels.
This feature would greatly enhance the utility of the ER706W and align it with the needs of power users and network professionals.
Thanks for considering this request!