Staff

Hello! Update: Hummingbird 1.2.0 is now available. Original message download links and changelog have been updated accordingly. Special thanks to all the testers whose help and patience have been instrumental in spotting bugs and reaching a stable release. Thank you so much! Kind regards

Hello! Update: AirVPN Suite 1.2.0 is now available. Original message download links and changelog have been updated accordingly. Special thanks to all the testers whose help and patience have been instrumental in spotting bugs and reaching a stable release. Thank you so much! Kind regards

Hello! AirVPN Suite is only for Linux and Debian is the system the whole suite is built on (compiled and linked) for x86-64 architecture. The Suite is based on OpenVPN 3 AirVPN which, obviously, is fully compatible with OpenVPN 2 based servers. OpenVPN 3 AirVPN is 132 commits ahead of OpenVPN:master and resolves a myriad of bugs and malfunctions caused by OpenVPN 3 main branch. WireGuard support is planned as well. Please, once again, read the provided document we linked in our previous post for your comfort. Kind regards

Hello! Update: Hummingbird 1.2.0 Release Candidate 3 is now available. Links to download the packages have been updated in this thread first message. Thank you very much for your tests! Kind regards

Hello! Update: AirVPN Suite 1.2.0 Release Candidate 3 is now available. Original message download links and changelog have been updated accordingly. Thank you for your tests! Kind regards

Hello! Please consider the AirVPN Suite, it should resolve the issue. https://airvpn.org/suite/readme/ Kind regards

Hello! Obviously Eddie is maintained as you have noticed by yourself. Beta testing is typically ended when all found bugs in the beta versions have been fixed and the customer satisfaction is high. A typical public beta testing cycle of Eddie Desktop edition, when brand new features are included (in this case WIreGuard, new drivers, deep rewrite of strategic pieces of code) may take 9-12 months. This is not an unreasonable time because testing involves about 18 Linux distribution in various different versions, with three different DE and two architectures, 3 different OS X systems, 6 different macOS systems, 5 different Windows versions in two different architectures, various ARM based systems in two different architectures, for a total amount of several hundreds systems where Eddie must run properly in. Considering the current testers feedback you can reasonably expect a stable release at the end of March 2022. Please feel free to report what your concern is exactly, and why you are not satisfied with Eddie 2.21.5 (beta). If you're already satisfied with it, just use it. Kind regards

Now, AirVPN .onion website is served under SSL/TLS. Some reason here: https://community.torproject.org/onion-services/advanced/https/ (we're writing this post from .onion under SSL)

@NoMercy1290 Hello! Correct, since the list "exploded" to more than a million entries yesterday (from a few hundred thousands) a security system disabled it. Today it has shrunk again to 300'000 entries. The list is now available. Kind regards

@TooLittleTime Hello! Yes, please consult the user's manual (the .rc file templates will also show a lot) and test whether the problem you mention is resolved in the current RC. As far as we know lists have always worked correctly, a bug was that even the password argument was treated as a list when a comma was there. Kind regards

@Maggie144 Hello! Thank you, bug reproduced and confirmed. It will be fixed soon. Kind regards

@colorman Hello! Thank you, bug reproduced and confirmed, and it is indeed a regression from RC 1 as you wrote. We are investigating but we have already a precise idea of the problem, so expect a fix soon. In the meantime, to use RC 2 and keep testing you must enter in the profile the deprecated 'cipher' directive, for example: cipher CHACHA20-POLY1305 or cipher AES-256-GCM Alternatively, you may avoid ovpn profiles. As a further alternative, include "--cipher <cipher>" in Goldcrest command line options. Kind regards

Correct, we compile this version without statically linking some libraries, for better stability. Yes, sorry but tray icon will be reimplemented as soon as possible.

@colorman Hello! We can't see AirVPN_Netherlands_UDP-443.ovpn, can you please check and re-send? Anyway from the log we see that the cipher forced on Bluetit is BF-CBC, which is not supported. Kind regards

@colorman Hello! Thank you, please disclose /home/gerrit/.config/goldcrest.rc and AirVPN_Netherlands_UDP-443.ovpn (cut sensitive information, if any). Kind regards

