So I have an SSTP (with native Windows client) working fine in a sense. My windows client's local IP is , so its local network is: 192.168.10.x

The Remote VPN server is behind a router and its IP address is

When I connect to the VPN server from the Windows client it makes the SSTP VPN connection just fine over port 443 and then I can ping from the windows client. I can even connect to and login to the Router that control's the VPN server's LAN. I can ping and connect to any other server/pc on the VPN server's local lan, ie 192.168.12.x from my Windows vpn CLIENT which was given an IP of

The problem is that from the Windows vpn client I can NOT ping which is the VPN server's real internal ip. Also, the VPN server can not ping either. I've tested firewall issue, disabled all firewalls and no difference.

Some pertinent details: VPN SERVER: Softether VPN VPN SERVER: Is a Virtual Machine running under qemu-KVM, the host has br0 bridged networking. After reading some posts, I did an ifconfig eth0 promisc on the kvm HOST to enable promiscuous mode but that made no difference. But I did not yet "reboot" Host or libvirt kvm "virtual machine" which runs centos.

I do NOT have "SecureNAT" enabled on the Softether VPN server. I did create a "Local Bridge" with eth0 (interface in the kvm virtual machine which runs the vpn server). For the VirtualHUB I also disabled the setting "ManageOnlyPrivateIP" and set it to 0 so that my VPN windows client would be served a 192.168.12.x ip address. Otherwise I think it would get from the VPN server. (strange I just gave that value back to default of 1 and my vpn client still gets from vpn server)

When I look at the VPN connection details on the Windows VPN client, strangely its impossible to get the true IP of the VPN server. It says its some fake dummy ip. I've read somewhere that perhaps the VPN server would give itself another arbitrary IP address in the 192.168.12.x range , (hopefully not which is the lan IP of the internet ROUTER on the VPN server's local lan). Anyway from what I read its impossible to know what IP address in the 192.168.12.x range this Softether VPN server would assign itself since it hides its vpn network stacks, ie you can't see ppp0 etc with ifconfig like you would with strongswan openswan etc IPsec l2tp which I've used before successfully (and am still using on other servers).

  • well made some progress, I can do a local tap device ie local bridge using tap_vpn etc and run dnsmasq to give ip out and I can make a 192.168.13.x new subnet and then I can have SSTP where I can talk direct with the VPN server but then I can't talk to the rest of the PC/server on the remote local lan where VPN server is. To do that I'm back to above problem where I can do local bridge on my VPN's eth0 but then my windows vpn client can't ping or connect to the VPN server just to the other systems on that remote lan. Why can't I have both :D – htfree Apr 17 '15 at 2:59
  • Hurray, more progress. I got it to work if I manually add a route on the Windows client PC after connecting. So basically I setup SSTP VPN tunnel with local bridge on tap and setup dnsmasq etc my client would get and the VPN server would be and they can communicate freely between and when I added 'manually' the route for 192.168.12.x on my windows client with gateway of then I can talk with the rest of PC/servers on the remote lan also. So works, only thing left is to see why dnsmasq and vpnbridge etc can't make do this for windows auto. on connection. – htfree Apr 17 '15 at 4:25



DO NOT OVERWORK entire week long 16-18hours a day until 4:30am and expect your brain to not be FRIED! IT WAS A STUPID WINDOWS FIREWALL ISSUE!!! YES, I "THOUGHT" I had disabled it but apparently I was too sleepy to have noticed I only disabled domain and maybe outgoing but not incoming firewall!

OK, I'm going to try and get some sunlight today, guess brain needs it??!

To all the sys-admins out there, if it don't work stop banging your head and go partying a while (or sleep!), come back bit refreshed and things will work out! :)

  • If this is solved, please mark it as such by ticking the check mark at the left so that it turns green. – Michael Hampton Feb 19 '18 at 19:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.