SoftEther VPN User Forum

1.Install softether VPN Server inside that 34.96.100.11 machine in system mode

2.Install https://r1ch.net/projects/forcebindip

3.https://download.vpngate.jp/common/cd.a ... 164560.zip

4.Config the VPN Client IPv4 properties with interface metric with a very large number larger than the local NIC to internet 34.96.100.11 for example 9999,in this way,even if the routing default gateway is modified by softether client,the os will still not use this route as a primary default gateway route[important]

5.Connect 219.100.37.58:443,in softether VPN Client,but keep No adjustments of routing table box unchecked.
because interface metric is sky high the windows os do not change default routes and gateway to default internet gateway at all,34.96.100.11 will remains accessiable by ssh or rdp

6.change the cmd working directory to forcebindip64.exe install directory ForceBindIP64.exe 10.236.25.51 C:\SE\So\vpnserver.exe /usermode [10.236.25.51] is the vpn client internal ip address

7.at this point,any clients using VPNazure.net services into my 34.96.100.11 with virtual HUB [bridge] with vpnmymachine.vpnazure.net will get ip address 219.100.37.58,note:they're not using any ip address in my 34.96.100.11 machine at all but still gets an 219.100.37.58,in this case the actual thing is ForceBindIP64.exe did the job,so it's still bypass the softether limits.

8.And yes,the connection is working very fine,no need to modify anything,just forcefully to make softether server to use 10.236.25.51 not 10.0.0.1,so it's not hard,and you can see my VPN Server program is forcefully using the 10.236.25.51 interface to make any outgoing connections to any softether servers [including 130.158.6.51],so in such case 219.100.37.58 is still forcefully used [you can check whether it is with https://systeminformer.sourceforge.io/]

Look here , the VPN Server is forcefully running on local NIC 10.236.25.51,there's no reason for my server not to have a public ip 219.100.37.58

So i'm actually changing the softether server in windows just allowed to use 10.236.25.51 only not to use 10.0.0.3 public internet NIC at all

How easy is this? Only 1 exe will do the job！

Look here,client ip address[source host]is not my machine local 10.0.0.1 public internet NAT NIC any more,instead it's the VPN Client NIC responsible for creating the connection！

and yes,all policy is bypassed now just with 2 clicks in windows machine,no high tech savvy things included at all,just forcefully make softether use 10.236.25.51 don't allow it to use 10.0.0.3 at all,this is all what's needed!

SID-VPN-6322 is a VPN Session created by the 219.100.37.58 session,not my machine,this is what i'm trying hard to trick softether to do:Local Mac address spoofing,and it works safe and sound,everyone's happy now!

The SID-VPN-6322 is able to populate any mac ip table entries it wants and mac spoofing is so confortable to archive,and by the way your advices are very helpful for me,still,thank you,i should find more way to trick softether into working in such local spoofing modes