If your corporate VPN access is via a Fortigate appliance’s proprietary SSL VPN there’s chances you’re using the vendor provided client. Too bad that one doesn’t really plug into modern Linux desktop experience; it’s CLI only and you’re not able to customize the network configuration too much. There’s no source code and thus no way you’ll be able to do anything about it.
With the availability of the new VPN plugin NetworkManager-fortisslvpn we address this. On its backend it uses the free software protocol implementation openfortivpn (thanks to Adrien Vergé) that got some major improvements lately and integrates well with NetworkManager.
Both openfortivpn and the NetworkManager-fortisslvpn plugin will be available in Fedora in next few days; the other distributions will hopefully follow.
New major version if NetworkManager, a service that manages your network connectivity is being released in coming months. This might be a good time to talk about the changes you can expect.
A simple client tool has been introduced with the release of NetworkManager version 0.8.1. Since then it has improved to the point it’s able to configure all functionality provided by the service. It can be used to control the daemon, manage the connections and create complex network configurations.
It’s accompanied by extensive documentation in nmcli(1) and nmcli-examples(1) manuals. Since the big overhaul in 0.9.10 release, we’re keeping the format of command line arguments compatible, guaranteeing your scripts that use it will keep working. Nevertheless, we’ve made some changes that make it easier to use.
Compared to the previous release it’s a rather small release, weighing just a little short of 160 commits. Nevertheless, we’ve included a fair amount of fixes and improvements from both the NetworkManager Team and the community.
While the stable series is mainly focused on improving robustness we’ve added some features too, making NetworkManager a bit more flexible and easier to use:
Improved capture portal detection. The capture portal now understands the RFC6585 HTTP 511 status code.
Default route through WiFi connection is now preferred to Mobile Broadband if both are available.
We now expose information on whether a particular connection is metered. It’s intended for tools like package managers that like pre-fetch large amount of data to be able to avoid increasing your Mobile connectivity bills.
NetworkManager can now configure Wake-on-LAN capabilitites of Ethernet hardware.
The release will likely find its way to your distribution’s mirror near you soon. It’s queued for Fedora 23 that’s expected to arrive later this year and also available in Fedora 22 testing repository, Other distributions will likely follow soon.
There’s more exciting features coming with NetworkManager 1.2 later this year. Stay tuned!
We recommend everyone to update and will appreciate any feedback!