How to route SoftEther traffic through another VPN?

[xodc]

I have a VPN software (LetsVPN) that will only allow me to have 2 devices to connect to my account. I installed its software on a Windows 11 machine, and noticed it created a tap network device for its connection. Is it possible to install SoftEther Server on this Windows 11 computer, so that any client that connects to SoftEther also has its traffic routed through LetsVPN?

Thanks!

[solo]

Try to hotspot the tap. As for SE server, it is easily achievable on Linux and we have discussed it numerous times on this forum. It should work on any Windows server edition with RRAS. It may work on W11 with 3rd party software like https://www.nat32.com/

[solo]

Here is a quick Windows RRAS VPN sharing test without local DHCP, connecting to VPN Gate. LetsVPN or any other service will also work.

[SE client] --->
[SE client] ---> [SE server ---> RRAS ---> SE client] ---> [VPN Gate server]
[SE client] --->

INITIAL SERVER PRESET

- install MLA https://learn.microsoft.com/en-us/troub ... ck-adapter
- assign a static IP to it, eg 192.168.22.2
- bridge SoftEther's hub to it

net stop "Routing and Remote Access"

- connect to VPNGATE
- note VPNGATE routing

Code: Select all

netstat -r
Network Destination        Netmask          Gateway       Interface  Metric
   219.100.37.193  255.255.255.255         10.0.2.2        10.0.2.15      1

- disconnect VPNGATE

net start "Routing and Remote Access"

- enter the route in RRAS "Static Routes" section
- add MLA and VPN NIC in RRAS "NAT/Basic Firewall" section
- set VPN NIC to public interface with NAT
- set MLA to private interface


START VPN SHARING

- connect to VPNGATE
- check logs

Code: Select all

netstat -r
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0   10.245.254.254    10.245.90.216      1
         10.0.2.0    255.255.255.0        10.0.2.15        10.0.2.15     10
     192.168.22.0    255.255.255.0     192.168.22.2     192.168.22.2     30
   219.100.37.193  255.255.255.255         10.0.2.2        10.0.2.15      1

ipconfig

Ethernet adapter MLA:
   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 192.168.22.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter VPN - VPN Client:
   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 10.245.90.216
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 10.245.254.254

Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix  . : home
   IP Address. . . . . . . . . . . . : 10.0.2.15
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

CLIENT VPN CONNECTION TO THE SHARING SERVER

- this test is using a static IP for simplicity

Code: Select all

ipconfig
Unknown adapter VPN - VPN Client:
   Connection-specific DNS Suffix  . :
   IPv4 Address. . . . . . . . . . . : 192.168.22.3
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

route add 9.9.9.9 mask 255.255.255.255 192.168.22.2

ping 9.9.9.9
Pinging 9.9.9.9 with 32 bytes of data:
Reply from 9.9.9.9: bytes=32 time=434ms TTL=56
Reply from 9.9.9.9: bytes=32 time=383ms TTL=56
Reply from 9.9.9.9: bytes=32 time=562ms TTL=56
Reply from 9.9.9.9: bytes=32 time=333ms TTL=56

tracert 9.9.9.9
Tracing route to dns9.quad9.net [9.9.9.9] over a maximum of 30 hops:
  1     3 ms     2 ms     2 ms  192.168.22.2
  2   354 ms   321 ms   326 ms  10.245.254.254
  3   327 ms   328 ms   327 ms  gw2.vpngate.v4.open.ad.jp [219.100.37.253]
  4   558 ms   574 ms   592 ms  igp1.green.v4.open.ad.jp [202.222.12.190]
  5   331 ms   325 ms   338 ms  bgp3.openospf1.v4.open.ad.jp [202.222.12.33]
  6   361 ms     *      328 ms  150.99.184.33
  7   376 ms   326 ms   347 ms  150.99.10.187
  8   364 ms   341 ms   358 ms  as42.ix.jpix.ad.jp [210.171.224.117]
  9   420 ms   585 ms   557 ms  dns9.quad9.net [9.9.9.9]
Trace complete.

1.png

2.png

3.png

4.png

5.png