Pushing Routes via SecureNAT/DHCP to Use Client's Local Gateway (Instead of VPN Gateway)

[masoel00]

I'm using SoftEther VPN with SecureNAT enabled (including the Virtual DHCP Server) to manage client connections. My goal is to push a specific route (e.g., 192.168.1.0/24) to the client, instructing it to use its own local default gateway (e.g., 10.45.1.1) instead of the VPN server's virtual gateway (192.168.30.1).

Network Setup:

The client is on a local network: 10.45.1.0/24 (default gateway: 10.45.1.1).
Another network, 192.168.1.0/24, is reachable via the client's local gateway (10.45.1.1) on a different VLAN.
The VPN server and its SecureNAT reside in a completely different network space.
Currently, if I push 192.168.1.0/24 via SecureNAT's static routes, the client attempts to route it through the VPN tunnel, which is not what I want.

Manually adding the route on the client (route add 192.168.1.0 mask 255.255.255.0 10.45.1.1) works perfectly, but not scalable when deployed to many clients, where users are not able to add local routes.

Question:
Is there a way, either through the GUI, vpncmd, or a configuration tweak, to tell SoftEther's DHCP server to push a route that resolves to the client's local default gateway? Alternatively, is this a feature that would need to be implemented (e.g., similar to OpenVPN's net_gateway directive)?

[suddhasilsarkar]

viewtopic.php?f=7&t=68027&p=97816&#p97816