Jump to content
Not connected, Your IP: 18.217.237.169

Staff

Staff
  • Content Count

    11043
  • Joined

    ...
  • Last visited

    ...
  • Days Won

    1866

Everything posted by Staff

  1. Hello! It's an "abandoned" system. Mainstream support ended on 2012 while extended support ended on April 11, 2017. Using it is therefore risky as any new discovered vulnerability is never patched. Kind regards
  2. @sebi Hello! You need to uncheck "Use Hummingbird if available" in the "Preferences" > "Advanced" window. Eddie will then look for OpenVPN in your command path (OpenVPN must be installed in your Linux box). If you have some OpenVPN binary you want to use outside the path, then you need to tell Eddie where to find that OpenVPN binary. Note that Eddie will run with root privileges only binaries owned by root. Beta versions exist exactly because unexpected problems may (and usually will) come out. Eddie stable releases are always packaged with a tested Hummingbird version. About the Suite, we are almost ready to launch a version linked against our openvpn-airvpn fork fixing the new bugs and regressions unfortunately inherited from the main branch which we did not find with our tests (our fault, hands down). If you want to use Eddie with a working version of Hummingbird you can rely on Eddie 2.21.8, which is the latest stable release and is packaged with Hummingbird 1.2.0. This is an excellent question, and currently Eddie can not renounce to those directives for a complex reason. In a few words, with the risk of oversimplifying, it's because of how our servers are configured in order to maintain backward compatibility with OpenVPN 2.3 and 2.4. Sooner or later we will break compatibility at least with OpenVPN 2.3. From that moment on, Eddie can be re-designed with more freedom in mind and some behavior which may appear "strange" when compared with ordinary OpenVPN configuration files (as it is in this case, with the directives you mention) can be simplified or canceled. Also note that some other behavior is dictated by the fact (and this is perfectly logic as well) that Eddie adds some important features on top of OpenVPN features (routes inside and outside the tunnel, DNS management, Network Lock...). Thank you, this sounds like a bug and it's great that bugs are found during beta testing (or anyway before a stable version is out). We will forward your message to Eddie's developer. Furthermore, please feel free to report this on GitHub and on Eddie's thread in "News", if you wish so. Kind regards
  3. Hello and thank you very much for your great feedback! Do you experience the instability with WireGuard, OpenVPN or both? If you haven't tested both, could you please do it and report whether you have the same problem or not? You can switch between them simply by tapping the VPN type icon on the main and other views. Also, we suggest that you send us a report (in a ticket, for privacy reasons) generated by Eddie while the problem is ongoing or has just occurred. In the "Log" view you can tap the paper plane icon and send the whole report to one of our web sites. Eddie will tell you back the link to it, which you should then send to us. You can anytime delete the report and anyway it will be automatically deleted in 30 days. Kind regards
  4. Hello and thank you very much! We confirm the "swift and painless compilation". The main problem we experienced is the following one: https://github.com/OpenVPN/ovpn-dco/issues/14 Unfortunately we don't have much to add on what Schwabe already wrote. We can say that we had the issue only on a single VM (an AWS EC2 used momentarily for this purpose) during our very early testings (Debian 11, 5.10 kernel, OpenVPN 2.6/OpenSSL/DCO etc. in house built). Now that we are testing only on dedicated servers (minimal Debian 11 installation, Xeon E3 or Xeon E5 architectures on HP and Dell servers) we can not not manage to reproduce the issue anymore. Should we get some additional piece of info/dump/how to reproduce/etc. we will definitely inform you. The crashes that we had on the VM had an apparently random pattern, so we can't even say what to do to maximize the reproducibility likelihood, we're sorry. In our configuration some OpenVPN processes are working in UDP, other ones in TCP, both tls-auth and tls-crypt, in all combinations. OpenVPN on the VM was 2.6.0, we see now that you strongly recommend 2.6.2 and of course we will update. LAST MIN. ADDITION: However, we now read a brand new comment on GitHub about the issue: Maybe we already built DCO including the TCP rework (on our dedicated server)? Can you tell when the rework and simplification have been committed? Kind regards
  5. @OpenSourcerer Just in case this is a valuable information for you, ProMind tested and could build OpenVPN+DCO on kernel 6.2.7 (in a Fedora 37 system) without any problem, through the provided Makefile and no modifications at all. Swift procedure, not even a single warning was thrown. Kind regards
  6. @oassQ9w4cbl4AySZhhth%p36x We will keep you posted. Unfortunately, it's possible that in an initial stage DCO will be only on experimental servers, so yes, persons available to testing will be invaluable, thanks! Check here for a quick update: https://airvpn.org/forums/topic/56119-new-10-gbits-server-available-bg/ Kind regards
  7. 5.16. Correction, 5.10 We never tried to do it on 6, and we're sorry (and concerned) to hear that. Thank you for the information. Kind regards
  8. Hello! From GitHub and yes, we have actually experienced various problems we wrote about a week ago or so, that's why you see this relevant delay in deploying DCO. Maybe DCO will have hard time to get its way into kernel.org, as we read of a lot of serious problems unresolved since months, but we'll see. We will keep you informed and we ensure you that we will not trigger a potential bomb in our kernels. If we reach an apparent stable environment, we will anyway deploy DCO very gradually. Kind regards
  9. Hello! We're very glad to inform you that a new 10 Gbit/s (full duplex) server located in Sofia (Bulgaria) is available: Wazn. With Wazn, AirVPN infrastructure can now offer 10 Gbit/s full duplex lines and servers in strategic locations all over Europe: Switzerland, the Netherlands, Sweden and Bulgaria, all of them with direct peering with a wide variety of providers and at least two tier2 transit providers. As WireGuard diffusion increases, such servers will be able to use more and more bandwidth, while the imminent OpenVPN DCO deployment on selected AirVPN servers will also provide for more scalability and performance. According to our tests (*) from Italy, the Netherlands, the United States and Germany (from both residential and business lines) and our statistics, in the countries with a presence AirVPN remains the fastest VPN for consumers in the world, both for available bandwidth and round trip times. We are confident that the progressive increase of CPU power and available bandwidth, together with our usual commitment against overselling, will further widen the gap. (*) Tests performed from tier1 providers such as Telecom Italia Sparkle or "near-tier1" ones such as Cogent and Hurricane. Tests performed against a wide variety of well known VPN services, including the most advertised ones. The AirVPN client will show automatically the new server; if you use any other OpenVPN or WireGuard client you can generate all the files to access it through our configuration/certificates/key generator (menu "Client Area"->"Config generator"). The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP for OpenVPN and ports 1637 and 47107 UDP for WireGuard. Wazn supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, OpenVPN tls-crypt and WireGuard. Full IPv6 support is included as well. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses and 4096 bit DH key not shared with any other VPN server. You can check the status as usual in our real time servers monitor: https://airvpn.org/servers/Wazn Do not hesitate to contact us for any information or issue. Kind regards and datalove
  10. @bidasci Use a proper language and don't be aggressive. You might use that language with your family, if they allow you to do so, but surely not with us and our community so get a grip of yourself right now. Open a ticket and the support team will assist you. Check the real time servers monitor to get convinced that the problem may very well be on your side. Acknowledging this simple fact is the first step to work to resolve your own problem with our assistance. Last but not least, advertising other VPNs in this way is severely forbidden, so the ad has been removed. Do not post other ads or you will be banned from the forum. Kind regards
  11. @nocturnaltabernacle Hello! It might be an MTU size issue. By default, on Linux and FreeBSD, WireGuard might set a 1420 bytes MTU size, which is too big for some networks. Shrink it to 1320 or even 1280 bytes (the minimum accepted value) and test again. In order to change wg interface MTU size on your BSD system, please edit the wg configuration file with any text editor and add the line: MTU = 1320 in the [Interface] section. Kind regards
  12. @BatteriVoltas Hello! Please feel free to open a ticket to get thorough support. In the ticket please state whether you get error 110 or 111 when you test from AirVPN web site port tester. As a preliminary check, please make sure that Deluge settings related to UPnP and NAT-PMP are all disabled and that no firewall (running in the same machine where Deluge runs too) interferes with packets to and from Deluge. A quick reference guide to check other settings: https://airvpn.org/faq/p2p/ Kind regards
  13. Hello! Because it's not mandatory. You can open a ticket from an account which does not have any e-mail address. Kind regards
  14. Hello! All the tickets (by customers) are normally answered in 2-8 hours during business days. During Sunday and other special days (Christmas, New Year's Day...) tickets are answered in 12 hours on average, and in 24 hours in the worst case.. Support service is not outsourced therefore we have total control over the support system and best expertise is guaranteed. Account DARR1 never opened a ticket. Furthermore, the e-mail address linked to DARR1 never sent any e-mail to "support@airvpn.org". Please feel free to open a ticket at your earliest convenience. Alternatively, write to support via e-mail (from the e-mail address linked to the account). Kind regards
  15. Hello! We're very glad to inform you that a new 10 Gbit/s server located in Alblasserdam (the Netherlands) is available: Dalim. The AirVPN client will show automatically the new server; if you use any other OpenVPN or WireGuard client you can generate all the files to access it through our configuration/certificates/key generator (menu "Client Area"->"Config generator"). The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP for OpenVPN and ports 1637 and 47107 UDP for WireGuard. Dalim supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, OpenVPN tls-crypt and WireGuard. Full IPv6 support is included as well. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses and 4096 bit DH key not shared with any other VPN server. You can check the status as usual in our real time servers monitor: https://airvpn.org/servers/Dalim Do not hesitate to contact us for any information or issue. Kind regards and datalove
  16. Hello! You have many options since we support Raspberry Pi machines thoroughly. 1. You can rely on the AirVPN Suite, which is available for 32 and 64 bit ARM processors. A legacy version is available as well: https://airvpn.org/linux/suite/ Pick a version according to the system you're running (32 or 64 bit OS) and if in doubt do not hesitate to specify your exact system and contact us. Examples: if you have the new Raspberry Pi OS 64 bit, download the 64 bit version. If you run some Raspbian 32 bit OS (deprecated) pick the 32 bit legacy version. The AirVPN Suite provides you with a stand alone binary, or a daemon and a client: just pick the solution that you like most as all the components are lightweight. User manual available here: https://airvpn.org/suite/readme/ 2. If you have the option to install Mono package and you can afford some bigger RAM footprint, you can consider Eddie ARM edition, which offers a fully featured GUI that the Suite does not provide for: https://airvpn.org/linux/eddie/ Also consider that Eddie integrates WireGuard, while the Suite currently doesn't (a new version supporting WireGuard is imminent, stay tuned). 3. Last alternative option is simply running a native WireGuard or OpenVPN client. In such cases, just follow the instructions for Linux related to the "native" clients. Our Configuration Generator will generate all the files those clients need, according to your preferences. Kind regards
  17. @FlyawayRavage Hello! The --air-server option requires an argument which is the exact server name, all is unknown with --air-info. The --air-key-list is stand-alone, you must not add --air-info. The --air-info --air-country combination also accepts continent names, and the special keyword earth. In your case, when Bluetit is connected to some VPN server, it ignores all of those commands and simply tells you the status. This behavior might be changed in the next version, as it might be confusing. What you probably want is (while Bluetit is disconnected from the VPN): goldcrest --air-list --air-country all Kind regards
  18. Hello! We have experienced a serious kernel panic problem apparently reported here: https://github.com/OpenVPN/ovpn-dco/issues The reported kernel crashes which we also experienced are fearsome, because when they occur all users (even WireGuard ones of course) are disconnected, machine control is lost, and a reboot via IPMI or hard power cycle is required. Before allowing something to run as a kernel part on a production server for all of you, that something must behave more properly. We will keep testing and searching for a stable setup, and of course we also hope in imminent bug fixes. We will keep you informed. Of course rolling out OpenVPN 2.6 without DCO is an option, but we would prefer to migrate directly to OpenVPN with DCO, instead of having to do it in two different steps. Kind regards
  19. Hello! We're very glad to announce a special promotion on our long term Premium plans for the end of Summer or Winter, according to the hemisphere you live in. You can get prices as low as 2.06 €/month with a three years plan, which is a 70% discount when compared to monthly plan price of 7 €. If you're already our customer and you wish to stay aboard for a longer period, any additional subscription will be added on top of already existing subscriptions and you will not lose any day. Please check plans special prices on https://airvpn.org and https://airvpn.org/buy All reported discounts are computed against the 7 EUR/month plan. Kind regards & datalove AirVPN Staff
  20. @litef00t Hello! Please upgrade (if you haven't already done so) to Eddie Android edition 3.0, where the autostart at boot procedure has been greatly enhanced to increase compatibility both with old Android versions (5.1) and the latest 12 and 13. If necessary please see here: https://airvpn.org/android/eddie/apk/tv/ Kind regards
  21. @ddrahos Hello! For clarity's sake we now replace "device" word with client "certificate". You do have different client certificates but you have all the sixteen ports linked to a single certificate named "Server", so all of your *.airdns.org names will always resolve into the exit-IP address of the last VPN server the devices using the "Servers" certificate connect to. If you wish that a different name resolves into a different IP address, let the 2nd device use a different certificate, and link to that certificate the set of ports that the 2nd device needs. This gives you the freedom to have different names, each one resolving correctly to the proper exit-IP address of the VPN server you want, at the small price of dividing ports for each device. Feel free to elaborate about which other questions the new system raises, we'll try to answer if possible. Kind regards
  22. Hello! Please click "Contact us" button on the top right corner of the web pages, or write an e-mail to support@airvpn.org Kind regards
  23. Hello! It's already implemented, and even in a more flexible way. Since a few months ago linking a name to a specific port is no more pro-forma only, provided that you have multiple "devices" and you configure different ports to link to different "devices". You can link the port to a specific "device", and a specific DDNS to one or multiple ports. In this way you have an even more flexible and comfortable system. For each device, each name of yours will resolve into the exit-IP address of the last VPN server to which you connect through that specific "device". In the port panel just select the "device" you want for that port, provided that the port is enabled. You can do so in the combo box just under the enable/disable toggle. If you use the same "device" on multiple devices which connect at the same time, and/or you have your remotely forwarded ports configured to "all devices", you will experience the behavior reported by @ddrahos , i.e. you will fall back to the a behavior which allows full backward compatibility with the previous system. Kind regards
  24. @zsam288 Hello! Yes, but on most residential lines you must switch to OpenVPN and also force TCP; WireGuard is blocked on every line (as far as we know), while UDP is sometimes blocked, sometimes heavily shaped. Our Eddie Android app recognizes problems and switches modes in an attempt to bypass blocks, but only when it works with OpenVPN (WireGuard has only one possible working mode...) so you need to manually switch to OpenVPN. Also, you may save time by directly forcing TCP and port 443, otherwise the app might not find the correct connection mode. For example, if UDP is heavily shaped but not blocked, the app will never switch to TCP by itself, because an UDP connection is finalized successfully. [In Eddie Desktop edition you can change connection mode in the "Preferences" > "Protocols" window.] Have a nice journey and a nice stay! Kind regards P.S. To stay on the safe side, and since Tor might be blocked on some lines, bring with you a small list of Tor obfuscated bridges IP addresses that you can configure in Tor Browser + Orbot (Android apps) in case of emergency.
  25. Hello! Please check whether the problem is related to https://www.macwheeler.com/windows-10-office-365-cannot-connect-over-openvpn-fixed - the workaround is easy. You may also test a WireGuard connection to potentially discern whether it's an OpenVPN-specific problem, as described in the above linked article, or not. If you run Eddie, the Air software client, you can switch to WireGuard in the "Preferences" > "Protocols" window. Kind regards
×
×
  • Create New...