Version 2.21.5 (Tue, 08 Mar 2022 11:30:14 +0000) [bugfix] [linux] Segmentation-fault of Elevation in some Arch distro [change] [linux] Tray icon (temporarily) removed from Arch/AUR build [bugfix] [macos] Fix for issue "Client not allowed: Remote executable not signed" [bugfix] [linux] Issue with custom IP in NetLock>Allowlist (nftables only) [bugfix] [linux] Better selection of iptables vs iptables-legacy vs iptables-nft [bugfix] [linux] Useless ping result reported in std::cout

Hello! Update: AirVPN Suite 1.2.0 Release Candidate 2 is now available. Original message download links and changelog have been updated accordingly. Thank you for your tests! Kind regards

Hello! Update: Hummingbird 1.2.0 Release Candidate 2 is now available. Links to download the packages have been updated in this thread first message. Thank you very much for your tests! Kind regards

@Gucci4Gucci Hello! False. Issue a whois before posting and mention your source ("reported as..." by whom? link?). CANES: $ whois 86.105.9.67 % IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: whois.ripe.net inetnum: 86.0.0.0 - 86.255.255.255 organisation: RIPE NCC status: ALLOCATED whois: whois.ripe.net changed: 2004-04 source: IANA # whois.ripe.net inetnum: 86.105.9.0 - 86.105.9.127 netname: M247-Europe-SRL descr: Bucharest Infrastructure org: ORG-MES6-RIPE remarks: Geofeed found at https://geoip.m247.ro/geofeeds.csv geoloc: 44.4753217 26.1039617 country: RO admin-c: GBXS-RIPE tech-c: GBXS-RIPE status: ASSIGNED PA remarks: ---- LEGAL CONCERNS ---- remarks: For any legal requests, please send an email to remarks: ro-legal@m247.ro for a maximum 48hours response. remarks: ---- LEGAL CONCERNS---- mnt-by: GLOBALAXS-MNT created: 2016-10-04T13:14:03Z last-modified: 2022-01-18T11:17:23Z source: RIPE organisation: ORG-MES6-RIPE org-name: M247 Europe SRL country: RO org-type: LIR address: 11B Sos. Fabrica de Glucoza, 1st floor District 2 address: 020331 address: Bucharest address: ROMANIA phone: +4 031 080 0700 abuse-c: ME5262-RIPE mnt-ref: RIPE-NCC-HM-MNT mnt-ref: M247-EU-MNT mnt-by: RIPE-NCC-HM-MNT mnt-by: M247-EU-MNT created: 2014-01-06T11:23:03Z last-modified: 2021-08-18T08:33:50Z source: RIPE # Filtered role: GLOBALAXS NOC remarks: M247 - Network Management Centre address: 1 Ball Green, Cobra Court address: M32 0QT, Manchester - United Kingdom tech-c: JB3482-RIPE tech-c: CB2407-RIPE nic-hdl: GBXS-RIPE abuse-mailbox: abuse@m247.ro mnt-by: GLOBALAXS-MNT created: 2006-07-13T15:37:05Z last-modified: 2018-09-10T17:32:45Z source: RIPE # Filtered % Information related to '86.105.9.0/24AS9009' route: 86.105.9.0/24 descr: M247 Europe SRL origin: AS9009 mnt-by: GLOBALAXS-MNT created: 2015-08-11T11:57:24Z last-modified: 2015-08-11T11:57:24Z source: RIPE % This query was served by the RIPE Database Query Service version 1.102.2 (BLAARKOP) ALAMAK: $ whois 91.207.102.163 % IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: whois.ripe.net inetnum: 91.0.0.0 - 91.255.255.255 organisation: RIPE NCC status: ALLOCATED whois: whois.ripe.net changed: 2005-06 source: IANA # whois.ripe.net inetnum: 91.207.102.0 - 91.207.103.255 netname: M247-EUROPE-SRL country: RO org: ORG-MES6-RIPE admin-c: ME5262-RIPE tech-c: ME5262-RIPE status: ASSIGNED PI mnt-by: RIPE-NCC-END-MNT mnt-by: M247-EU-MNT mnt-routes: M247-EU-MNT mnt-domains: M247-EU-MNT remarks: ---- LEGAL CONCERNS ---- remarks: For any legal requests, please send an email to remarks: ro-legal@m247.ro for a maximum 48hours response. remarks: ---- LEGAL CONCERNS---- created: 2013-10-09T10:13:09Z last-modified: 2018-11-29T10:55:39Z source: RIPE # Filtered organisation: ORG-MES6-RIPE org-name: M247 Europe SRL country: RO org-type: LIR address: 11B Sos. Fabrica de Glucoza, 1st floor District 2 address: 020331 address: Bucharest address: ROMANIA phone: +4 031 080 0700 abuse-c: ME5262-RIPE mnt-ref: RIPE-NCC-HM-MNT mnt-ref: M247-EU-MNT mnt-by: RIPE-NCC-HM-MNT mnt-by: M247-EU-MNT created: 2014-01-06T11:23:03Z last-modified: 2021-08-18T08:33:50Z source: RIPE # Filtered role: M247 Europe address: Sos. Fabrica de Glucoza, Nr 11B address: etaj 1, Sector 2, Bucuresti Romania admin-c: PP13161-RIPE tech-c: MP26073-RIPE abuse-mailbox: abuse@m247.ro nic-hdl: ME5262-RIPE mnt-by: M247-EU-MNT created: 2014-01-13T12:11:34Z last-modified: 2014-12-08T16:22:40Z source: RIPE # Filtered % Information related to '91.207.102.0/23AS9009' route: 91.207.102.0/23 descr: M247 Europe SRL origin: AS9009 mnt-by: GLOBALAXS-MNT created: 2015-04-17T10:11:11Z last-modified: 2015-04-17T10:11:11Z source: RIPE % This query was served by the RIPE Database Query Service version 1.102.2 (WAGYU)

