Package Details: airvpn-bin 2.13.6-1

Git Clone URL: (read-only)
Package Base: airvpn-bin
Description: AirVPN client "Eddie" based on OpenVPN, stable version.
Upstream URL:
Licenses: GPL3
Conflicts: airvpn, airvpn-beta-bin
Provides: airvpn
Submitter: uncle
Maintainer: uncle
Last Packager: uncle
Votes: 14
Popularity: 0.160186
First Submitted: 2015-08-13 02:15
Last Updated: 2017-10-05 16:57

Latest Comments

dreivier commented on 2018-04-23 06:44

gksu is gone (gksu-git is still available in aur though) and also doesn't work with wayland.

uncle commented on 2018-04-08 20:58

@caevaroy, I agree, however this is a matter for the developers. Personally, I have been using a downgraded iptables.

@MCATIS, the developers are already working on this feature in the latest beta, however it does not appear to be functioning yet, at least not on Arch.

MCATIS commented on 2018-03-26 19:55

Works great, thank you. Out of curiosity, is there any way for this to work as a panel applet? Just to avoid cluttering up my panel with another open application.

caevaroy commented on 2018-03-23 04:09

Would be great to get a patch for this critical issue.

uncle commented on 2017-03-20 03:16

No worries @cb474, flagging a package as out-of-date is actually helpful to me. The notification system for the AUR does not seem to work very well, so when someone leaves a comment, I rarely get a notification of it. Because of this, I will often just take a look at the list of packages I maintain, and if one of them has been marked out-of-date, it's name will be red, so I can tell it is out of date just by glancing at the list of packages.

cb474 commented on 2017-03-19 02:07

Thanks for the update uncle. I really appreciate your providing this package. I saw that you do tend to update it (and the beta version) in a very timely fashion. I appreciate that. I only marked it out of date to help notify you that it had changed. Hope you didn't feel like I was prodding you to update it sooner than you had time for. I know you (and others) maintain AUR packages as a contribution to the community and can only get to these things in your spare time. Again, thanks for packaging this.

uncle commented on 2017-03-17 19:41

Stable package has been upgraded to 2.12.4. @ofzad the beta package was updated to 2.12.4 when 2.12.4 was in beta. Now that 2.12.4 is stable, the stable package has been upgraded to 2.12.4. @cb474 is correct, 2.12.4 was only updated to stable as of recently. When I saw that it had been updated and had the opportunity to use my computer, I updated the AUR package. AUR packages do not always get updated immediately. Most are maintained in the author's free time, which means sometimes real life events take precedent. Sometimes changes in the program require rewriting of the AUR package which can take some time, also. This being said, I always make an effort to update my packages in as timely a fashion as I can, especially ones like airvpn packages, which people rely on for security.

cb474 commented on 2017-03-16 19:01

I think 2.12.4 was only considered stable as of today, looking at the "other versions" link on the AirVPN website.

It just hasn't been updated yet. I'm marking this out of date.

ofzad commented on 2017-03-16 13:10

Sorry @uncle but should not this package be update to the new version 2.12.4 being this a stable and not a beta version?

Can I ask you why did you choose to update to version 2.12.4 the beta channel?

In fact as you can see here the 2.12.4 is considered the "stable" one


I'm just asking this because the update is marked as "strongly recommended" and may pass unnoticed if you rely on the "stable" package and do not have the beta version.

uncle commented on 2017-02-01 00:00

I have updated to 2.11.15 stable, but take note that, at least for me, Eddie will fail DNS checks, when I have the "Check AirVPN DNS" option selected. If I connect without performing a DNS check, then manually verify on ipleak,net my DNS address will correctly be the same as my IP address, and checking my /etc/resolv.conf file, it will correctly be "nameserver". Everything looks okay, but use at your own risk, and manually verify your DNS address.

EDIT: Others have reported this problem has been resolved for them, so it may just be some quirk specific to my system.

All comments