0
Votes

Option to add Static Routing / Port Forwarding against Client VPN Interface (for me it WG_C)

 
0
Votes

Option to add Static Routing / Port Forwarding against Client VPN Interface (for me it WG_C)

Option to add Static Routing / Port Forwarding against Client VPN Interface (for me it WG_C)
Option to add Static Routing / Port Forwarding against Client VPN Interface (for me it WG_C)
11 hours ago
Model: Archer BE400  
Hardware Version: V1
Firmware Version: 1.0.9 Build 20250417 rel.46306(5553)

Hi,

@Kevin_Z

Last week, I upgraded my Archer C90 router to the BE400 as I was looking for enhanced security features—specifically configurable DoH/DoT and VPN support. I have configured the router and am very satisfied with its performance, especially the ability to use my personal DoH server hosted on Azure. I am currently running it in Ultra Secure Mode, and I also use the router to connect to my WireGuard VPN hosted on Azure.

 

I also noticed that I can access the router’s management console (with remote management enabled) and SMB service through the VPN IP, which works perfectly from Azure. However, I am unable to expose any other services hosted on my LAN. When I configure port forwarding, the ports are exposed only on the WAN side. Since my ISP uses CGNAT, my WAN IP is actually private and not directly accessible from the internet.

 

If port forwarding or routing rules could be applied directly against the VPN interface, it would allow LAN-hosted services to be exposed via VPN. This would be a very valuable feature to have.

 

I kindly request that you consider adding this capability in a future firmware update. I would also be happy to participate in beta testing if needed.

 

Thank you for your support.

Regards, Saugata D.
#1
Options