@OpenSourcerer Hello! We couldn't reproduce the issue in Arch, but our distribution uses DBus 1.14, while yours runs the 1.12.20 legacy. Do you have the option to upgrade to 1.12.22 or 1.14 and check whether the problem gets resolved or not? We start suspecting that the issue is related to 1.12.20. Kind regards

@OpenSourcerer Hello! Yes, that's fine, Bluetit implements an exclusive D-Bus mode to prevent multiple clients from connecting to it. That's puzzling, it may be caused by D-Bus lack of memory or wrong data type (EDIT: the error would be caused by lack of memory only according to D-Bus documentation) Furthermore Bluetit crashes immediately after.: We've been struggling and failing to reproduce the issue so far. Can you tell us your D-Bus version? Have you experienced the problem in Arch only or even in other distributions? Kind regards

Issue details Eddie checks the integrity of Eddie installation every time it is started. The following command: /usr/bin/codesign -v --verify /Applications/Eddie.app/Contents/MacOS/Eddie must return /Applications/Eddie.app/Contents/MacOS/Eddie: valid on disk /Applications/Eddie.app/Contents/MacOS/Eddie: satisfies its Designated Requirement but when a crash occurs it generates a dump file that causes failed validation: /Applications/Eddie.app/Contents/MacOS/Eddie: a sealed resource is missing or invalid file added: /Applications/Eddie.app/Contents/Resources/mono_crash.11b738480.0.json Removing dump files with the below command reverts to a successful validation: rm /Applications/Eddie.app/Contents/Resources/mono_crash*

If you encounter exactly this error under macOS: Unable to start (Client not allowed: Remote executable not signed) run from terminal (adjust the path if different) sudo rm /Applications/Eddie.app/Contents/Resources/mono_crash* This issue is resolved in Eddie version 2.21.5 and above.

@OpenSourcerer Hello! -6 option problem you have detected is caused by the fact that the option is managed by OpenVPN3 and not by the Suite. OpenVPN3 options can't have "on", "off" etc. arguments, but only "yes", "no" and "default"/other, while the Suite parser is much more flexible. We will translate the arguments of those options which are managed internally by OpenVPN3 in order to resolve the issue. In the meantime you should use only "yes" or "no" to resolve the problem and keep testing. Kind regards

Hello and thank you! OK, it sounds fine here. Yes, bug reproduced - it doesn't recognize any setting. If connection is attempted over IPv6, for example because default system choice is IPv6 or configuration file prescribes IPv6 address in remote directive, failure is expected when IPv6 is not available server side. That's fine. The problem in such systems is again the bug for which one can't turn off -6 (allowuaf), making those almost unable to connect to IPv4 only servers (a remote IPv4 address must be forced to circumvent the problem). The default setting for IPv6 should be the default system setting. Docs clarification/fix needed, we will check. Thank you very much! Kind regards