Linux: AirVPN Suite 2.0.0 preview available

[Staff 10114]

  On 2/15/2025 at 8:18 AM, colorman said:

./install.sh: line 385: setcap: command not found

Hello!

setcap sets file capabilities and requires libcap. Please install libcap and libcap-progs packages, uninstall and re-install the Suite, test again and report back at your convenience.

Kind regards
 

[colorman 27]

I missed package libcap-progs

But still error;

localhost:/usr/local/bin> ./goldcrest AirVPN_Belgium_UDP-1637-Entry3.conf
Goldcrest - AirVPN Bluetit Client 2.0.0 beta 4 - 14 February 2025

2025-02-15 11:49:25 Reading run control directives from file /home/gerrit/.config/goldcrest.rc
2025-02-15 11:49:25 Bluetit - AirVPN WireGuard/OpenVPN3 Service 2.0.0 beta 4 - 14 February 2025
2025-02-15 11:49:25 OpenVPN core 3.11 AirVPN (20250206) linux x86_64 64-bit
2025-02-15 11:49:25 Copyright (C) 2012- OpenVPN Inc. All rights reserved.
2025-02-15 11:49:25 OpenSSL 3.1.4 24 Oct 2023
2025-02-15 11:49:25 AirVPN WireGuard Client 2.0.0 Linux x86_64 64-bit
2025-02-15 11:49:25 Bluetit options successfully reset
2025-02-15 11:49:25 Requesting VPN connection to Bluetit
2025-02-15 11:49:25 Network filter and lock are using nftables
2025-02-15 11:49:25 Kernel module nf_tables is already loaded
2025-02-15 11:49:25 Network filter successfully initialized
2025-02-15 11:49:25 Private network is allowed to pass the network filter
2025-02-15 11:49:25 ERROR: Cannot start WireGuard connection. Client name and user name (system login name) not pro
vided.
2025-02-15 11:49:25 Bluetit session terminated

 

[Staff 10114]

  On 2/15/2025 at 10:51 AM, colorman said:

But still error; 

Hello!
 

  On 2/15/2025 at 10:51 AM, colorman said:

2025-02-15 11:49:25 ERROR: Cannot start WireGuard connection. Client name and user name (system login name) not provided.

We managed to reproduce the bug by trying to launch Goldcrest by both airvpn (or users in the airvpn group) and root. We will address the problem in the next beta version. In the meantime (so you can continue testing) please do not use a configuration file for WireGuard connections. Run Hummingbird directly when you want to establish a WireGuard connection through a configuration file and run Goldcrest for AirVPN integration.

Thank you for your tests!

Kind regards
 

[colorman 27]

  On 2/15/2025 at 11:42 AM, Staff said:

Hello!
 
We managed to reproduce the bug by trying to launch Goldcrest by both airvpn (or users in the airvpn group) and root. We will address the problem in the next beta version. In the meantime (so you can continue testing) please do not use a configuration file for WireGuard connections. Run Hummingbird directly when you want to establish a connection through a configuration file and run Goldcrest for AirVPN integration.

Thank you for your tests!

Kind regards
 

Thanks..
Use Eddie now

[jeffiscow 0]

Hey Y'all!

First I'd like to say this tool seems awesome that for the handwork and support.

I've been having a problem after I tried opening a port for p2p on the Airvpn site and binding it to my bittorrent client bluetit detected 2 dns and shutdown and locked and was getting the  "lock file --recover-network" message. I was able to fix that but now was getting a “D-Bus serviceorg.airvpn.server is not available” message. After trying everything I could find on the forums and the only thing that has fixed it was reinstalling, I figured I'd check if the Arch had a package in the AUR.

There are a few things I tried airvpn-suite-beta-bin 2.0.0-3 and this is what happened:
 

