All Activity
This stream auto-updates
- Past hour
-
-
-
-
-
-
-
-
-
-
- Today
-
Hm? You can use it like that? Awesome! Then please use it like so, no need for AirVPN to implement it.
-
@stallard Hello! At least one error is visible: remote port number differs from local port number. Due to how a torrent program works you must configure matching remote and local ports (for additional details please read the FAQ). Just delete the "local" field of your remote port in your AirVPN account port panel, adjust qBittorrent listening port accordingly, re-start both VPN connection and qBittorrent and follow this checklist: https://airvpn.org/forums/topic/66388-port-forwarding/?tab=comments#comment-243305 Additional tips for the errors you get: Error 111 (connection refused): the connection has been actively reset by the destination system (the client, in this case your system) through a TCP RST Error 110: no reply from the destination system (client), the sent packet has been silently dropped Further information on p2p programs: https://airvpn.org/faq/p2p/ Kind regards
-
-
Hi All, I have qbittorrent on TrueNAS, run by an arr stack. Qbittorrent seems to upload/seed ok, until I tried a private tracker- and they indicate my port is closed. And I have no leechers, so I suppose that's true. So I decided to test, with the results below. Seems my port is actually closed? Odd that some torrents are seeding. Kind of lost now... the tracker list in qBit says that the trackers are working- but there are 0 peers. Does this make any sense to anyone? Thanks for any tips...I'm not even sure if I'm asking the right questions.
-
-
Hello AirVPN, Goodbye NordVPN :D
Glidos replied to catman7's topic in Other VPN competitors or features
Just did a little better with a New York server: 181.03 down 48.10 up ... and then later 300Mbps in a speed test and a torrent hit 30MBps. Hmmm! -
Hello AirVPN, Goodbye NordVPN :D
Glidos replied to catman7's topic in Other VPN competitors or features
That's really interesting. I wonder why I cannot achieve such speeds. I'm connecting from the UK. I've experimented with several different servers. 125Mbps down is the best I've seen from AirVPN so far. Currently I'm connected via the Chamukuy server in Canada. I'm getting 43.07 down, 69.45 up (Mbps). I'm using Openvpn UDP, which I know has overhead, but I was using that with Nord (and with Ivacy back a while). My fibre connection gives me a reliable simetric 600Mbps. -
-
Found the issue, it seems I have changed the network zone, so changed destionation zone from Internal to DMZ and that fixed it.
-
Hello AirVPN, Goodbye NordVPN :D
fsy replied to catman7's topic in Other VPN competitors or features
Uhm, 35 MBps (280 Mbit/s) is no match for airvpn : the top users routinely exceed it, if you check the stats you'll see ... with my ISP off peak I can beat 800 Mbit/s (100 MBps) on my Gbit line in northern Europe and when in the US ... although I have no comparison to offer with Nord I'm already at 90% of my line - in real life I can never beat 850-900 Mbit/s without vpn, so.. -
-
I have synology DSM6 1. Synology quickconnect seems to have issue (message = error, check network or DNS) with UDP now, so i have to generate .ovpn file with TCP instead. And now quickconnect works. Who knows ?!?! 2. I have never toggled "Separate keys/certs from .ovpn file" button in the past but just the .ovpn file. Everything went fine as long as i specify "tls-auth, for 2.3" (not tls-crypt or >2.3). But now the config generator generate different .ovpn file and I have the message ".ovpn files contains invalid parameters". So I have to replace lines with data-ciphers and data-ciphers-fallback by one single line with "cipher AES-256-CBC". It's the same result than to do "set the "OpenVPN profile" combo box to "2.4"" but it's not natural to choose 2.3 on the left side and 2.4 on right side of the page... My two cents
-
- Yesterday
-
thanx for useful info. TrustTunnel is not a proxy, just new VPN protocol, and if i run it, then close and start Eddie, my speed increases (in Eddie) from 60Mb to peak 600Mb. without starting TrustTunnel i get max download speed 60Mb with WG activated. SSL and SSH gives me 200-300Mb, but only 8-9Mb of upload speed (due to ISP shaping)
-
-
Hello, how can I stop Eddie from automatically reconnecting to some slow server when it loses connection? I'd rather stay offline than have that. Also: Is it possible to force connection to a specific server in case a disconnect occurs somewhere in the settings? Thanks in advance!
-
-
-
Me UnifiOS 4.4.9 (latest official for the UCG-F) and also Network 10.0.162. But when I check now in the Client Area I don't even have a session active ... so something weird is going on, Already created a new device, new config, moved the ports to that new device and changed to the new IP because of the new device in the DNAT rules. Almost looks like AirVPN has issues. Will try to post some images tomorrow, watching Daytona 24 atm.
-
Yes, works for me too.
-
Yes, no problem on my end. For all intents and purposes:For all intents and purposes: For all intents and purposes: - UnifiOS 5.0.10 - Network 10.0.162
-
-
Hello! Your /etc/resolv.conf file is not a symlink according to Eddie. Question: in NetworkManager configuration, do you have something like: [main] dns=systemd-resolved If you set DNS directly via NetworkManager and NM is not configured as above, NM overwrites /etc/resolv.conf file (this would explain why it's not a symlink when you run Eddie). At the next systemd-resolved (re)start, it is over-written again as a symlink (this would explain why you see it as a symlink in your initial report and you need to re-start systemd-resolved each time). You should manage DNS either through NetworkManager only, systemd-resolved only (explicit delegation to systemd-resolved must be enforced on NM if you need to run it for other reasons), or by getting rid of Windows-like DNS management (go back to /etc/resolv.conf rock solid, old school management, optionally having NM manage resolv.conf directly). (*) Avoid any hodgepodge of different DNS managements, they come from Windows-style duct-taped DNS management jumble that have caused decades of huge problems including DNS leaks (we remember well svchost.exe DNS leaks disasters). (*) Should you decide to disable systemd-resolved completely remember to stop, disable and mask it, otherwise it may (will) be re-enabled and re-started without your knowledge by systemd. Maybe not, see here: Note how Eddie restores the previous DNS on enp12s0 correctly, and the previous resolv.conf backed up file that was not a symlink but contained the VPN DNS possibly for the reason previously explained or maybe for a mixture of NM / systemd-resolved concurrent usage. Try to delete the resolv.conf backup file and follow the previous suggestions, in particular make sure your system relies on a clean DNS management, then feel free to let us know whether the problem gets resolved. That's fine and expected, it's a safety feature of Eddie. If you want to prevent Eddie from managing DNS you have to disable this check by unticking "Check Air VPN DNS" in "Preferences" > "DNS" window. Kind regards
-
Does this still work for everybody? It seems my port forwarding suddenly stopped working and I can't seem to find the reason behind it. I have checked the ports are still configured with the same device, the same for the vpn config. Firewall rule and DNAT rule is still set and configured as suggested.
-
Hello AirVPN, Goodbye NordVPN :D
Glidos replied to catman7's topic in Other VPN competitors or features
Getting on for a decade later, but me too: I tried NordVPN for a few days, used their money back guarantee offer to end the subscription, and am now using AirVPN - but my experiences and reasons are far different from what has been said earlier in this thread. Nord are fast now, really fast. I had one torrent download at 35MBps (and I do mean bytes not bits). Generally they were faster than what I'n seeing from AirVPN now. What put me off Nord though was the lack of port forwarding. If I understand correctly, torrenting through Nord means not connecting with anyone else who uses Nord, or many of the other VPNs out there. I'm finding AirVPN speeds consistent and good enough (some servers download 125mbps upload 50mbps). I don't know enough about all this to determine whether that's good for 2026. The big difference for me, what I really like more than anything about AirVPN is the openness - that I can post something like this - that I'm not forced into a long-term contract. I can buy 3 days, a week, a month whatever, while I see how things go. People I can trusts is the feeling I'm getting. -
- Last week
-
Note I also try to define a file: /etc/systemd/resolved.conf.d/dns_servers.conf [Resolve] DNS=1.1.1.2 Although this works without VPN, then when I try to connect to a server with Eddie, then it fails at "Checking DNS" step and tries to reconnect indefinitely. I created a log when it cannot check the VPN, when systemd-resolved uses the file /etc/systemd/resolved.conf.d/dns_servers.conf I just described above: eddie-log-20260124.txt
-
Hi, thanks for your support. Unfortunately it does not work: I set up 9.9.9.9 for all interfaces using NetworkManager. I also deleted .config/eddie/default.profile $ resolvectl Global Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Current DNS Server: 9.9.9.9#dns.quad9.net Fallback DNS Servers: 9.9.9.9#dns.quad9.net 2620:fe::9#dns.quad9.net 1.1.1.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 8.8.8.8#dns.google 2001:4860:4860::8888#dns.google Link 2 (enp12s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6 Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 9.9.9.9 DNS Servers: 9.9.9.9 192.168.0.1 2606:4700:4700::1111 2a02:8070:d483:bf20:2e00:abff:fe88:c64 Default Route: yes Link 4 (wlan0) Current Scopes: none Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported Default Route: no Then I used Eddie to connect (as you mention, regardless of Network Lock, so I did not lock this time): $ resolvectl Global Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: foreign Current DNS Server: 10.128.0.1 DNS Servers: 10.128.0.1 fd7d:76ee:e68f:a993::1 Fallback DNS Servers: 9.9.9.9#dns.quad9.net 2620:fe::9#dns.quad9.net 1.1.1.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 8.8.8.8#dns.google 2001:4860:4860::8888#dns.google Link 2 (enp12s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6 Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 10.128.0.1 DNS Servers: 10.128.0.1 fd7d:76ee:e68f:a993::1 Default Route: no Link 4 (wlan0) Current Scopes: none Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported DNS Servers: 10.128.0.1 fd7d:76ee:e68f:a993::1 Default Route: no Link 5 (Eddie) Current Scopes: DNS Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 10.128.0.1 DNS Servers: 10.128.0.1 fd7d:76ee:e68f:a993::1 Default Route: no Then I exit Eddie: $ resolvectl Global Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Current DNS Server: 10.128.0.1 DNS Servers: 10.128.0.1 fd7d:76ee:e68f:a993::1 Fallback DNS Servers: 9.9.9.9#dns.quad9.net 2620:fe::9#dns.quad9.net 1.1.1.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 8.8.8.8#dns.google 2001:4860:4860::8888#dns.google Link 2 (enp12s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6 Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: fd7d:76ee:e68f:a993::1 DNS Servers: 10.128.0.1 fd7d:76ee:e68f:a993::1 Default Route: yes Link 4 (wlan0) Current Scopes: none Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported DNS Servers: 10.128.0.1 fd7d:76ee:e68f:a993::1 Default Route: no Here I do not have resolving. Eddie did not reinstate 9.9.9.9 to my interfaces. If I restart systemd-resolved: $ sudo systemctl restart systemd-resolved $ resolvectl Global Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Fallback DNS Servers: 9.9.9.9#dns.quad9.net 2620:fe::9#dns.quad9.net 1.1.1.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 8.8.8.8#dns.google 2001:4860:4860::8888#dns.google Link 2 (enp12s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6 Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 9.9.9.9 DNS Servers: 9.9.9.9 192.168.0.1 2606:4700:4700::1111 2a02:8070:d483:bf20:2e00:abff:fe88:c64 Default Route: yes Link 4 (wlan0) Current Scopes: none Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported DNS Servers: 10.128.0.1 fd7d:76ee:e68f:a993::1 Default Route: no this works again. This suggests a bug when Eddie handles stub based systemd-resolved configuration, no? Could Eddie simply restart systemd-resolved at exit? It has root permission. Would it be a possible solution?
-
Long-time Mac user here. Years ago I thought of Transmission as a decent entry-level plug-and-play BT app, which it indeed was. If all you needed was limited functionality/configurability it was fine. But today, according to numerous user complaints, it's buggy and there's virtually no support whatsoever. User requests for support go unanswered, as do requests for new features. IOW Transmission is dead and has been for several years. qBittorrent performs consistently well, is feature-rich, highly configurable, well-supported and receives regular updates.
-
-
AmneziaWG was recently introduced to Eddie Android. It can be surmised that it will find its way into all other clients, too, in the coming months. I don't think another protocol will come so quickly. Please experiment with AmneziaWG first. Besides, all proxy protocols are being shot down, like Shadowsocks. Further protocols like V2Ray were proposed, but since they're all proxy protocols, they will never be implemented. AmneziaWG, on the other hand, is Wireguard essentially, so it got attention.
-
Hello! The IPv6 networks are up and all the servers are operating normally. Kind regards
-
@Staff Any updates on this?
-
now it's open-source... plans to add? //Unlike those conventional VPN protocols, TrustTunnel is engineered to blend in with regular HTTPS traffic, making it far harder to throttle or block and helping it slip past deep-packet inspection, all while preserving strong privacy and security. It achieves this through TLS-based encryption, the same standard that secures HTTPS, and by leveraging HTTP/2 or HTTP/3 transport, which are ubiquitous on the web. Each connection runs on its own dedicated stream, which combines packets for faster, more efficient transmission. It is also optimized for mobile platforms and performs well even in unstable network conditions.
