Jump to content
Not connected, Your IP: 216.73.216.41

All Activity

This stream auto-updates     

  1. Past hour
  2. You could bring your own domain and point it to AirVPN in A record. It would work, but since the IP is shared, I don't think it's recommended. I don't think subdomains are discoverable, so using a subdomain would be safer for this. A better solution would be for you to host a separate VPN in your local network and expose it to Internet with AirVPN. This VPN can have it's own internal DNS and CA, or you can point A record (and TXT for DNS-01 challenge) of your domain to a private IP address
  3. Good to know, but it's outside our scope to force users to be rigorous. We offer the option and the proper tools to act rigorously and we try to educate through articles. We can't do much more. That was a very good suggestion but it still remains in a limbo, we will prioritize it when possible. Kind regards
  4. It's implemented since 2012 and currently defeats any AI or not AI attempt to disclose users' identity via traffic analysis. Only the global adversary is potentially able to do it, if it exists, but by definition the global adversary can not be defeated in any case, you can only make to it the content of your communications inaccessible, not your real origin and destinations of communications. Difficult to take offense by one who does not even know (or pretends he/she doesn't know) features implemented 13 years ago. Now locking the thread for a few days to avoid trolling anyway. Kind regards
  5. Today
  6. Definitely not AirVPN-related. It belogs to Telepark Passau. Is this your ISP by any chance? Does something similar happen with IPleak's torrent addess detection?
  7. It shows that there is a real adversary for port forwarding - one that could make users think twice before trusting the "no logging" claims, if a privacy mishap happens and article headlines scream danger. AirVPN team, you have not implemented multi-hop and traffic-analysis foiling - you are behind, slacking. You can take offense or actually pick up the pace - it's only a matter of time before AI exposes any VPN users' identity via traffic analysis, so I suggest AirVPN be ahead. I do like the transparent network, it's very helpful.
  8. @Staff Thank you for your response. To be absolutely clear: I am strongly against any illegal activities, including copyright infringement, and fully support AirVPN's ToS, which prohibit such use. I used a throwaway account here as a basic OPSEC practice, which aligns with privacy best practices and doesn't imply wrongdoing. On the technical points: Users' origin IPs are visible in real-time so long as they are actively connected. Indeed, users are explicitly warned of this in the Client Area. In a compelled disclosure scenario, this could reveal origin IPs corresponding to active connections without relying on logs. Your comment that "ports can be deleted/changed for account inactivity, pool shifts and other actions not involving the user" seems at odds with the following statement in the [UPDATE] Remote port forwarding system expansion announcement: "Each user can rely indefinitely, as long as the account has a valid plan, on the same ports and the same exit-IP address." Paying with non-KYC Monero mitigates transaction ID exposure, and more generally, following the "partition of trust" model you described here would obviate any of the aforementioned privacy issues. However, most users probably don't have such rigorous OPSEC. For the record, I do not support aspartame's proposal to add ephemeral ports. Instead, I hope that the implementation of the port forwarding management API you discussed here can be completed. My apologies if my scenario was misconstrued. I brought this up in what I hoped was the constructive spirit of the "General & Suggestions" forum. Kind regards.
  9. Hi, I have a strange problem. I have Qbittorrent behind AirVPN with port forwarding setup. Everything is working great on the most trackers. All trackers show me the correct IP address of the airvpn server I'm connected to with the correct port which is forwarded. Also the torrent client itself shows the expected airvpn adress. Only one tracker shows besides the correct ip also another ip a totally other IP Adress with the correct port. So, on this tracker all information is right but the additinal, wrong IP Adress. So, it's impossible to be connectable. The tracker shows 185.39.65.10 as my IP adress, which isn't right. So, two questions: 1. Is this an IP( 185.39.65.10) from any airvpn server ? How can I prevent the false unreachable IP from being created additionally after a couple of minutes. 2. If yes, how could it happen that this adress is shown in the tracker? The adress does not belong to the connected airvpn server on my opinion, nor to my server itself. My connected airvpn server is in switzerland. I read that there might be a rerouting problem. I have already set the "anti-geolocation system" (under "Settings") to "Not active / neutral". However, the problem with the additional, incorrect IP address still exists.
  10. @Donwo1995 Hello! There are a couple of wrong assumptions in your scenario: We do not log origin IP addresses according to the ToS and the current legal framework, therefore we can not provide information we do not have. Not really, as ports can be deleted/changed for account inactivity, pool shifts and other actions not involving the user. This problem can be resolved with specific payment methods without intermediaries. On a different, higher priority layer we must make clear that you can't come here, declare publicly an intent of illegal usage of the service by writing from an account that does not even have a valid subscription and then expect that AirVPN aids and abets this illegal usage through additional ad hoc options. If one really claims a criminal intent and comes here to declare it publicly, he/she should not expect help from AirVPN, in fact quite the contrary. Kind regards
  11. Broken on Fedora, Ubuntu, everything ARM64. ry@trixieGnome:~$ cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 13 (trixie)" NAME="Debian GNU/Linux" VERSION_ID="13" VERSION="13 (trixie)" VERSION_CODENAME=trixie DEBIAN_VERSION_FULL=13.0 ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" ry@trixieGnome:~$ eddie-ui Error loading shared library: /tmp/mono-bundle-JgbY1u/libgdiplus.so.0 libtiff.so.5: cannot open shared object file: No such file or directory ry@trixieGnome:~$ uname -a Linux trixieGnome 6.12.35+deb13-arm64 #1 SMP Debian 6.12.35-1 (2025-07-03) aarch64 GNU/Linux ry@cinnamon:~$ cat /etc/os-release NAME="Fedora Linux" VERSION="42 (Adams)" RELEASE_TYPE=stable ID=fedora VERSION_ID=42 VERSION_CODENAME="" PLATFORM_ID="platform:f42" PRETTY_NAME="Fedora Linux 42 (Adams)" ANSI_COLOR="0;38;2;60;110;180" LOGO=fedora-logo-icon CPE_NAME="cpe:/o:fedoraproject:fedora:42" DEFAULT_HOSTNAME="fedora" HOME_URL="https://fedoraproject.org/" DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f42/system-administrators-guide/" SUPPORT_URL="https://ask.fedoraproject.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Fedora" REDHAT_BUGZILLA_PRODUCT_VERSION=42 REDHAT_SUPPORT_PRODUCT="Fedora" REDHAT_SUPPORT_PRODUCT_VERSION=42 SUPPORT_END=2026-05-13 ry@cinnamon:~$ eddie-ui Error loading shared library: /tmp/mono-bundle-eIeG3Y/libgdiplus.so.0 libtiff.so.5: cannot open shared object file: No such file or directory ry@cinnamon:~$ uname -a Linux cinnamon 6.15.6-200.fc42.aarch64 #1 SMP PREEMPT_DYNAMIC Thu Jul 10 18:51:34 UTC 2025 aarch64 GNU/Linux ry@armubuntu2504:~$ uname -a Linux armubuntu2504 6.14.0-24-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Sun Jun 15 11:00:47 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux ry@armubuntu2504:~$ cat /etc/os-release PRETTY_NAME="Ubuntu 25.04" NAME="Ubuntu" VERSION_ID="25.04" VERSION="25.04 (Plucky Puffin)" VERSION_CODENAME=plucky ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=plucky LOGO=ubuntu-logo ry@armubuntu2504:~$ eddie-ui Error loading shared library: /tmp/mono-bundle-Zo2Dnt/libgdiplus.so.0 libjpeg.so.62: cannot open shared object file: No such file or directory This really needs to be fixed. A Linux ARM64 build that is broken on all modern ARM64 distributions and the Raspberry Pi is not a good showing. This limits my use of AirVPN. (At least I have been able to do a workaround on a debian 12 vm and it works for now)
  12. Yesterday
  13. This is not possible with any offered challenge types on AirVPN. HTTP-01 requires port 80, TLS-ALPN-01 port 443, but users cannot forward ports <1024. DNS-01 requires setting TXT records in DNS, but users cannot edit the airdns.org zone.
  14. To illustrate a potential privacy risk with port forwarding, consider this hypothetical scenario. Strike 3 Holdings automatically monitors copyright infringement, logging an IP address, timestamp, port, and the port's open status. The IP belongs to an AirVPN server, which would normally halt legal action. However, in this case, Strike 3 Holdings obtains a court order. The order compels AirVPN to identify the user connected to the server at the time of infringement and using the forwarded port in question. In response, AirVPN staff would identify the IP's port pool and query their database for the user account currently forwarding that port. Because AirVPN offers static port forwarding, this query would likely identify the infringer's account. This alone is insufficient for disclosure. The port could have been relinquished after the infringement, and AirVPN keeps no historical port forwarding logs. Users can also change port configurations during a session. A more detailed examination, however, reveals a problem. Port forwarding can only be managed via the AirVPN website, which logs login dates and basic browser information for security purposes. The hypothetical user, Joe Smith, has not logged in since initially configuring his forwarded ports long ago. The timestamp of the infringement is more recent than the last recorded login for the account holding the forwarded port. This creates compelling evidence that the account owner continuously held that port forwarding rule since their last login. AirVPN would then be compelled to provide Joe's username, login history, current ports, origin IPs, and payment transaction IDs. With this information, Strike 3 Holdings can subpoena payment processors and ISPs to uncover Joe Smith's identity.
  15. I have two ethernet interfaces. On Fedora Linux. I have set eddie to use en0. When eddie is not running ie vpn is down, my en1 interface operates in shared mode. en0 connects to the internet A second PC is connected to interface en1 via a hub and the second PC can then see the internet When the VPN is running, my local Fedora can see the internet, but the second PC can no longer connect to en1 . How can I fix this so I can share my connection to the upstream laptop. Thank you
  16. Hello! Yes, thanks a lot! It will be fixed very soon. Kind regards
  17. I seem to miss the link between the contents of the article and port forwarding, and by extension a link between port forwarding and any individual BitTorrent activity involving copyrighted works. Therefore, this feature makes no sense.
  18. Why should UK get any more servers? The bandwidth is maybe 60% used.
  19. If you need specific VoD services unlocked, this can be arranged even without having a server in Turkey. With enough demand, a rerouting server may be set up.
  20. Hello everyone, I want to save myself a web hosting account and make a REST API for my home automation accessible via the AirVPN Dynamic DNS service. The whole thing should run on an Unraid server, and it must absolutely have a TLS/SSL certificate accepted by browsers (e.g., Let's Encrypt). Is this possible?If yes, how? Thank you very much! Jomsen
  21. @Staff etc/airvpn/bluetit.rc from RC3 x86_64 tarball still contains the deprecated airvpnconnectivitycheck option and the new networkcheck isn't included. Also checked ARM64 tarball: same. I guess all tarballs are affected.
  22. Last week
  23. Looks good, problem seems solved. Thanks
  24. The heat on torrenting is getting worse - https://torrentfreak.com/u-s-court-orders-up-to-97500-in-damages-for-sharing-adult-films-via-bittorrent-250322/ The weak link in privacy is port forwarding, so adding an easy-to-use expiration date to a port would help users with their privacy. It could have practical time windows of usage: 12 hours, 1 day, 2 days, 7 days I think it would be a nice opt-in feature.
  25. Hello! We're very glad to inform you that Hummingbird 2.0.0 Release Candidate 3 is now available for macOS, both for Intel and M1/M2/M3/M4 based systems. The links to the latest RC 3 and the main changes have been updated in the first message of this thread. This new version is linked against the latest OpenVPN3-AirVPN library version and improves gateway detection when used in WireGuard mode. Kind regards
  26. Hello! We're very glad to inform you that AirVPN Suite 2.0.0 Release Candidate 3 for Linux is now available. The original post is updated to show the new download URLs. The important improvements over RC 2 are: bug fixes Blutetit: added run control directive networkcheck (please see the included user's manual readme.md) Bluetit: removed run control directive airvpnconnectivitycheck (superseded by networkcheck directive) gateway is set in case it was not provided at construction time Special note for firewalld users Please read here, it's very important: https://airvpn.org/forums/topic/70164-linux-network-lock-and-firewalld/ Please note that compatibility with Debian 10 and its derivatives, that reached end of long term support and end of life on June 2024, is lost even for the legacy version, mainly because the Suite is now C++20 compliant. The legacy version remains suitable for Debian 11 and its derivatives. Kind regards
  27. Me too, but I can see where they come from: Secret services of different countries working together is a bad dream for anyone worried about surveillance and other secret activities. So someone constantly connecting to a VPN server in a country part of such intelligence-sharing agreements will find themselves reeling from paranoia since, no matter where you connect, the "eyes" will always be on you. Those people all ignore one simple prerequisite: The eyes must first be on you. But since it's secret services we're talking about, the paranoid mind will assume constant observation. Which absolutely no human, or even a group of humans, will ever be able to do. If it were so effective, we'd see massive strides in criminal case clearance rates because, why even take part in intelligence sharing? Alas, clearance rates are all below 50% in the States alone for all categories. For Germany, it's close to 60% on average, highest for generally crimes against humans (murder, insult, etc), lowest for generally crimes against goods (damage to property, theft, etc.). We do debate about data retention from time to time, especially if some big crime happens, but no, data retention is not in effect in Germany. Some conservatives are loud, though, trying to get it back. All servers are setup very similarly, and all locations adhere to AirVPN's standard. AirVPN doesn't even bother looking at datacenters in the countries themselves if their legal framework doesn't allow that standard. So feel free to choose what works best for you latency/throughput-wise, all servers are safe. If things change, the servers might disappear, too, but this is always announced.
  1. Load more activity
×
×
  • Create New...