Staff

Hello! Of course. Not only OpenVPN-AirVPN code is clean, clearly commented and can be maintained efficiently (Donald Knuth is an ideal master of the AirVPN suite developer chief ) but we also submitted pull requests initially for the master branch, before we forked.. An OVPN3 project leader and some other person reminded us that pull requests could not be accepted if AirVPN did not disclose the real identity of its developers, and if AirVPN did not accept the re-licensing clause specified in the CLA.rst contract stating that OpenVPN Inc., and only OpenVPN Inc., can re-license our code under any other license, including "non open" licenses (Part, II, https://github.com/OpenVPN/openvpn3/blob/master/CLA.rst) Both conditions were and are not accepted by AirVPN, and we were forced to fork. Therefore, upstream must be performed by third-parties or by OpenVPN Inc. itself, but remember that we do not agree to the mentioned contract, especially in the part which states that code may be re-licensed by OpenVPN Inc. under any other license. Currently, the following modifications by AirVPN can be of particular interest for the main branch: the (N_)RECONNECT bug fix in Linux the data channel cipher selection bug fix the new implementation of Data Channel cipher negotiation compatible with OpenVPN 2.5 new method as well as the older OpenVPN 2 implementation the "ncp-disable" directive implementation (it comes handy with older than OpenVPN 2.5 servers) the "data-ciphers" directive implementation the fix of the "explosion" bug triggered under apparently random circumstances, in reality due to the unbelievable lack of data structure initialization in at least five different parts of the code the cleaner rewrite of the options parser getting rid of a good amount of parsing bugs the new method to select the correct cipher for each packet with pointer to methods in place of a dumb, and slower, series of "if" in the main branch which are executed at every and each outgoing or incoming packet block (useful when it's linked against mbedTLS) many other bug fixes which would make this message too long for this thread - being 103 commits ahead, you really have a more stable, more OpenVPN 2 compatible, and faster library now Kind regards

Hello! Acknowledged. The documentation is not only online, it's included in the package too so you can consult it anytime, even if you're offline. Kind regards

@air2157 Hello! We think you're right. If confirmed, it does not seem as an Hummingbird limitation at all: we must check twice but at a first glance we have dragged such a limitation from the main branch of OpenVPN 3 library, specifically here: https://github.com/OpenVPN/openvpn3/blob/master/openvpn/options/merge.hpp when OpenVPN3 wants to merge additional profile (about which, we will have some questions for you after some tests, stay tuned ). We have already widely rewritten critical OpenVPN 3 parts in our fork, fixed dozens of bugs and conceptually wrong code, added new key features and essential directives, and we will rewrite even this part if it comes out that it's a counter-productive implementation by the main branch developers that we missed. Again, we will not hesitate to rewrite other code whenever the main branch code is inappropriate, after we have consulted with the development leader, as we have always done. Thank you for having found out the issue and reported it to us. @OpenSourcerer In this case the documentation is correct, as Hummingbird does not enforce limitation on the file name. Work on Hummingbird documentation has received excellent feedback (dozens of positive comments), readers please check here: https://airvpn.org/suite/readme/ https://airvpn.org/hummingbird/readme/ However, and obviously, anything can be improved. Is there anybody else here who can give us an additional feedback about Hummingbird & Suite documentation? OpenVPN3 main branch is undocumented while its source code is poorly commented, so it may have happened that a peculiar feature, especially when it is as "strange" as it seems in this case, has been missed. Luckily, nothing that justifies the "sloppy" adjective, in our opinion. Remember that we offer a README.md specific to HB which is much more complete than a man page (you can't of course stuff the whole readme.md in the man pages). man pages had been planned for the AirVPN Suite and not for Hummingbird, since Hummingbird had been considered a binary which can be launched by Eddie, while as a stand alone binary it was just transitional software to show what our AirVPN OpenVPN 3 library could do, before we had a real daemon, Bluetit, whose version 1.1.0 release has now the priority. Of course now that Hummingbird appears to have reached such a wide appreciation and success (which we did not expect) we may change our plans, in order to maintain Hummingbird not only as an Eddie alternative to OpenVPN (Hummingbird in Intel Mac and in M1 Mac provides a 2x throughput boost against OpenVPN 2.5), but also as a part of the Suite. Next step is publishing the developer's manual for Bluetit, our first and only real daemon, which we deem as very important. Then we can consider man pages specific to the Suite and in that occasion we can re-think about Hummingbird man pages, because at the of the day we offer a much more complete documentation than a man page. We totally agree with you. If the restriction is confirmed OpenVPN3 main branch developers might be asked about why they think it is appropriate to enforce it, anyway we have seen worse things in the original source code. On our side, we will verify the problem and we will remove it if confirmed, luckily we forked OpenVPN 3 a long ago so we have no constraints. Our fork is now 103 commits ahead the main branch, and we assure you that we are determined to wipe out any other OpenVPN3 main branch "absurdity", according to your definition, we find. Kind regards

@lostagain Hello! Trivially because when your system is in the virtual network, it is also in the real network provided by your ISP. You will not receive unsolicited packets from the VPN if you don't forward ports remotely, but you can still receive them from your ISP network. Network Lock will block those incoming packets but that will not prevent a DDoS of course . A better solution is that you do not forward packets from your router to your systems when your systems are in the VPN. Also remember that if you forward remotely ports, you will be protected by the global anti-DDoS system on the server datacenter, and you will not have specific traffic inspection for your forwarded packets to filter them against attacks. We do not inspect our customer packets by policy and our network remains agnostic. Kind regards

@Stalinium Hello! We have categorized the guides in two places, answers to FAQ and How-To section (which is not a community forum, so new topics can be opened only by Staff). We have also added (very recently) a new search engine which does not search the whole forum but only our guides. That said, as usual everything can be made better in an endless loop of improvements. :) About users jumping in without testing, the best we can do is offering a robust leaks prevention (Network Lock) based on firewall rules. That should protect thoroughly even the most reckless user. :) Kind regards

