Connect to SoftEther server via SSH after connected to VPN

Post your questions about SoftEther VPN software here. Please answer questions if you can afford.
Post Reply
johhen
Posts: 2
Joined: Mon Apr 21, 2014 9:13 pm

Connect to SoftEther server via SSH after connected to VPN

Post by johhen » Mon Apr 21, 2014 9:30 pm

I use SoftEther on RaspberryPi's to allow VPN access to my family member's homes. However, I do not seem to be able to VPN to the IP address of the host running the VPN while I am connected to the VPN. If I VPN to another server on the network, I can then VPN back to the server. Is there a configuration I need to change to allow this? This would allow me to minimize the number of external ports I need to open!

I set the SoftEther servers up with the following command sequence:
ServerPasswordSet ADMINPASSWORD
HubCreate VPN /PASSWORD:
hubdelete default
Hub VPN
UserCreate USERNAME /GROUP:none /REALNAME:none /NOTE:none
UserPasswordSet USERNAME /PASSWORD:TESTPASS
OpenVPNEnable no /PORTS:1194
sstpenable no
bridgecreate VPN /DEVICE:eth0 /TAP:no
ipsecenable /L2TP:yes /L2TPRAW:no /ETHERIP:no /PSK:TESTSECRET /DEFAULTHUB:VPN
keepdisable
vpnovericmpdnsenable /ICMP:no /DNS:no
listenerdelete 1194
listenerdelete 5555
listenerdelete 992
ServerCipherset AES256-SHA
flush
exit



Thanks.

qupfer
Posts: 202
Joined: Wed Jul 10, 2013 2:07 pm

Re: Connect to SoftEther server via SSH after connected to V

Post by qupfer » Mon Apr 21, 2014 10:34 pm

Did you read the manual? Specialy Part 3.6.11?

johhen
Posts: 2
Joined: Mon Apr 21, 2014 9:13 pm

Re: Connect to SoftEther server via SSH after connected to V

Post by johhen » Mon Apr 21, 2014 11:45 pm

I did not see the notes at the bottom there - my mistake. I did not know exactly what I was looking for in the manual - I did look in chapter 3.6 a few times, but did not read it cover to cover.

My understanding based on 3.6.11 is that to be able to do what I am desiring I would require either a second physical network interface to the raspberrypi, or creating a tap device? I did not have this limitation (at least, it wasn't something I manually had to configure, if the tap option is what was used) when I used xl2tpd for an L2TP+IPsec vpn on the same kernel, which leads to my confusion.

Post Reply