Not connected, Your IP: 216.73.216.108
Online: 35190 users - 436464 Mbit/s total BWAll Activity
This stream auto-updates
- Past hour
-
airvpn push ipv6 on ipv4 only connection floods log
willowvpn replied to willowvpn's topic in Troubleshooting and Problems
So openvpn config now has: pull-filter ignore "ifconfig-ipv6" pull-filter ignore "route-ipv6" pull-filter ignore "redirect-gateway ipv6" pull-filter ignore "dhcp-option DNS6" pull-filter ignore "tun-ipv6" pull-filter ignore "redirect-gateway" redirect-gateway def1 bypass-dhcp And the log is: Sat Dec 20 11:34:18 2025 daemon.notice netifd: Interface 'wan' is now up Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan Sat Dec 20 11:34:18 2025 user.notice firewall: Reloading firewall due to ifup of wan (wan) Sat Dec 20 11:34:19 2025 daemon.warn openvpn(airvpn)[2294]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TCP/UDP: Preserving recently used remote address: [AF_INET]194.187.251.90:443 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Socket Buffers: R=[131072->131072] S=[16384->16384] Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Attempting to establish TCP connection with [AF_INET]194.187.251.90:443 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TCP connection established with [AF_INET]194.187.251.90:443 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TCPv4_CLIENT link local: (not bound) Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TCPv4_CLIENT link remote: [AF_INET]194.187.251.90:443 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TLS: Initial packet from [AF_INET]194.187.251.90:443, sid=a904da59 0707d733 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: VERIFY KU OK Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Validating certificate extended key usage Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: VERIFY EKU OK Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Columba, emailAddress=info@airvpn.org Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, peer certificate: 4096 bits RSA, signature: RSA-SHA512, peer temporary key: 253 bits X25519 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: [Columba] Peer Connection Initiated with [AF_INET]194.187.251.90:443 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TLS: tls_multi_process: initial untrusted session promoted to trusted Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.14.145.1,dhcp-option DNS6 fde6:7a:7d20:a91::1,tun-ipv6,route-gateway 10.14.145.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:7d20:a91::1000/64 fde6:7a:7d20:a91::1,ifconfig 10.14.145.2 255.255.255.0,peer-id 0,cipher CHACHA20-POLY1305,protocol-flags cc-exit tls-ekm dyn-tls-crypt,tun-mtu 1500' Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Pushed option removed by filter: 'redirect-gateway ipv6 def1 bypass-dhcp' Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Pushed option removed by filter: 'dhcp-option DNS6 fde6:7a:7d20:a91::1' Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Pushed option removed by filter: 'tun-ipv6' Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Pushed option removed by filter: 'ifconfig-ipv6 fde6:7a:7d20:a91::1000/64 fde6:7a:7d20:a91::1' Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: OPTIONS IMPORT: --ifconfig/up options modified Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: OPTIONS IMPORT: route-related options modified Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: OPTIONS IMPORT: tun-mtu set to 1500 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_route_v4_best_gw query: dst 0.0.0.0 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_route_v4_best_gw result: via 192.168.1.1 dev wan Sat Dec 20 11:34:19 2025 daemon.notice netifd: Interface 'airvpn' is enabled Sat Dec 20 11:34:19 2025 daemon.notice netifd: Network device 'tun0' link is up Sat Dec 20 11:34:19 2025 daemon.notice netifd: Interface 'airvpn' has link connectivity Sat Dec 20 11:34:19 2025 daemon.notice netifd: Interface 'airvpn' is setting up now Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TUN/TAP device tun0 opened Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_iface_mtu_set: mtu 1500 for tun0 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_iface_up: set tun0 up Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_addr_v4_add: 10.14.145.2/24 dev tun0 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: /usr/libexec/openvpn-hotplug up airvpn tun0 1500 0 10.14.145.2 255.255.255.0 init Sat Dec 20 11:34:19 2025 daemon.notice netifd: Interface 'airvpn' is now up Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_route_v4_add: 194.187.251.90/32 via 192.168.1.1 dev [NULL] table 0 metric -1 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_route_v4_add: 0.0.0.0/1 via 10.14.145.1 dev [NULL] table 0 metric -1 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_route_v4_add: 128.0.0.0/1 via 10.14.145.1 dev [NULL] table 0 metric -1 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Initialization Sequence Completed Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Data Channel: cipher 'CHACHA20-POLY1305', peer-id: 0, compression: 'stub' Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Timers: ping 10, ping-restart 60 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Protocol options: protocol-flags cc-exit tls-ekm dyn-tls-crypt Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: exiting on receipt of SIGTERM Sat Dec 20 11:34:19 2025 user.notice firewall: Reloading firewall due to ifup of airvpn (tun0) Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: started, version 2.90 cachesize 1000 Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: DNS service limited to local subnets Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: UBus support enabled: connected to system bus Sat Dec 20 11:34:24 2025 daemon.info dnsmasq-dhcp[1]: DHCP, IP range 192.168.8.100 -- 192.168.8.249, lease time 12h Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: read /etc/hosts - 12 names Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 2 names Sat Dec 20 11:34:24 2025 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses I think log no longer shows an error, but does this look right? ipleak.net tells there is airvpn server DNS ipv6 reachable -
-
-
-
- Today
-
-
-
-
-
-
-
Hello! It's by Telecomix, a group an AirVPN founder co-operated with! https://en.wikipedia.org/wiki/Telecomix Kind regards
-
Thank you for your feedback. I am using another VPN provider and have set up three wire-guard tunnels. It works great. I have decided to try Air-VPN. They all (my current VPN and Air-VPN) use similar listening ports. The Air-VPN tunnel peer does not handshake. Finally, I have been able to use Air-VPN wire-guard to connect from my Linux box without issues. The Linux box is behind the Pfsense firewall. The problem arises when I try to implement the connection on my Pfsense firewall/router. -
My over the top setup (servers with lowest divergence compared to baseline speedtest)
-
i searched it up on the search engine and stumbled upon a website called https://www.datalove.me Just want to point it out.
-
it happens to me too, also whenever I try new linux distros I always install Eddie to check if it works, and the "laggy" problem occurs in 90% of the distros I try I always assumed it was because of that "Mono" library, but it has been there forever so I never reported it because I know it is a big change that won't happen in the near future.
- Yesterday
-
The other provider you use listens for connections on what port? Personally I've had ISPs that block wireguard on the ports that AirVPN uses but not on port 80, for example. -
AirVPN API - Status Endpoint Discussion
Esurient replied to Esurient's topic in General & Suggestions
Oh that's perfect, now I can get rid of the subnet scanning behavior from the app and speed up the db check, Thanks for the help! Hope they add this into the FAQ or other relevant page. -
AirVPN API - Status Endpoint Discussion
Tech Jedi Alex replied to Esurient's topic in General & Suggestions
You are technically not getting assigned the IP, you're using the address of the server. But anyway, entry and exit IP addresses have been separate since time immemorial, the latter of which is irrelevant for clients wanting to connect, so it's not emitted by the status API. There are two ways to get that info, though. Query servername_exit.airservers.org. This one is used by Eddie for route checks. When connected, curl check.airservers.org (with /api for JSON, and prepend ipv4./ipv6. for specific IP version), see Specs, section VPN DNS Server > Special resolution & URLs. Actually, I was trying to find some documentation on that separation, but neither the FAQ nor the specs mention this. But it's in every server and sale announcement. Little bit of inconsistency there. So, now you know. -
I’m trying to set up an AirVPN WireGuard tunnel on pfSense, but I cannot get a handshake, despite the configuration appearing correct. Environment pfSense (current release) WireGuard package installed Existing WireGuard tunnel with another provider works correctly (so pfSense + WG itself is functional) What I’ve done Generated the WireGuard configuration using AirVPN’s Config Generator Created the WireGuard tunnel in pfSense using the provided: Private key Interface address (/32 as given) DNS (also tested without relying on tunnel DNS) Added the peer with: Correct public key Endpoint IP and port from AirVPN Allowed IPs as provided by AirVPN Assigned the WireGuard interface Created firewall rules allowing outbound traffic NAT configured as expected (same approach as my working WG tunnel) Symptoms Tunnel shows as up No handshake occurs No RX/TX traffic on the WireGuard status page Keys definitely match (regenerated multiple times) Interface address added (though handshake should occur even without it) What makes this confusing Another WireGuard provider works perfectly on the same pfSense box Same WAN, same firewall/NAT logic AirVPN’s UI no longer shows the older “Devices → WireGuard” workflow, only the config generator The same AirVPN config works when tested with wg-quick on Linux What I’m wondering Is there anything AirVPN-specific that pfSense requires (MTU, keepalive, endpoint handling)? Any known issues with AirVPN WireGuard peers and pfSense? Does AirVPN require a specific Allowed IPs or gateway configuration that differs from other providers? If anyone has AirVPN + WireGuard working on pfSense, I’d really appreciate insight into what I might be missing. Thank you for reading my post.
-
AirVPN API - Status Endpoint Discussion
Esurient replied to Esurient's topic in General & Suggestions
That was just an example, I did a check now on Germany, Adhil, Connected I have the IP 37.46.199.70, however reading the status API only 37.46.199.66, 37.46.199.67, 37.46.199.68 and 37.46.199.69 are exposed in the IPv4 entry whilst the client is stating it is using entry 3 (x.68), If I'm not wrong, if I were to do a DNS query on all DE servers, I get dig ANY de.all.vpn.airdns.org @dns1.airvpn.org +short 141.98.102.234 185.189.112.18 83.143.245.50 185.189.112.26 37.46.199.50 185.104.184.42 37.46.199.66 37.46.199.82 141.98.102.178 37.120.217.242 141.98.102.186 141.98.102.242 141.98.102.226 185.189.112.10 On the IPv4 section, which still does not match up the IP address I'm assigned. Edit: I have geo routing disabled. -
Is Turkey blocking Wireguard protocols?
Tech Jedi Alex replied to bwv1042's topic in Troubleshooting and Problems
Can you try a connection with Eddie, then provide a support file?. -
Hold on. Where did you even read that Eddie supposedly had a Web UI? Seems like the product of hallucination AI usage.
-
Port forwarding on Linux Mint
Tech Jedi Alex replied to RubberSoulWarrior's topic in Troubleshooting and Problems
While connected, bind qBittorrent to the tun0 interface and restart qBittorent. -
ANSWERED Eddie will not run on a Pi 5
oxygen4505 replied to AuContraire's topic in Eddie - AirVPN Client
Personally, I switched to the AirVPN Suite and gave up on Eddie UI on the Raspberry Pi 5. It’s a bit more complicated to set up at first if you’re not familiar with it (especially the network lock, in my case), but otherwise it looks solid and has been running reliably for several months at my place. -
AirVPN API - Status Endpoint Discussion
Tech Jedi Alex replied to Esurient's topic in General & Suggestions
Which server is that? It looked a bit like Asterope (UK) as it's the only one with .215 and .216 entry addresses, but its exit is .213. What do you mean by "subnet"? That info is not yielded by the status endpoint. And, if there is one info the status endpoint does not yield, it's the exit address. It can be queried via DNS, though. -
-
-
Similar situation with many German servers at the moment - I really hope the availability of usable AirVPN servers (those which are not blacklisted by Google's recaptcha and which YouTube still allows with only a regular Captcha an no login) does not deteriorate any further. I've been a very satisfied user of AirVPN's services for a couple of years but this behaviour of YouTube unfortunately might become a potential deal breaker. Maybe a way around that from the perspective of AirVPN might be exchanging servers every once in a while or configuring new IP addresses? I would say that currently less then half of German servers do work. Enjoy the holidays!
-
.thumb.png.8be84fd39f94c1640ac8c5456fbf3449.png)
ANSWERED Help with setting up external access Plex server
Staff replied to robzeta's topic in Troubleshooting and Problems
Hello! Yes, keep in mind (it was clarified in other threads, not this one) that Plex always listens to port 32400 of the VPN interface, no matter what. Therefore you should "re-map" the server port 33585 to your local VPN interface port 32400 (directly on your AirVPN account port panel). Note: hot change is supported for remote port only, so when you change local port on your AirVPN account port panel, if you are already connected to the VPN please disconnect and re-connect to apply the change. Kind regards -
It's so much easier on our state of the art VT100, but the bosses promised that we could have the brand new VT220 for Christmas if we behave, ROFL.
-
Hello! It sounds like some Mono related problem, can you check your Mono version in your system (and update it if newer version is available)? Kind regards
-
- Last week
-
ANSWERED Help with setting up external access Plex server
bidasci replied to robzeta's topic in Troubleshooting and Problems
I am getting the same problem as well. Is there something that I am doing wrong? ESET firewall rules for Plex is already allowed both directions, any port, TCP and UDP, and it still fails. Do I have to set local port to 32400? -
I am on linux mint 22.2 and for me Eddie is lightning. My hardware is top notch with 64 GB of ddr5 and a matching level processor on the motherboard. Eddie just couldn't be faster so its something on your end. Don''t know if it matters but I am also on strong fiber.
-
Yeah. You could say it's been defaced. Use the 😈 goddamn 👺 emojis "<evil grin>" this is so cringe lmao
-
That's most probably why – it now removed the whole redirect-gateway option. Which may actually be expected because it's using prefix comparison! From the manual: So it's not an exact match – it's a starts-with match! Learned something new today. So, going by that description I thought something like this would work: pull-filter ignore "redirect-gateway ipv6" pull-filter accept "redirect-gateway " But, well, OpenVPN deletes the whole option since it starts with redirect-gateway ipv6, so for the second pull-filter there is no longer any redirect-gateway to accept. I next thought, a workaround from server-side would be to put ipv6 at the end of the pushed redirect-gateway option. This would maybe allow the construct found in the manual to do what is expected: pull-filter accept "redirect-gateway def1 bypass-dhcp" pull-filter ignore "redirect-gateway " .. but on closer look, no, the second option would remove the whole line again.. So, I believe ignoring the pushed option in its entirety and setting it yourself is your solution. pull-filter ignore "redirect-gateway" redirect-gateway def1 bypass-dhcp Along with the other pull-filter options, of course.
-
Eddie Android edition 4.0.0 preview available
lordlukan replied to Staff's topic in News and Announcement
The default Eddie 4.0 beta 1 settings work on RU mobile networks with Amnezia (quick test). The settings above are not the same! Hello, that's not working for .Ru on the android. Maybe someone can advice parametrs to avoid ISP blocks for .Ru