@OpenSourcerer @WinniethePooh Hello! Yes, that 50.x.y.z is an address of one of our micro-routing servers. Certainly Binance must have been "micro-routed" for some anti-blocking purpose after customers' requests. This information should clarify and resolve the "enigma". Kind regards

@HopeandGory We removed your linked web site page because it contains dangerous information (they suggest to connect a torrent software to a socks proxy in order to get an anonymity layer) and advertisements to shady VPN services, at least one of them notorious for personal data breach and personal data harvesting, so they web site owners might not be in good faith. However they link to ipleak.net to verify your leaks (a free service powered by AirVPN ), how strange. Our own guides on how to optimize torrent and eMule software and how to prevent any kind of traffic leak outside the VPN connection with our software contain more information, both in quantity and relevance. And those guides exist since 11 years ago or so. Furthermore, the guides have been included in the FAQ linked in the web site top menu, in the "How-To" forum, in the welcome e-mail, in the thorough and accurate AirVPN guide by LZ1, and in dozens of threads in the community forum. Note that LZ1 as well as OpenSourcerer are community members, they do not work for AirVPN and they do all they do merely for passion and altruism. Think of all of the above, read the documentation, and we are confident that you will deeply re-evaluate AirVPN community. Kind regards

@pjnsmb Hello! gb3.ipv6.vpn.airdns.org is updated correctly, so Bluetit will connect to the correct server that domain resolves into. The failure to resolve names during Bluetit start at bootstrap but the ability to do so afterwards remains a problem which we could not reproduce so far. It was detected in Raspbian and OSMC, due to their settings which cause systemd to run Bluetit prematurely, and fixed by implementing in Bluetit its own network link detection. Kind regards

@pjnsmb Hello! It has been sorted out, please try again now (for the readers: anyway not a Bluetit issue). Kind regards

@colorman Hello! Another piece of info please. When you run Hummingbird (and it "explodes"), do you have Bluetit daemon running as well? Kind regards

@colorman Good! Now network lock works with Goldcrest/Bluetit, when you force nftables. Momentarily, do not forget to force it, otherwise network lock will fail. We will be investigating on this bad issue. Correction: it does not work with nftables as well. About Hummingbird, thank you: we see that Hummingbird crashes when it is invoked in that way, as Eddie does, so we have now a track to understand what happens. We'll investigate on it as well, of course. Kind regards

@colorman Typo (now fixed, please fix it yourself too). Enter: sudo hummingbird --network-lock off --ignore-dns-push foo.ovpn Remember to specify the full path to the *.ovpn file if necessary. Kind regards

@colorman That's expected, Goldcrest parser expects the configuration file at the end of the whole command, so it assumes that "nftables" is the configuration file. Retry with: ./goldcrest --network-lock nftables AirVPN_Netherlands_UDP-443-Entry3.ovpn Remember to specify the full path to *.ovpn file if necessary. Kind regards

Hello! Please generate a configuration file form the Configuration Generator (in your account "Client Area", in our web site) with the same protocol, port, destination server that cause the problem with Eddie+Hummingbird. Then run Hummingbird as Eddie does: sudo hummingbird --network-lock off --ignore-dns-push foo.ovpn where foo.ovpn must be replaced by the full path and name of the ovpn configuration file you previously generated. The options to disable network lock and reject DNS push are included to run Hummingbird in the same way Eddie does. In this way we should be able to see what happens to Hummingbird and maybe have some clue. Kind regards

@colorman Hello! Can you please also test Bluetit with nftables (which should be the default filtering platform in your openSUSE version)? First, you need to install nft (it's a binary utility run by Bluetit as a frontend to nf_tables packet filter), if it's not already available in your system. Then, just run Goldcrest as you usually do, but with the following, additional option: --network-lock nftables Check whether you still get an error, in Bluetit and Goldcrest logs, about network lock or not. Kind regards