Package Details: softethervpn-client-manager v4.34_9745-1

Git Clone URL: (read-only, click to copy)
Package Base: softethervpn-client-manager
Description: SoftEther VPN Client Manager
Upstream URL:
Licenses: Apache
Submitter: net147
Maintainer: net147
Last Packager: net147
Votes: 6
Popularity: 0.043251
First Submitted: 2018-01-02 06:34
Last Updated: 2020-07-06 04:31

Latest Comments

1 2 Next › Last »

adevries17 commented on 2020-01-02 16:20

@net147 the service was disabled. I got it working thank you!

net147 commented on 2019-12-31 23:07

@adevries17 softethervpn-client.service should be running from softethervpn package or if the client is running on another system, use vpncmgr-remote instead of vpncmgr.

adevries17 commented on 2019-12-31 17:25

Every time I try to launch the package, it comes up with "Unable to connect to the VPN client service operating on the local computer" Which service(s) should be running?

net147 commented on 2018-03-08 13:20

@nfs hamcore.se2 and vpncmgr.exe is now automatically extracted from the Windows installer so there is no need to do it manually now.

nfs commented on 2018-03-07 05:16

@net147: Thanks for the info and clarification regarding systemd-networkd. It turns out that dhclient actually works fine and I can finally connect to my vpn server by tethering to my cellphone. My real problem was figuring out how to adjust the routing table. After I finally did, I wrote a little bash script to call dhclient on the vpn adapter, then it creates a new route to the vpn server via my cellphone adapter default gateway, deletes the default route, and creates a new default route via the gateway of the VPN adapter. This finally really got it working quite well. My internet ip address appears to be the server's address instead of the cellphone provided ip, and I can also access my LAN.

net147 commented on 2018-02-14 02:34

@nfs I just create a systemd-networkd profile based off but using the VPN's interface name and restart systemd-networkd service. When I connect using the SoftEtherVPN client manager, systemd-networkd automatically configures the interface according to the profile (e.g. using DHCP).

Note the link you referred to does not use systemd-networkd at all.

nfs commented on 2018-02-14 02:28

@net147: Thanks for responding. My knowledge of networking details is not high, but I would have imagined that there would be a relatively easy way to get NetworkManager to handle a vpn client, as it appears to be able to take vpn connections for openconnect, vpnc, and fortisslvpn vpn types by default.

Given that you avoid NetworkManager in favor of systemd-networkd, maybe it's not so easy to configure. . . Unfortunately, there is no wiki for configuring the softether client on Arch at all, but I found the following which uses systemd-networkd for a softether client:

Is this the sort of configuration approach you would recommend?

net147 commented on 2018-01-26 09:36

@nfs SoftEtherVPN client does not include DHCP client. You will have to configure your operating system to request DHCP lease when the VPN connects. I use systemd-networkd for the VPN connection and NetworkManager for everything else.

nfs commented on 2018-01-26 09:23

Still can't get this working. The client appears to be connected; the server thinks it's assigned an address (using securenat), but on the client side (Tools, Network Device Status) it shows the ip address, subnet mask, gateway, and dhcp server as Any pointers? I'm using NetworkManager.

net147 commented on 2018-01-08 01:00

@nfs You need to install VPN Client Manager for Windows using a Windows system or wine, then copy the files to the PKGBUILD directory. They use a custom installer. There is an issue open to add a ZIP package so I can use to obtain the files more easily -