myusername@ArchLaptop % yain airvpn-suite-beta-bin                                                                                                                                                                  ~
AUR Explicit (1): airvpn-suite-beta-bin-2.0.0-3
:: (1/1) Downloaded PKGBUILD: airvpn-suite-beta-bin
  1 airvpn-suite-beta-bin                    (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> a
:: Deleting (1/1): /home/jeffiscow/.cache/yay/airvpn-suite-beta-bin
HEAD is now at b19ea8b pkgver++; arch=armv7h; license=GPL-3.0-only
  1 airvpn-suite-beta-bin                    (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> a

:: Proceed with install? [Y/n] y
==> Making package: airvpn-suite-beta-bin 2.0.0-3 (Sat 08 Mar 2025 11:18:48 AM EST)
==> Retrieving sources...
  -> Downloading AirVPN-Suite-x86_64-2.0.0-beta-1.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 3877k  100 3877k    0     0  3234k      0  0:00:01  0:00:01 --:--:-- 3236k
  -> Found airvpn-suite.sysusers
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha512sums...
    AirVPN-Suite-x86_64-2.0.0-beta-1.tar.gz ... Passed
    airvpn-suite.sysusers ... Passed
:: (1/1) Parsing SRCINFO: airvpn-suite-beta-bin
==> Making package: airvpn-suite-beta-bin 2.0.0-3 (Sat 08 Mar 2025 11:18:52 AM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found AirVPN-Suite-x86_64-2.0.0-beta-1.tar.gz
  -> Found airvpn-suite.sysusers
==> Validating source files with sha512sums...
    AirVPN-Suite-x86_64-2.0.0-beta-1.tar.gz ... Passed
    airvpn-suite.sysusers ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting AirVPN-Suite-x86_64-2.0.0-beta-1.tar.gz with bsdtar
==> Sources are ready.
==> Making package: airvpn-suite-beta-bin 2.0.0-3 (Sat 08 Mar 2025 11:18:56 AM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Entering fakeroot environment...
==> Starting package()...
install: invalid group 'airvpn'
==> ERROR: A failure occurred in package().
    Aborting...
 -> error making: airvpn-suite-beta-bin-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
airvpn-suite-beta-bin - exit status 4

Is this saying I need to create the “airvpn” group before I install the package, and if so, any idea what permissions and setting that group would need?

inxi print out for ya if that helps.

Thanks in advance!
 

inxi.txtFetching info...

[OpenSourcerer 1467]

I see my lapse in thinking there. In package(), the cuckoo binary is copied with airvpn as its group, but this group is only created in pacman's post-transaction hooks, after a package is installed. Since it's not able to create the package in the first place, airvpn-suite-beta-bin 2.0.0-3 is upgradeable (since the airvpn group would exist already) , but uninstallable from scratch.
I don't know that "yain" program you use (yay fork?), but if there is an option to edit the PKGBUILD before installing, comment out line 34, otherwise edit the PKGBUILD and build using makepkg:

34   # install -Dm4755 -g airvpn bin/cuckoo "$pkgdir/usr/bin/cuckoo"

makepkg -sCcri

After installing, set mode of cuckoo to 4755 and change group to airvpn:

# chmod 4755 /usr/bin/cuckoo
# chgrp airvpn /usr/bin/cuckoo

Be advised that the package is unmaintained. I abandoned maintainership of all Suite packages two months ago.

[jeffiscow 0]

@OpenSourcerer
I'm in the process of learning about Linux, security and how to best use of VPNs, so I apologize for not including everything I tried first before coming to the forum to ask for help. I didn't want to write a novel. My thought process on using the package from the AUR was It would save time and energy when installing and reinstalling. Also, “yain” is just an alias I set for “sudo yay -S”.

I didn't realize at the time the package was unmaintained, but know that I know I'll go back and try setting up Suite the suggested way. If I run into the "--recover-network" not working again I'll post the bluetit log and whatever is recommended and advised.

[colorman 27]

@Staff
Is there any development on the next Beta version?
It's very quiet.
Thanks in advance

[Staff 10114]

  On 3/29/2025 at 4:22 PM, colorman said:

@Staff
Is there any development on the next Beta version?
It's very quiet.
Thanks in advance

Hello!

Yes, there has been intensive work behind the scenes to fix some tricky bugs and improve the implementation of specific parts (special thanks to beta testers behind the scenes). The next beta version, or perhaps the first Release Candidate, is scheduled for the very first days of April.

Kind regards