![]() ![]() This is because the vpnserver wasn't properly managing the up/down state of the interface. Normally there are other OS-level services (like NetworkManager) that handle this thing for you, but I couldn't get any of them to work for SoftEther. Since posting all of this though, I've got an even better option. ![]() So SoftEther will be connected internally but you'll have no way to make use of that connection. So if you use an init script to start the vpnserver, you'll find that it's up and connected, but you have a VPN interface with no IP address or routes. But this clearly doesn't work for non-interactive startup. The documentation recommends that you manually start dhclient and make the necessary routing table changes after connecting. The Windows client automatically handles DHCP and routing, but the Linux client does not. Install this as /lib/systemd/system/rvice and then use systemd enable rvice to enable it. Use make -C tmp & make -C tmp package to build an OS-specific package (rpm or deb) which includes this, and systemd enable rvice so it always starts on reboot. This depends on using the bundled rvice in the latest releases on github. Now SoftEther automatically connects on startup, and dhclient starts right after. Then I made my VPN connection a "startup connection" in the VPN client config. So instead I created a systemd unit file to start dhclient automatically with SoftEther. I'm doing this on an Ubuntu server and I spent a long time trying to get netplan (and/or NetworkManager directly) to own the SoftEther interface, but I just couldn't get it to work. As everyone knows, the Windows client automatically handles DHCP and routing, but the Linux client does not. I just want to share a configuration for a Linux host with an always-on SoftEther client.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |