Softethervpn: [Solved] Error occurred. (Error code: 31)

Created on 24 Apr 2015 · 9Comments · Source: SoftEtherVPN/SoftEtherVPN

Im getting this on my 64bit gentoo box, any idea how to solve it?
I also get the same thing even with vpncmd running as root

~# vpnclient start
~$vpncmd
or
~# vpncmd

Select 1, 2 or 3: 2

Specify the host name or IP address of the computer that the destination VPN Client is operating on.
If nothing is input and Enter is pressed, connection will be made to localhost (this computer).
Hostname of IP Address of Destination:

Connected to VPN Client "localhost".
VPN Client>remoteenable
RemoteEnable command - Allow Remote Management of VPN Client Service
The command completed successfully.

VPN Client>niccreate
NicCreate command - Create New Virtual Network Adapter
Virtual Network Adapter Name: test

Error occurred. (Error code: 31)
Installation of the Virtual Network Adapter device driver failed.

VPN Client>

Source

gulbuhar

👍4

Most helpful comment

For what it's worth, I ran into this issue using Ubuntu 16.04 LTS and solved it via...

sudo modprobe -v tunnel4
sudo modprobe -v ip_tunnel
sudo /usr/local/vpnclient/vpnclient stop
sudo /usr/local/vpnclient/vpnclient start
/usr/local/vpnclient/vpncmd

NOTE: this change is only temporary and after a reboot these kernel modules will be removed again. You can auto-load them on every reboot by adding them permanently to /etc/modules via:

echo -e "tunnel4\nip_tunnel" | sudo tee -a /etc/modules

nerdyness on 18 Dec 2017

👍6

All 9 comments

i just find the solution
TUN/TAP needs to be enabled to create Virtual Network Adapter to do so
regenerate the kernel with

Device Drivers --->
Network device support --->
[*] Universal TUN/TAP device driver support

gulbuhar on 24 Apr 2015

👍2

excuse me, how do you solve this problem finally? I met this problem before, but I haven't found a solution yet.

Pireirik on 11 Sep 2016

@Eric7Coding runing sudo ./vpnclient start before ./vpncmd worked for me

Palciny on 30 Oct 2016

@Eric7Coding depends on your Linux distro, but as @gulbuhar mentioned, you might need to enable tun/tap in the kernel and recompile and install the kernel

moatazelmasry2 on 22 Nov 2017

For what it's worth, I ran into this issue using Ubuntu 16.04 LTS and solved it via...

sudo modprobe -v tunnel4
sudo modprobe -v ip_tunnel
sudo /usr/local/vpnclient/vpnclient stop
sudo /usr/local/vpnclient/vpnclient start
/usr/local/vpnclient/vpncmd

NOTE: this change is only temporary and after a reboot these kernel modules will be removed again. You can auto-load them on every reboot by adding them permanently to /etc/modules via:

echo -e "tunnel4\nip_tunnel" | sudo tee -a /etc/modules

nerdyness on 18 Dec 2017

👍6

For someone using WSL (Windows Subsystem for Linux), this does not entirely work. What could be some other workaround? Creating a virtual NIC in windows and somehow mapping it into the VPN client?

seanlowe on 1 Sep 2018

Sorry, I can't help you out here. The way I see it you have two options here:
1) Use the Windows Client
2) Run Linux in a VM (on VirtualBox, Hyper-V, or the like)

nerdyness on 2 Sep 2018

Yeah, those were my thoughts too. Thanks for the input!

seanlowe on 3 Sep 2018

The Ubuntu 16.04 solution did not work for me on Ubuntu 18.04. Did anyone manage to run the vpnclient on Bionic?