3
Votes

Expose OpenVPN client tunnel as WAN interface and allow VLAN/SSID routing through it.

 
3
Votes

Expose OpenVPN client tunnel as WAN interface and allow VLAN/SSID routing through it.

Expose OpenVPN client tunnel as WAN interface and allow VLAN/SSID routing through it.
Expose OpenVPN client tunnel as WAN interface and allow VLAN/SSID routing through it.
Thursday - last edited Thursday
Tags: #ER706W
Model: ER706W  
Hardware Version: V1
Firmware Version: 1.2.2 Build 20250821 Rel.60581(5553)

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!

 

#1
Options
2 Reply
Re:Expose OpenVPN client tunnel as WAN interface and allow VLAN/SSID routing through it.
14 hours ago

  @demontanaro 

Thank you for your feedback.
At present, the PPTP/L2TP client already appears as a virtual-WAN interface and can be used in Policy Routing.
When you create a PPTP/L2TP/OpenVPN client profile, you can also decide which local networks will be forwarded through the tunnel by customizing the “LAN Network” field.
I will forward your additional suggestions to the relevant team for further evaluation.

 

Thank you for taking the time to share your insights within the TP-Link Community. Your feedback is greatly appreciated and has been formally documented and escalated to our Product Development Division for thorough evaluation.

At this juncture, we are unable to confirm whether the requested enhancement will be implemented or to provide a definitive timeline. We appreciate your understanding of the complexities inherent in our product-planning and development cycles.

Should you have any further suggestions or additional context to offer, please feel free to share them here. All supplementary input will be consolidated and forwarded to the relevant teams for continued consideration.

#2
Options
Re:Expose OpenVPN client tunnel as WAN interface and allow VLAN/SSID routing through it.
3 hours ago

Thanks @Ethan-TP 

 

 

#3
Options

Information

Helpful: 3

Views: 55

Replies: 2

Voters 3

voter's avatar
voter's avatar
voter's avatar

Tags

ER706W