Re: VPN Clients Can't Connect to Server when in VPN
Posted: Sat Sep 13, 2014 12:44 am
After struggling with this for the better part of a day I finally found the solution on an obscure post. I too was not able to connect to any services running on the server running SoftEther, although I was able to connect out to the Internet and to all other IP's on my LAN. To resolve this, like the documentation in section 3.6.11 says you have to create another physical interface. If you have a physical server that means installing another NIC if you dont have two already, in my case I'm using VirtualBox so I simply attached another virtual NIC to my VM's instance (which is attached to the same physical NIC on the host machine as the primary virtual NIC).
What the documentation doesn't tell you, is that this second NIC needs to be on a different subnet than your primary. So say your primary NIC's IP is 192.168.1.2, gateway 192.168.1.1. Your secondary NIC needs to be on for example 192.168.2.2, with gateway 192.168.2.1. Even though that gateway may well not exist (it doesnt in my case) this simple change fixed the problem and I am now able to SSH and access other services running on the VPN server. In Ubuntu 12.04 Linux I was able to modify my NIC config in /etc/network/interfaces to read:
auto eth2
iface eth2 inet static
address 192.168.2.2
netmask 255.255.255.0
gateway 192.168.2.1
dns-nameservers 8.8.8.8
Once your second NIC is up and running, just connect a local bridge from your virtual hub to the second NIC (eth2 in my case). You dont need to use a local bridge to the primary NIC, it is unnecessary. Hope it helps someone, and I also hope the fine developers at UoT can update section 3.6.11, and 11.1.2 of the manual to make this a bit more clear!
What the documentation doesn't tell you, is that this second NIC needs to be on a different subnet than your primary. So say your primary NIC's IP is 192.168.1.2, gateway 192.168.1.1. Your secondary NIC needs to be on for example 192.168.2.2, with gateway 192.168.2.1. Even though that gateway may well not exist (it doesnt in my case) this simple change fixed the problem and I am now able to SSH and access other services running on the VPN server. In Ubuntu 12.04 Linux I was able to modify my NIC config in /etc/network/interfaces to read:
auto eth2
iface eth2 inet static
address 192.168.2.2
netmask 255.255.255.0
gateway 192.168.2.1
dns-nameservers 8.8.8.8
Once your second NIC is up and running, just connect a local bridge from your virtual hub to the second NIC (eth2 in my case). You dont need to use a local bridge to the primary NIC, it is unnecessary. Hope it helps someone, and I also hope the fine developers at UoT can update section 3.6.11, and 11.1.2 of the manual to make this a bit more clear!