Introducing the IVPN client v2.4 for Windows & OSX

Releases By Ed Holden | Posted on November 26, 2015

We’re thrilled to releasing major new updates to our IVPN client for Windows and OSX. We’ve listened carefully to customers and this release addresses almost every feature request we’ve had in the past year. We’ve put extra effort onto the OSX client as it has previously not received as much attention as the windows client. That’s also changing as both clients are built from a common code base. All future releases of the IVPN client software will be for both OSX and Windows at the same time. To facilitate this we have aligned the OSX client version with that of the windows version, 2.4

Full mesh Multi-hop network support

For both clients, we have introduced the capability to multi-hop on our new full mesh network. When you connect to an entry server using multi-hop, your traffic will be routed securely and directly to the exit server for maximum performance (no intermediate servers). Both IVPN clients have updated versions of OpenVPN and the obfsproxy transport (useful if you’re in China etc.) and a significant number of bugs have been squashed making this by far the most stable release we have published.

IVPN Firewall - Robust leak protection for OSX

The OSX client has the same robust IVPN Firewall that we introduced for the Windows client earlier this year. The IVPN Firewall ensures full protection against data leaks by implementing low level firewall rules using OSX’s native PF firewall. It doesn’t matter if your connection drops or  your network configuration changes, the only exit for packets is through the VPN tunnel until it is explicitly disabled, providing a significant increase in your privacy and security.

The firewall is independent of the IVPN client so even if a component of the IVPN Client crashes filtering will continue uninterrupted. The IVPN Firewall can be configured to switch on automatically during VPN connection or you can enable it manually when you need it. You can even configure the ‘always-on’ IVPN Firewall so it starts before any other processes, ensuring that no traffic will bypass the VPN tunnel even during the boot up phase.

In addition, the IVPN Firewall protects against data leaks as a result of network configuration and routing table changes, IPv6 leaks and software crashes. For more information about how these types of leaks occur see our previous post on the IVPN Firewall for Windows.

New UI for OSX

Home screen for IVPN Client

IVPN client connected

IVPN client - exit selection

OSX client preferences

Apps
We invite you to discuss this post in our Reddit community or on Twitter. You can also send your feedback to blog@ivpn.net.

11 Comments

Maarten Billemont

30.11.2015

Wonderful news!

Are there any plans to publish the source code for these clients under a Free Software license so that we can build it ourselves and don’t need to rely on pre-built binaries?

Mr. A. Dog

15.12.2015

I am very happy that you have the Firewall features in Mac OSX now. Bravo!

MK

04.04.2016

The firewall feature is excellent. Thank you! I now have version 2.6 on OSX, and I have 2 feature suggestions:

  1. If there were some way to see what the current upload / download speed is. Perhaps this could be done via mousing-over the iVPN icon (just as with the Tunnelblick icon).

  2. If it were possible to have a sound play upon connection and a (different) sound play up on disconnection. I liked this about Tunnelblick.

Thank you!

Gerhard

16.06.2016

Please also brings a client for Ubuntu / Kubuntu … out.

SmallTownPleb

26.07.2016

Is macOS Sierra compatible with this client? I know this new OS broke my Logitech peripherals.

Ed Holden

26.07.2016

Not yet, we’re still testing, a lot of new changes in Sierra which require updates to the OSX app. We will release updates ASAP to ensure full compatibility before release.

LKO

05.11.2016

Great work IVPN - very happy to see this!

Are there plans to release an iOS app? At this stage the OpenVPN works but it’s not reliable.

Dennis Kügler

07.11.2016

Yes, we’re actively developing an iOS client and hoping to release v1 before the end of the year.

Liam

07.11.2016

Amazing! Thank you for your response. Keep up the great work - you’ve also kept me as a customer now.

Nick

02.01.2017

Is this fully open-source? If not, it hardly matters what features you put in, as it’ll be untrustworthy at a fundamental level. The client does look sleek though - but where’s the Linux version? Must say its strange to completely ignore Linux, but attempt to push out iOS versions. Also, what’s the point of your “multi-hops” - which enemies are you trying to avoid? It seems like its just marketing, because the hops are done by the same company. So if someone was wiretapping IVPN, your multi-hops wouldnt do a thing to stop them, unless the traffic is tunnelled again, to hide the contents of it.

LKO

09.01.2017

Any updates on the iOS client?
IVPN News

Independent security audit concluded

By Nick Pestell

IVPN News

IVPN applications are now open source

By Viktor Vecsei

Releases

Beta IVPN Linux app released

By Viktor Vecsei

Releases

Key rotation issue fix in IVPN iOS app – update required

Posted on February 18, 2025 by Viktor Vecsei

In summary: We identified a potential DNS leak issue affecting our iOS app in brief intervals during WireGuard key regeneration. Details of the issue When IVPN iOS app rotates WireGuard keys while VPN is connected, the app calls the asynchronous method setTunnelNetworkSettings to update VPN tunnel with new configuration.
Introducing device management for better control of logged in devices Releases

Introducing device management for better control of logged in devices

Posted on February 13, 2024 by Viktor Vecsei

We are introducing IVPN device management, an opt-in (disabled by default) feature that helps you review and log out from devices currently logged in to IVPN apps. This step is a direct response to frequent customer requests for better device controls.
Spotted a mistake or have an idea on how to improve this page?
Suggest an edit on GitHub.