Not connected, Your IP: 216.73.217.175
Online: 48416 users - 644929 Mbit/s total BWAll Activity
This stream auto-updates
- Past hour
-
-
-
-
-
-
-
- Today
-
-
-
-
Hello! Thank you for reporting this and sharing the workaround. The distinction you found between working IP connectivity and failing hostname resolution is useful. The explanation is consistent with a DNS configuration problem inside the namespace. 127.0.0.53 is systemd-resolved’s local DNS stub address. Since a network namespace has its own loopback interface, that address inside aircuckoo does not reach the resolver running in the main namespace. Unless a resolver is also listening inside aircuckoo, DNS requests sent there cannot succeed. See the systemd-resolved documentation. https://www.man7.org/linux/man-pages/man8/systemd-resolved.service.8.html Providing reachable DNS servers through /etc/netns/aircuckoo/resolv.conf is therefore a reasonable workaround for the reported symptoms. The namespace-specific configuration mechanism is documented in ip-netns https://www.man7.org/linux/man-pages/man8/ip-netns.8.html, and Cuckoo also applies the namespace’s configuration files when launching an application. Two clarifications: This does not establish that Network Lock caused the problem. Disabling networklockpersist would not make the main namespace’s loopback resolver accessible inside aircuckoo. There is no need to disable that protection to address this DNS issue. Also, the Suite 2.1.0 manual documents networklockpersist as off by default. Please do not assume the manual DNS override will survive namespace recreation. Bluetit manages this directory and can remove and regenerate its contents during the traffic-splitting lifecycle. Cuckoo intentionally runs applications outside the VPN. DNS requests made to Cloudflare or Google through this configuration also follow the non-VPN path; choosing those resolvers changes who receives the queries. To investigate why the stub address was selected, please share your distribution and Suite version, relevant traffic-splitting and Network Lock settings, and: readlink -f /etc/resolv.conf cat /etc/resolv.conf cat /etc/netns/aircuckoo/resolv.conf resolvectl status The Bluetit startup log, particularly the “Found system … DNS” entries, would also help. Please remove credentials and other sensitive information before posting. There is no need to undo the working workaround. Kind regards
-
-
-
Before we begin, I want to point out that I do not understand computer networking. It's so foreign to me that I can't wrap my head around it. After many hours, I turned to AI for assistance. I agree that the flaws within AI far outweigh the good. My work requires me to use AI, so I think it's ridiculous that I can't use the free version of Claude while my boss profits from it. I think that is hypocritical. Claude has helped me solve a range of issues, from incompatible library versions and bash scripting to a functioning Cuckoo. I provided Claude with the readme.md and my shell logs, and was immediately returned with a fix. I want to share what was found so that the AIRVPN Suite documentation or the Suite itself can be updated. The issue that I had was that Cuckoo did not have connectivity. While this fix might have been trivial to others, it's outside my understanding. Here is Claude's fix " That confirms it exactly: routing works fine (ping by IP succeeds), but DNS is broken because resolv.conf inside aircuckoo points to 127.0.0.53 — the systemd-resolved stub, which only exists in your main namespace. Inside aircuckoo there's nothing listening on that loopback address, so every hostname lookup dies silently, which is exactly the "Failed to fetch" pattern you saw. The fix is to give the aircuckoo namespace real, reachable nameservers instead of the stub resolver. Since network namespaces get their own loopback, create a namespace-specific override: sudo mkdir -p /etc/netns/aircuckoo sudo tee /etc/netns/aircuckoo/resolv.conf > /dev/null <<'EOF' nameserver 1.1.1.1 nameserver 8.8.8.8 EOF This is picked up automatically by ip netns exec for anything run in that namespace, without touching the main system's DNS config. Then Test: sudo ip netns exec aircuckoo getent hosts google.com Relaunch Vivaldi: cuckoo -r vivaldi A couple of things to be aware of going forward: If Bluetit ever regenerates the namespace (e.g., after a systemctl restart bluetit), the /etc/netns/aircuckoo/resolv.conf file should persist since it lives outside the namespace itself, but worth re-testing after a restart just in case. You can swap 1.1.1.1/8.8.8.8 for whatever resolvers you prefer (your router's, or your ISP's). " This tells me there is a problem with having network lock enabled; the bluetit.rc has its default value. If I changed network lock persist to off, maybe that would have solved the problem? I won't bother changing it now; maybe if Cuckoo stops working, I'll try changing networklockpersist to off. I'm not going to pretend like I understand how a resolver works or how to configure a resolv.conf, be gentle. If you would like my logs or configurations, let me know.
-
[SOLVED] Network lock protection lost when eddie-ui crashes
cheeze replied to zebulon's topic in Eddie - AirVPN Client
and any required dependencies Yes right there is part I try to make sure is included in the download. Thank you for explaining why this happens. -
for the last few days it worked fine thanks for fixing it
-
Hello everyone! I recently learned about the airvpn. What i like is the tools are all opensource, aligns with my ethos. I even used ipleak back in the day to check my ip info as well. Later i found out that it was made by air's team as well. What truly surprised me is the availability of a forum. It's quite rare and i like it. The website reminds me of archlinux, simple and functional not following every UI/UX trends. I don't have a active plan right now as i joined-in today. Missed the deal by a day, oh well. I am using linux, and earlier with another vpn service i used to get the openvpn files and set it up inside the kde plasma network-manager then setup a firewall rule as kill switch. Is eddie gui a better way to connect to airvpn on archlinux, instead of the above method?
- ...
-
- 1
-
-
-
-
Hello, I am using the latest version of Eddie for Windows 10 (2.27.2) because I wanted to use openvpn with DCO. However, I noticed that this version crashes from time to time without any specific pattern. My windows event viewer only shows that "Eddie-cli-elevated.exe, version 2.26.0.0" errored with event id 1000. When I re-open Eddie, the logs are re-written so I don't have any specific information to share. Is there any place I can look for more information to share and help with the report of this issue? Thanks in advance.
-
-
Version 1.1 is now published. Thanks again to everyone who provided technical feedback on the original release. I went back through the testing and expanded the investigation substantially. The main changes in v1.1 are: - Clarified that the kill switch tested in the paper was my own system-level nftables policy used with wg-quick, not AirVPN Eddie or Network Lock. - Corrected the test environment to Linux Mint 22.3. - Added controlled IPv6 testing using a known-working non-VPN IPv6 path rather than relying on an environment where IPv6 connectivity was unavailable. - Added deliberate nftables startup-failure testing and hardened the systemd dependencies so general networking will not start if the firewall fails. - Found a shutdown edge case where a broad OUTPUT established-state rule allowed a known TCP flow to emit a FIN packet outside the tunnel during reboot. - Removed that rule and verified that the reproduced shutdown escape no longer occurred. - Documented exactly how wg-quick and systemd-resolved configured AirVPN DNS. - Added simultaneous packet capture showing DNS inside the logical VPN interface while no port-53 DNS appeared on the physical interface. - Tightened the distinction between what I directly observed, what AirVPN states about its service, and what third-party sources report. - Added a sanitized reproducibility package containing configuration snapshots, software versions, evidence indexes, SHA256 hashes, and reviewed packet-capture artifacts. Zenodo v1.1: https://doi.org/10.5281/zenodo.23027447 GitHub: https://github.com/Fragmented-Sentinel/what-a-vpn-actually-hides GitHub v1.1 release: https://github.com/Fragmented-Sentinel/what-a-vpn-actually-hides/releases/tag/v1.1 I have kept v1.0 available rather than replacing it so that the changes and corrections remain transparent. One of the more interesting things that came out of the additional testing was that a configuration can appear secure during normal operation while still failing during startup or shutdown. Deliberately forcing those failure states turned out to be much more informative than another successful leak test. - Yesterday
-
Hello, I am trying to set up a Jellyfin server for remote access through the VPN to be available outside my local network. Jellyfin is reachable from the Internet through my normal public IP and router port forwarding (tested from my phone using mobile network). With Eddie running and AirVPN connected, the forwarded connection times out. pktmon shows the incoming TCP SYN reaching the VPN interface at 10.184.203.83:8096, but no SYN-ACK is returned. Jellyfin is listening on 0.0.0.0:8096, and Windows Firewall has an inbound TCP/8096 allow rule. I have a Plex media server and qBittorrent running correctly with forwarded ports through AirVPN, but the Jellyfin port is never open and always times out. I set up Jellyfin the same way I did for Plex and qBittorrent, with the applications and the Eddie client running on the same machine, and everything goes through the VPN with network lock. Plex has the 32400 local port, and a randomly assigned external port from AirVPN, it shows as open, and I can access Plex outside of my local network. Jellyfin however, does not work through the VPN despite the same port forwarding set up (8096 local port, random external port). Jellyfin settings match with AirVPN settings, the local port is 8096, and the "public HTTP port number" setting in Jellyfin is set to the same external port in my client area. Any suggestions? Thank you so much in advance -
-
-
-
-
New 10 Gbit/s server available (SE)
Tim Cooks pasta replied to Staff's topic in News and Announcement
Very nice!!! I've had some speed issues with the other Nordic servers, but Formosa speeds are great!!! -
.thumb.png.8be84fd39f94c1640ac8c5456fbf3449.png)
Swiss Servers always disconnects and packet loss?
Staff replied to Gandalf15's topic in Troubleshooting and Problems
Hello! Any problem related to IPv4 seems resolved. IPv6 related problems persist. The warning on packet loss you can see on the servers monitor is caused by IPv6 related problems: intermittent but very frequent packet loss. These problems do not affect Athebyne, Dorado and Toliman. We are in touch with the dc engineers while investigating this problem. Kind regards -
Having the VPN handled in a home router (running OpenWRT for example) could be a solution not involving an outdated OS.
-
@19990909jp @alrosm@sbcglobal.net Hello! If you prefer to keep Windows 7 for now, you can still connect to AirVPN using OpenVPN 2.4.12 for Windows 7, independently of Eddie. The installer is available from the official OpenVPN archive: https://build.openvpn.net/downloads/releases/openvpn-install-2.4.12-I601-Win7.exe. Generate your configuration files using the AirVPN Configuration Generator, selecting compatibility with OpenVPN 2.4, then import the downloaded .ovpn files into OpenVPN GUI: https://airvpn.org/generator/. Please consider this a temporary workaround. OpenVPN 2.4.12 itself is no longer supported, as indicated here: https://community.openvpn.net/Pages/Supported versions. A long-term solution requires moving to a more modern, actively supported operating system, whether a supported Windows version, FreeBSD or a Linux distribution compatible with your hardware. Microsoft ended Windows 7 support in January 2020, and its Extended Security Updates programme ended in January 2023. Continuing to use Windows 7, especially for Internet access, exposes you to vulnerabilities that no longer receive fixes from Microsoft: https://learn.microsoft.com/en-us/lifecycle/products/windows-7 A VPN protects traffic through the VPN tunnel, but it cannot fix operating system vulnerabilities or protect your data from malware already running on your computer. Restoring the VPN connection does not eliminate these risks. Kind regards
- Last week
-
is there a win7 soution please
-
-
Hello, I just opened my AirVPN account yesterday and can't seem to get any connections because the program hangs when checking IPv4. I am using a bulk wifi service provided by whitesky. I've tried other suggestions I've seen on the forum, such as switching from automatic to strictly a TCP protocol, but even when I am able to complete a connection there is no internet access. I have tried: Changing ports (443, 53), which did not stop it from hanging Changing protocol to TCP, which allowed a connection but no internet Stopping safety checks, which allowed a connection but no internet Changing network preferences from [IPv4, IPv6] to [IPv6, IPv4], to just IPv6, which did not stop it from hanging I can't seem to find a working solution online, but I was able to make a connection just fine last night. I also tried connecting through mullvad, which was able to connect but was similarly unable to access the internet. I fear it may be out of my control and up to the whims of my network manager. My logs are below. . 2026.09.27 16:42:16 - Eddie version: 2.26.2 / windows_x64, System: Windows, Name: Windows 10 Pro, Version: 10.0.26200.0, Framework: v4.0.30319 . 2026.09.27 16:42:16 - Command line arguments (1): path="home" . 2026.09.27 16:42:16 - Privileged tools run from: install directory (secure, no staging) . 2026.09.27 16:42:16 - Runtime directory: C:\ProgramData\Eddie-VPN\run\service . 2026.09.27 16:42:16 - Collect network information . 2026.09.27 16:42:16 - Reading options from C:\Users\wooff\AppData\Local\Eddie\default.profile . 2026.09.27 16:42:16 - WireGuard - Version: 1.0 . 2026.09.27 16:42:16 - OpenVPN - Version: 2.7.3 - OpenSSL 3.6.2 7 Apr 2026, LZO 2.10 (C:\Program Files\AirVPN\openvpn.exe) . 2026.09.27 16:42:16 - SSH - Version: OpenSSH_for_Windows_9.5p2, LibreSSL 3.8.2 (C:\WINDOWS\System32\OpenSSH\\ssh.exe) . 2026.09.27 16:42:16 - SSL - Version: 5.69 (C:\Program Files\AirVPN\stunnel.exe) I 2026.09.27 16:42:16 - Ready . 2026.09.27 16:42:18 - Collect information about AirVPN completed I 2026.09.27 16:42:21 - Session starting. . 2026.09.27 16:42:21 - Activation of Network Lock - Windows Filtering Platform I 2026.09.27 16:42:21 - Checking authorization ... ! 2026.09.27 16:42:21 - Connecting to Guniibuu (United States of America, Phoenix, Arizona) . 2026.09.27 16:42:22 - Routes, add 198.44.133.70/32 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:42:22 - WireGuard > Setup start . 2026.09.27 16:42:22 - WireGuard > Setup complete . 2026.09.27 16:42:22 - WireGuard > Setup interface . 2026.09.27 16:42:22 - WireGuard > Received first handshake . 2026.09.27 16:42:22 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2026.09.27 16:42:22 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2026.09.27 16:42:22 - DNS leak protection with packet filtering enabled. . 2026.09.27 16:42:22 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.128.0.1) . 2026.09.27 16:42:22 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:42:23 - DNS IPv4 of a network adapter forced (Eddie 1, from automatic to 10.128.0.1) . 2026.09.27 16:42:23 - DNS IPv6 of a network adapter forced (Eddie 1, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:42:23 - DNS IPv4 of a network adapter forced (Ethernet, from automatic to 10.128.0.1) . 2026.09.27 16:42:23 - DNS IPv6 of a network adapter forced (Ethernet, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:42:23 - Routes, add 0.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:42:23 - Routes, add 128.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:42:23 - Routes, add ::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:42:23 - Routes, add 8000::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:42:23 - Routes, add 198.44.133.99/32 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:42:24 - Routes, add 2607:9000:7000:31:b9a5:25fa:cb5:227a/128 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:42:24 - Flushing DNS I 2026.09.27 16:42:24 - Checking route IPv4 . 2026.09.27 16:42:30 - Checking route (4° try) . 2026.09.27 16:42:34 - Checking route (5° try) ! 2026.09.27 16:42:44 - Disconnecting . 2026.09.27 16:42:44 - WireGuard > Stop request received . 2026.09.27 16:42:44 - WireGuard > Stopping . 2026.09.27 16:42:44 - WireGuard > Completed . 2026.09.27 16:42:45 - Routes, delete 198.44.133.70/32 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:42:45 - Routes, delete 198.44.133.99/32 for interface "{C75FB5A6-ACC2-4B5D-A63C-125523436AC4}", not present. . 2026.09.27 16:42:46 - Routes, delete 2607:9000:7000:31:b9a5:25fa:cb5:227a/128 for interface "{C75FB5A6-ACC2-4B5D-A63C-125523436AC4}", not present. . 2026.09.27 16:42:46 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:42:46 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:42:46 - DNS IPv4 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:42:46 - DNS IPv6 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:42:46 - DNS IPv4 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:42:46 - DNS IPv6 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:42:46 - DNS leak protection with packet filtering disabled. . 2026.09.27 16:42:46 - Collect network information . 2026.09.27 16:42:46 - Connection terminated. I 2026.09.27 16:42:46 - Cancel requested. . 2026.09.27 16:42:46 - Deactivation of Network Lock ! 2026.09.27 16:42:46 - Session terminated. I 2026.09.27 16:43:28 - Session starting. . 2026.09.27 16:43:28 - Activation of Network Lock - Windows Filtering Platform I 2026.09.27 16:43:28 - Checking authorization ... ! 2026.09.27 16:43:29 - Connecting to Guniibuu (United States of America, Phoenix, Arizona) . 2026.09.27 16:43:29 - Routes, add 2607:9000:7000:31:2f0:97c2:7575:e9e3/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:43:29 - WireGuard > Setup start . 2026.09.27 16:43:29 - WireGuard > Setup complete . 2026.09.27 16:43:29 - WireGuard > Setup interface . 2026.09.27 16:43:29 - WireGuard > Received first handshake . 2026.09.27 16:43:29 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2026.09.27 16:43:29 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2026.09.27 16:43:29 - DNS leak protection with packet filtering enabled. . 2026.09.27 16:43:30 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.128.0.1) . 2026.09.27 16:43:30 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:43:30 - DNS IPv4 of a network adapter forced (Eddie 1, from automatic to 10.128.0.1) . 2026.09.27 16:43:30 - DNS IPv6 of a network adapter forced (Eddie 1, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:43:30 - DNS IPv4 of a network adapter forced (Ethernet, from automatic to 10.128.0.1) . 2026.09.27 16:43:30 - DNS IPv6 of a network adapter forced (Ethernet, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:43:30 - Routes, add 0.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:43:30 - Routes, add 128.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:43:30 - Routes, add ::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:43:30 - Routes, add 8000::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:43:30 - Routes, add 198.44.133.99/32 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:43:31 - Routes, add 2607:9000:7000:31:b9a5:25fa:cb5:227a/128 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:43:31 - Flushing DNS I 2026.09.27 16:43:31 - Checking route IPv4 . 2026.09.27 16:43:37 - Checking route (4° try) . 2026.09.27 16:43:41 - Checking route (5° try) E 2026.09.27 16:43:51 - Checking route IPv4 failed, last reason: Fetch url error:Timeout was reached ! 2026.09.27 16:43:51 - Disconnecting . 2026.09.27 16:43:51 - WireGuard > Stop request received . 2026.09.27 16:43:51 - WireGuard > Stopping . 2026.09.27 16:43:51 - WireGuard > Completed . 2026.09.27 16:43:52 - Routes, delete 2607:9000:7000:31:2f0:97c2:7575:e9e3/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:43:52 - Routes, delete 198.44.133.99/32 for interface "{3B2AEF08-0FB2-4019-8BC1-633C48D363A5}", not present. . 2026.09.27 16:43:52 - Routes, delete 2607:9000:7000:31:b9a5:25fa:cb5:227a/128 for interface "{3B2AEF08-0FB2-4019-8BC1-633C48D363A5}", not present. . 2026.09.27 16:43:52 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:43:52 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:43:52 - DNS IPv4 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:43:52 - DNS IPv6 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:43:52 - DNS IPv4 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:43:52 - DNS IPv6 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:43:52 - DNS leak protection with packet filtering disabled. . 2026.09.27 16:43:52 - Collect network information . 2026.09.27 16:43:52 - Connection terminated. I 2026.09.27 16:43:55 - Checking authorization ... ! 2026.09.27 16:43:56 - Connecting to Khambalia (United States of America, Phoenix, Arizona) . 2026.09.27 16:43:56 - Routes, add 2607:9000:7000:33:3ddb:c857:8df5:50d5/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:43:56 - WireGuard > Setup start . 2026.09.27 16:43:56 - WireGuard > Setup complete . 2026.09.27 16:43:56 - WireGuard > Setup interface . 2026.09.27 16:43:56 - WireGuard > Received first handshake . 2026.09.27 16:43:56 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2026.09.27 16:43:56 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2026.09.27 16:43:57 - DNS leak protection with packet filtering enabled. . 2026.09.27 16:43:57 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.128.0.1) . 2026.09.27 16:43:57 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:43:57 - DNS IPv4 of a network adapter forced (Eddie 1, from automatic to 10.128.0.1) . 2026.09.27 16:43:57 - DNS IPv6 of a network adapter forced (Eddie 1, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:43:57 - DNS IPv4 of a network adapter forced (Ethernet, from automatic to 10.128.0.1) . 2026.09.27 16:43:57 - DNS IPv6 of a network adapter forced (Ethernet, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:43:57 - Routes, add 0.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:43:57 - Routes, add 128.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:43:57 - Routes, add ::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:43:57 - Routes, add 8000::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:43:57 - Routes, add 198.44.133.131/32 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:43:58 - Routes, add 2607:9000:7000:33:c584:3a6a:cbdd:1c1e/128 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:43:58 - Flushing DNS I 2026.09.27 16:43:58 - Checking route IPv4 . 2026.09.27 16:44:04 - Checking route (4° try) . 2026.09.27 16:44:08 - Checking route (5° try) E 2026.09.27 16:44:18 - Checking route IPv4 failed, last reason: Fetch url error:Timeout was reached ! 2026.09.27 16:44:18 - Disconnecting . 2026.09.27 16:44:18 - WireGuard > Stop request received . 2026.09.27 16:44:18 - WireGuard > Stopping . 2026.09.27 16:44:18 - WireGuard > Completed . 2026.09.27 16:44:19 - Routes, delete 2607:9000:7000:33:3ddb:c857:8df5:50d5/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:44:19 - Routes, delete 198.44.133.131/32 for interface "{D22E6917-84D3-47D0-A745-8825A53B3B09}", not present. . 2026.09.27 16:44:19 - Routes, delete 2607:9000:7000:33:c584:3a6a:cbdd:1c1e/128 for interface "{D22E6917-84D3-47D0-A745-8825A53B3B09}", not present. . 2026.09.27 16:44:19 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:44:19 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:44:19 - DNS IPv4 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:44:19 - DNS IPv6 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:44:19 - DNS IPv4 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:44:19 - DNS IPv6 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:44:19 - DNS leak protection with packet filtering disabled. . 2026.09.27 16:44:19 - Collect network information . 2026.09.27 16:44:19 - Connection terminated. I 2026.09.27 16:44:22 - Checking authorization ... ! 2026.09.27 16:44:23 - Connecting to Sheratan (United States of America, Phoenix, Arizona) . 2026.09.27 16:44:23 - Routes, add 2607:9000:7000:32:b66b:bf09:93cd:a633/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:44:23 - WireGuard > Setup start . 2026.09.27 16:44:23 - WireGuard > Setup complete . 2026.09.27 16:44:23 - WireGuard > Setup interface . 2026.09.27 16:44:23 - WireGuard > Received first handshake . 2026.09.27 16:44:23 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2026.09.27 16:44:23 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2026.09.27 16:44:23 - DNS leak protection with packet filtering enabled. . 2026.09.27 16:44:24 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.128.0.1) . 2026.09.27 16:44:24 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:44:24 - DNS IPv4 of a network adapter forced (Eddie 1, from automatic to 10.128.0.1) . 2026.09.27 16:44:24 - DNS IPv6 of a network adapter forced (Eddie 1, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:44:24 - DNS IPv4 of a network adapter forced (Ethernet, from automatic to 10.128.0.1) . 2026.09.27 16:44:24 - DNS IPv6 of a network adapter forced (Ethernet, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:44:24 - Routes, add 0.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:44:24 - Routes, add 128.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:44:24 - Routes, add ::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:44:24 - Routes, add 8000::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:44:24 - Routes, add 198.44.133.115/32 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:44:25 - Routes, add 2607:9000:7000:32:5248:3348:fc1f:3a46/128 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:44:25 - Flushing DNS I 2026.09.27 16:44:25 - Checking route IPv4 . 2026.09.27 16:44:31 - Checking route (4° try) . 2026.09.27 16:44:35 - Checking route (5° try) E 2026.09.27 16:44:45 - Checking route IPv4 failed, last reason: Fetch url error:Timeout was reached ! 2026.09.27 16:44:45 - Disconnecting . 2026.09.27 16:44:45 - WireGuard > Stop request received . 2026.09.27 16:44:45 - WireGuard > Stopping . 2026.09.27 16:44:45 - WireGuard > Completed . 2026.09.27 16:44:45 - Routes, delete 2607:9000:7000:32:b66b:bf09:93cd:a633/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:44:46 - Routes, delete 198.44.133.115/32 for interface "{4BD5BF91-6786-4AFE-A951-B3D7396DAEDD}", not present. . 2026.09.27 16:44:46 - Routes, delete 2607:9000:7000:32:5248:3348:fc1f:3a46/128 for interface "{4BD5BF91-6786-4AFE-A951-B3D7396DAEDD}", not present. . 2026.09.27 16:44:46 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:44:46 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:44:46 - DNS IPv4 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:44:46 - DNS IPv6 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:44:46 - DNS IPv4 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:44:46 - DNS IPv6 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:44:46 - DNS leak protection with packet filtering disabled. . 2026.09.27 16:44:46 - Collect network information . 2026.09.27 16:44:46 - Connection terminated. I 2026.09.27 16:44:49 - Checking authorization ... ! 2026.09.27 16:44:50 - Connecting to Flegetonte (United States of America, Los Angeles) . 2026.09.27 16:44:50 - Routes, add 2607:9000:300:40:15b8:eede:d932:4512/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:44:50 - WireGuard > Setup start . 2026.09.27 16:44:50 - WireGuard > Setup complete . 2026.09.27 16:44:50 - WireGuard > Setup interface . 2026.09.27 16:44:50 - WireGuard > Received first handshake . 2026.09.27 16:44:50 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2026.09.27 16:44:50 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2026.09.27 16:44:51 - DNS leak protection with packet filtering enabled. . 2026.09.27 16:44:51 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.128.0.1) . 2026.09.27 16:44:51 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:44:51 - DNS IPv4 of a network adapter forced (Eddie 1, from automatic to 10.128.0.1) . 2026.09.27 16:44:51 - DNS IPv6 of a network adapter forced (Eddie 1, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:44:51 - DNS IPv4 of a network adapter forced (Ethernet, from automatic to 10.128.0.1) . 2026.09.27 16:44:51 - DNS IPv6 of a network adapter forced (Ethernet, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:44:51 - Routes, add 0.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:44:51 - Routes, add 128.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:44:51 - Routes, add ::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:44:51 - Routes, add 8000::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:44:52 - Routes, add 198.44.129.3/32 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:44:52 - Routes, add 2607:9000:300:40:a601:8c52:4a02:f723/128 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:44:52 - Flushing DNS I 2026.09.27 16:44:52 - Checking route IPv4 . 2026.09.27 16:44:58 - Checking route (4° try) . 2026.09.27 16:45:02 - Checking route (5° try) E 2026.09.27 16:45:12 - Checking route IPv4 failed, last reason: Fetch url error:Timeout was reached ! 2026.09.27 16:45:12 - Disconnecting . 2026.09.27 16:45:12 - WireGuard > Stop request received . 2026.09.27 16:45:12 - WireGuard > Stopping . 2026.09.27 16:45:12 - WireGuard > Completed . 2026.09.27 16:45:13 - Routes, delete 2607:9000:300:40:15b8:eede:d932:4512/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:45:13 - Routes, delete 198.44.129.3/32 for interface "{1003DCAF-7B74-4705-A187-71363E399A0E}", not present. . 2026.09.27 16:45:13 - Routes, delete 2607:9000:300:40:a601:8c52:4a02:f723/128 for interface "{1003DCAF-7B74-4705-A187-71363E399A0E}", not present. . 2026.09.27 16:45:13 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:45:13 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:45:13 - DNS IPv4 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:45:13 - DNS IPv6 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:45:13 - DNS IPv4 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:45:13 - DNS IPv6 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:45:13 - DNS leak protection with packet filtering disabled. . 2026.09.27 16:45:13 - Collect network information . 2026.09.27 16:45:13 - Connection terminated. I 2026.09.27 16:45:15 - Cancel requested. . 2026.09.27 16:45:15 - Deactivation of Network Lock ! 2026.09.27 16:45:15 - Session terminated. ! 2026.09.27 16:45:23 - Activation of Network Lock - Windows Filtering Platform I 2026.09.27 16:45:36 - Session starting. I 2026.09.27 16:45:36 - Checking authorization ... ! 2026.09.27 16:45:37 - Connecting to Sarin (United States of America, Los Angeles) . 2026.09.27 16:45:37 - Routes, add 2607:9000:3000:33:415c:3f0f:c0db:65ee/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:45:37 - WireGuard > Setup start . 2026.09.27 16:45:37 - WireGuard > Setup complete . 2026.09.27 16:45:37 - WireGuard > Setup interface . 2026.09.27 16:45:42 - WireGuard > Received first handshake . 2026.09.27 16:45:42 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2026.09.27 16:45:42 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2026.09.27 16:45:42 - DNS leak protection with packet filtering enabled. . 2026.09.27 16:45:43 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.128.0.1) . 2026.09.27 16:45:43 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:45:43 - DNS IPv4 of a network adapter forced (Eddie 1, from automatic to 10.128.0.1) . 2026.09.27 16:45:43 - DNS IPv6 of a network adapter forced (Eddie 1, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:45:43 - DNS IPv4 of a network adapter forced (Ethernet, from automatic to 10.128.0.1) . 2026.09.27 16:45:43 - DNS IPv6 of a network adapter forced (Ethernet, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:45:43 - Routes, add 0.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:45:43 - Routes, add 128.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:45:43 - Routes, add ::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:45:43 - Routes, add 8000::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:45:43 - Routes, add 198.44.129.227/32 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:45:44 - Routes, add 2607:9000:3000:33:2c22:7641:7f49:8887/128 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:45:44 - Flushing DNS . 2026.09.27 16:45:44 - Collect network information ! 2026.09.27 16:45:44 - Connected. ! 2026.09.27 16:46:20 - Disconnecting . 2026.09.27 16:46:20 - WireGuard > Stop request received . 2026.09.27 16:46:20 - WireGuard > Stopping . 2026.09.27 16:46:20 - WireGuard > Completed . 2026.09.27 16:46:20 - Routes, delete 2607:9000:3000:33:415c:3f0f:c0db:65ee/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:46:20 - Routes, delete 198.44.129.227/32 for interface "{A6A87010-F6E4-42C3-AA90-C1B5E8DB1075}", not present. . 2026.09.27 16:46:21 - Routes, delete 2607:9000:3000:33:2c22:7641:7f49:8887/128 for interface "{A6A87010-F6E4-42C3-AA90-C1B5E8DB1075}", not present. . 2026.09.27 16:46:21 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:46:21 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:46:21 - DNS IPv4 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:46:21 - DNS IPv6 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:46:21 - DNS IPv4 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:46:21 - DNS IPv6 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:46:21 - DNS leak protection with packet filtering disabled. . 2026.09.27 16:46:21 - Collect network information . 2026.09.27 16:46:21 - Connection terminated. . 2026.09.27 16:46:21 - Flushing DNS ! 2026.09.27 16:46:21 - Session terminated. ! 2026.09.27 16:46:23 - Deactivation of Network Lock I 2026.09.27 16:47:34 - Session starting. . 2026.09.27 16:47:34 - Activation of Network Lock - Windows Filtering Platform I 2026.09.27 16:47:34 - Checking authorization ... . 2026.09.27 16:47:35 - Collect network information . 2026.09.27 16:47:35 - Created new ovpn-dco network interface "Eddie" . 2026.09.27 16:47:35 - Collect network information . 2026.09.27 16:47:36 - Using ovpn-dco network interface "Eddie (OpenVPN Data Channel Offload)" ! 2026.09.27 16:47:36 - Connecting to Sarin (United States of America, Los Angeles) . 2026.09.27 16:47:36 - Routes, add 2607:9000:3000:33:415c:3f0f:c0db:65ee/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:47:36 - OpenVPN > OpenVPN 2.7.3 [git:v2.7.3/6ad8be3f36997a25] Windows [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] [DCO] built on Apr 27 2026 . 2026.09.27 16:47:36 - OpenVPN > Windows version: 10.0.26200,amd64 . 2026.09.27 16:47:36 - OpenVPN > library versions: OpenSSL 3.6.2 7 Apr 2026, LZO 2.10 . 2026.09.27 16:47:36 - OpenVPN > DCO version: 2.8.2 . 2026.09.27 16:47:36 - OpenVPN > TCP/UDP: Preserving recently used remote address: [AF_INET6]2607:9000:3000:33:415c:3f0f:c0db:65ee:443 . 2026.09.27 16:47:36 - OpenVPN > TCPv6_CLIENT link local: (not bound) . 2026.09.27 16:47:36 - OpenVPN > TCPv6_CLIENT link remote: [AF_INET6]2607:9000:3000:33:415c:3f0f:c0db:65ee:443 . 2026.09.27 16:47:36 - OpenVPN > TLS: Initial packet from [AF_INET6]2607:9000:3000:33:415c:3f0f:c0db:65ee:443, sid=019ad558 989a66a4 . 2026.09.27 16:47:36 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org . 2026.09.27 16:47:36 - OpenVPN > VERIFY KU OK . 2026.09.27 16:47:36 - OpenVPN > Validating certificate extended key usage . 2026.09.27 16:47:36 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication . 2026.09.27 16:47:36 - OpenVPN > VERIFY EKU OK . 2026.09.27 16:47:36 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Sarin, emailAddress=info@airvpn.org . 2026.09.27 16:47:36 - OpenVPN > Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, peer certificate: 4096 bits RSA, signature: RSA-SHA512, peer signing digest/type: rsa_pss_rsae_sha256 RSASSA-PSS, key agreement: X25519MLKEM768 . 2026.09.27 16:47:36 - OpenVPN > [Sarin] Peer Connection Initiated with [AF_INET6]2607:9000:3000:33:415c:3f0f:c0db:65ee:443 . 2026.09.27 16:47:36 - OpenVPN > TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1 . 2026.09.27 16:47:36 - OpenVPN > TLS: tls_multi_process: initial untrusted session promoted to trusted . 2026.09.27 16:47:37 - OpenVPN > SENT CONTROL [Sarin]: 'PUSH_REQUEST' (status=1) . 2026.09.27 16:47:37 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.17.15.1,dhcp-option DNS6 fde6:7a:7d20:d0f::1,tun-ipv6,route-gateway 10.17.15.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:7d20:d0f::1010/64 fde6:7a:7d20:d0f::1,ifconfig 10.17.15.18 255.255.255.0,peer-id 1,cipher AES-256-GCM,protocol-flags cc-exit tls-ekm dyn-tls-crypt,tun-mtu 1500' . 2026.09.27 16:47:37 - OpenVPN > Pushed option removed by filter: 'redirect-gateway ipv6 def1 bypass-dhcp' . 2026.09.27 16:47:37 - OpenVPN > Pushed option removed by filter: 'dhcp-option DNS 10.17.15.1' . 2026.09.27 16:47:37 - OpenVPN > Pushed option removed by filter: 'dhcp-option DNS6 fde6:7a:7d20:d0f::1' . 2026.09.27 16:47:37 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified . 2026.09.27 16:47:37 - OpenVPN > OPTIONS IMPORT: route-related options modified . 2026.09.27 16:47:37 - OpenVPN > OPTIONS IMPORT: tun-mtu set to 1500 . 2026.09.27 16:47:37 - OpenVPN > interactive service msg_channel=0 . 2026.09.27 16:47:37 - OpenVPN > ovpn-dco device [Eddie] opened . 2026.09.27 16:47:37 - OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address 43 static 10.17.15.18 255.255.255.0 store=active . 2026.09.27 16:47:37 - OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ip delete dns 43 all . 2026.09.27 16:47:37 - OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ip delete wins 43 all . 2026.09.27 16:47:37 - OpenVPN > IPv4 MTU set to 1500 on interface 43 using SetIpInterfaceEntry() . 2026.09.27 16:47:37 - OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ipv6 set address 43 fde6:7a:7d20:d0f::1010/128 store=active . 2026.09.27 16:47:37 - OpenVPN > add_route_ipv6(fde6:7a:7d20:d0f::/64 -> fde6:7a:7d20:d0f::1010 metric 0) IF 43 . 2026.09.27 16:47:37 - OpenVPN > IPv6 route added using ipapi . 2026.09.27 16:47:37 - OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ipv6 delete dns 43 all . 2026.09.27 16:47:37 - OpenVPN > IPv6 MTU set to 1500 on interface 43 using SetIpInterfaceEntry() . 2026.09.27 16:47:37 - OpenVPN > Initialization Sequence Completed . 2026.09.27 16:47:37 - OpenVPN > Data Channel: cipher 'AES-256-GCM', peer-id: 1 . 2026.09.27 16:47:37 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2026.09.27 16:47:37 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2026.09.27 16:47:37 - DNS leak protection with packet filtering enabled. . 2026.09.27 16:47:38 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.17.15.1) . 2026.09.27 16:47:38 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fde6:7a:7d20:d0f::1) . 2026.09.27 16:47:38 - DNS IPv4 of a network adapter forced (Eddie 1, from automatic to 10.17.15.1) . 2026.09.27 16:47:38 - DNS IPv6 of a network adapter forced (Eddie 1, from automatic to fde6:7a:7d20:d0f::1) . 2026.09.27 16:47:38 - DNS IPv4 of a network adapter forced (Ethernet, from automatic to 10.17.15.1) . 2026.09.27 16:47:38 - DNS IPv6 of a network adapter forced (Ethernet, from automatic to fde6:7a:7d20:d0f::1) . 2026.09.27 16:47:38 - Routes, add 0.0.0.0/1 for interface "Eddie (OpenVPN Data Channel Offload)", already exists. . 2026.09.27 16:47:38 - Routes, add 128.0.0.0/1 for interface "Eddie (OpenVPN Data Channel Offload)", already exists. . 2026.09.27 16:47:38 - Routes, add ::/1 for interface "Eddie (OpenVPN Data Channel Offload)", already exists. . 2026.09.27 16:47:38 - Routes, add 8000::/1 for interface "Eddie (OpenVPN Data Channel Offload)", already exists. . 2026.09.27 16:47:38 - Routes, add 198.44.129.227/32 for interface "Eddie (OpenVPN Data Channel Offload)". . 2026.09.27 16:47:39 - Routes, add 2607:9000:3000:33:2c22:7641:7f49:8887/128 for interface "Eddie (OpenVPN Data Channel Offload)". . 2026.09.27 16:47:39 - Flushing DNS I 2026.09.27 16:47:39 - Checking route IPv4 I 2026.09.27 16:47:42 - Checking route IPv6 I 2026.09.27 16:47:42 - Checking DNS . 2026.09.27 16:47:43 - Collect network information ! 2026.09.27 16:47:43 - Connected. . 2026.09.27 16:47:43 - OpenVPN > Timers: ping 10, ping-restart 60 . 2026.09.27 16:47:43 - OpenVPN > Protocol options: protocol-flags cc-exit tls-ekm dyn-tls-crypt ! 2026.09.27 16:48:19 - Disconnecting . 2026.09.27 16:48:19 - Sending soft termination signal . 2026.09.27 16:48:22 - OpenVPN > Closing ovpn-dco interface . 2026.09.27 16:48:22 - OpenVPN > delete_route_ipv6(fde6:7a:7d20:d0f::/64) . 2026.09.27 16:48:22 - OpenVPN > IPv6 route deleted using ipapi . 2026.09.27 16:48:22 - OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ipv6 delete address 43 fde6:7a:7d20:d0f::1010 store=active . 2026.09.27 16:48:22 - OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ipv4 delete address 43 10.17.15.18 store=active . 2026.09.27 16:48:22 - OpenVPN > SIGTERM[hard,] received, process exiting . 2026.09.27 16:48:23 - Routes, delete 2607:9000:3000:33:415c:3f0f:c0db:65ee/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:48:23 - Routes, delete 198.44.129.227/32 for interface "Eddie (OpenVPN Data Channel Offload)". . 2026.09.27 16:48:24 - Routes, delete 2607:9000:3000:33:2c22:7641:7f49:8887/128 for interface "Eddie (OpenVPN Data Channel Offload)". . 2026.09.27 16:48:24 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:48:24 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:48:24 - DNS IPv4 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:48:24 - DNS IPv6 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:48:24 - DNS IPv4 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:48:24 - DNS IPv6 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:48:24 - DNS leak protection with packet filtering disabled. . 2026.09.27 16:48:24 - Interface Eddie metric restored from 3 to Automatic, layer IPv4 . 2026.09.27 16:48:24 - Interface Eddie metric restored from 3 to Automatic, layer IPv6 . 2026.09.27 16:48:24 - Collect network information . 2026.09.27 16:48:24 - Connection terminated. . 2026.09.27 16:48:24 - Flushing DNS . 2026.09.27 16:48:24 - Deactivation of Network Lock ! 2026.09.27 16:48:24 - Session terminated. I 2026.09.27 16:52:33 - Session starting. . 2026.09.27 16:52:34 - Activation of Network Lock - Windows Filtering Platform I 2026.09.27 16:52:34 - Checking authorization ... ! 2026.09.27 16:52:34 - Connecting to Maia (United States of America, Los Angeles) . 2026.09.27 16:52:34 - Routes, add 2607:9000:3000:32:5ca5:68a0:c556:395c/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:52:35 - WireGuard > Setup start . 2026.09.27 16:52:35 - WireGuard > Setup complete . 2026.09.27 16:52:35 - WireGuard > Setup interface . 2026.09.27 16:52:35 - WireGuard > Received first handshake . 2026.09.27 16:52:35 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2026.09.27 16:52:35 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2026.09.27 16:52:35 - DNS leak protection with packet filtering enabled. . 2026.09.27 16:52:35 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.128.0.1) . 2026.09.27 16:52:35 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:52:35 - DNS IPv4 of a network adapter forced (Eddie 1, from automatic to 10.128.0.1) . 2026.09.27 16:52:35 - DNS IPv6 of a network adapter forced (Eddie 1, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:52:35 - DNS IPv4 of a network adapter forced (Ethernet, from automatic to 10.128.0.1) . 2026.09.27 16:52:35 - DNS IPv6 of a network adapter forced (Ethernet, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:52:35 - Routes, add 0.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:52:35 - Routes, add 128.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:52:36 - Routes, add ::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:52:36 - Routes, add 8000::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:52:36 - Routes, add 198.44.129.211/32 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:52:36 - Routes, add 2607:9000:3000:32:4d59:f15d:aa0b:e9e/128 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:52:36 - Flushing DNS I 2026.09.27 16:52:36 - Checking route IPv4 . 2026.09.27 16:52:42 - Checking route (4° try) . 2026.09.27 16:52:46 - Checking route (5° try) E 2026.09.27 16:52:56 - Checking route IPv4 failed, last reason: Fetch url error:Timeout was reached ! 2026.09.27 16:52:56 - Disconnecting . 2026.09.27 16:52:56 - WireGuard > Stop request received . 2026.09.27 16:52:56 - WireGuard > Stopping . 2026.09.27 16:52:56 - WireGuard > Completed . 2026.09.27 16:52:57 - Routes, delete 2607:9000:3000:32:5ca5:68a0:c556:395c/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:52:57 - Routes, delete 198.44.129.211/32 for interface "{E83CAFE2-5284-42F4-8C93-D6C5D38732E8}", not present. . 2026.09.27 16:52:57 - Routes, delete 2607:9000:3000:32:4d59:f15d:aa0b:e9e/128 for interface "{E83CAFE2-5284-42F4-8C93-D6C5D38732E8}", not present. . 2026.09.27 16:52:57 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:52:57 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:52:57 - DNS IPv4 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:52:57 - DNS IPv6 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:52:57 - DNS IPv4 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:52:58 - DNS IPv6 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:52:58 - DNS leak protection with packet filtering disabled. . 2026.09.27 16:52:58 - Collect network information . 2026.09.27 16:52:58 - Connection terminated. I 2026.09.27 16:53:01 - Cancel requested. . 2026.09.27 16:53:01 - Deactivation of Network Lock ! 2026.09.27 16:53:01 - Session terminated. I 2026.09.27 16:53:18 - Session starting. . 2026.09.27 16:53:18 - Activation of Network Lock - Windows Filtering Platform I 2026.09.27 16:53:18 - Checking authorization ... ! 2026.09.27 16:53:19 - Connecting to Sarin (United States of America, Los Angeles) . 2026.09.27 16:53:19 - Routes, add 2607:9000:3000:33:415c:3f0f:c0db:65ee/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:53:19 - WireGuard > Setup start . 2026.09.27 16:53:19 - WireGuard > Setup complete . 2026.09.27 16:53:19 - WireGuard > Setup interface . 2026.09.27 16:53:19 - WireGuard > Received first handshake . 2026.09.27 16:53:19 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2026.09.27 16:53:19 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2026.09.27 16:53:19 - DNS leak protection with packet filtering enabled. . 2026.09.27 16:53:19 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.128.0.1) . 2026.09.27 16:53:19 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:53:19 - DNS IPv4 of a network adapter forced (Eddie 1, from automatic to 10.128.0.1) . 2026.09.27 16:53:19 - DNS IPv6 of a network adapter forced (Eddie 1, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:53:20 - DNS IPv4 of a network adapter forced (Ethernet, from automatic to 10.128.0.1) . 2026.09.27 16:53:20 - DNS IPv6 of a network adapter forced (Ethernet, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:53:20 - Routes, add 0.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:53:20 - Routes, add 128.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:53:20 - Routes, add ::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:53:20 - Routes, add 8000::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:53:20 - Routes, add 198.44.129.227/32 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:53:20 - Routes, add 2607:9000:3000:33:2c22:7641:7f49:8887/128 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:53:20 - Flushing DNS I 2026.09.27 16:53:20 - Checking route IPv4 . 2026.09.27 16:53:26 - Checking route (4° try) . 2026.09.27 16:53:30 - Checking route (5° try) ! 2026.09.27 16:53:40 - Disconnecting . 2026.09.27 16:53:41 - WireGuard > Stop request received . 2026.09.27 16:53:41 - WireGuard > Stopping . 2026.09.27 16:53:41 - WireGuard > Completed . 2026.09.27 16:53:41 - Routes, delete 2607:9000:3000:33:415c:3f0f:c0db:65ee/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:53:41 - Routes, delete 198.44.129.227/32 for interface "{EAF2B080-2D07-4E18-87C3-5A9B7BD57071}", not present. . 2026.09.27 16:53:41 - Routes, delete 2607:9000:3000:33:2c22:7641:7f49:8887/128 for interface "{EAF2B080-2D07-4E18-87C3-5A9B7BD57071}", not present. . 2026.09.27 16:53:41 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:53:42 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:53:42 - DNS IPv4 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:53:42 - DNS IPv6 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:53:42 - DNS IPv4 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:53:42 - DNS IPv6 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:53:42 - DNS leak protection with packet filtering disabled. . 2026.09.27 16:53:42 - Collect network information . 2026.09.27 16:53:42 - Connection terminated. I 2026.09.27 16:53:42 - Cancel requested. . 2026.09.27 16:53:42 - Deactivation of Network Lock ! 2026.09.27 16:53:42 - Session terminated. I 2026.09.27 16:54:20 - Session starting. . 2026.09.27 16:54:20 - Activation of Network Lock - Windows Filtering Platform I 2026.09.27 16:54:21 - Checking authorization ... ! 2026.09.27 16:54:21 - Connecting to Sarin (United States of America, Los Angeles) . 2026.09.27 16:54:22 - Routes, add 2607:9000:3000:33:415c:3f0f:c0db:65ee/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:54:22 - WireGuard > Setup start . 2026.09.27 16:54:22 - WireGuard > Setup complete . 2026.09.27 16:54:22 - WireGuard > Setup interface . 2026.09.27 16:54:22 - WireGuard > Received first handshake . 2026.09.27 16:54:22 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2026.09.27 16:54:22 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2026.09.27 16:54:22 - DNS leak protection with packet filtering enabled. . 2026.09.27 16:54:22 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.128.0.1) . 2026.09.27 16:54:22 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:54:22 - DNS IPv4 of a network adapter forced (Eddie 1, from automatic to 10.128.0.1) . 2026.09.27 16:54:22 - DNS IPv6 of a network adapter forced (Eddie 1, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:54:22 - DNS IPv4 of a network adapter forced (Ethernet, from automatic to 10.128.0.1) . 2026.09.27 16:54:22 - DNS IPv6 of a network adapter forced (Ethernet, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:54:23 - Routes, add 0.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:54:23 - Routes, add 128.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:54:23 - Routes, add ::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:54:23 - Routes, add 8000::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:54:23 - Routes, add 198.44.129.227/32 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:54:23 - Routes, add 2607:9000:3000:33:2c22:7641:7f49:8887/128 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:54:23 - Flushing DNS I 2026.09.27 16:54:23 - Checking route IPv4 . 2026.09.27 16:54:29 - Checking route (4° try) . 2026.09.27 16:54:33 - Checking route (5° try) ! 2026.09.27 16:54:43 - Disconnecting . 2026.09.27 16:54:43 - WireGuard > Stop request received . 2026.09.27 16:54:43 - WireGuard > Stopping . 2026.09.27 16:54:44 - WireGuard > Completed . 2026.09.27 16:54:44 - Routes, delete 2607:9000:3000:33:415c:3f0f:c0db:65ee/128 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:54:44 - Routes, delete 198.44.129.227/32 for interface "{34C5C6CF-1E15-44DF-86A0-48FA76515347}", not present. . 2026.09.27 16:54:44 - Routes, delete 2607:9000:3000:33:2c22:7641:7f49:8887/128 for interface "{34C5C6CF-1E15-44DF-86A0-48FA76515347}", not present. . 2026.09.27 16:54:44 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:54:44 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:54:44 - DNS IPv4 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:54:45 - DNS IPv6 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:54:45 - DNS IPv4 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:54:45 - DNS IPv6 of a network adapter restored to original settings (Ethernet, to automatic) . 2026.09.27 16:54:45 - DNS leak protection with packet filtering disabled. . 2026.09.27 16:54:45 - Collect network information . 2026.09.27 16:54:45 - Connection terminated. I 2026.09.27 16:54:45 - Cancel requested. . 2026.09.27 16:54:45 - Deactivation of Network Lock ! 2026.09.27 16:54:45 - Session terminated. I 2026.09.27 16:59:15 - Session starting. . 2026.09.27 16:59:15 - Activation of Network Lock - Windows Filtering Platform I 2026.09.27 16:59:15 - Checking authorization ... ! 2026.09.27 16:59:16 - Connecting to Sarin (United States of America, Los Angeles) . 2026.09.27 16:59:16 - Routes, add 198.54.129.62/32 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:59:16 - WireGuard > Setup start . 2026.09.27 16:59:16 - WireGuard > Setup complete . 2026.09.27 16:59:16 - WireGuard > Setup interface . 2026.09.27 16:59:16 - WireGuard > Received first handshake . 2026.09.27 16:59:17 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2026.09.27 16:59:17 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2026.09.27 16:59:17 - DNS leak protection with packet filtering enabled. . 2026.09.27 16:59:17 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.128.0.1) . 2026.09.27 16:59:17 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:59:17 - DNS IPv4 of a network adapter forced (Eddie 1, from automatic to 10.128.0.1) . 2026.09.27 16:59:17 - DNS IPv6 of a network adapter forced (Eddie 1, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:59:17 - Routes, add 0.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:59:17 - Routes, add 128.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:59:17 - Routes, add ::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:59:17 - Routes, add 8000::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:59:17 - Routes, add 198.44.129.227/32 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:59:18 - Routes, add 2607:9000:3000:33:2c22:7641:7f49:8887/128 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:59:18 - Flushing DNS I 2026.09.27 16:59:18 - Checking route IPv4 . 2026.09.27 16:59:24 - Checking route (4° try) . 2026.09.27 16:59:28 - Checking route (5° try) E 2026.09.27 16:59:38 - Checking route IPv4 failed, last reason: Fetch url error:Timeout was reached ! 2026.09.27 16:59:38 - Disconnecting . 2026.09.27 16:59:38 - WireGuard > Stop request received . 2026.09.27 16:59:38 - WireGuard > Stopping . 2026.09.27 16:59:38 - WireGuard > Completed . 2026.09.27 16:59:39 - Routes, delete 198.54.129.62/32 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:59:39 - Routes, delete 198.44.129.227/32 for interface "{B3E51A89-B6D9-486C-ACB2-64ECBC165041}", not present. . 2026.09.27 16:59:39 - Routes, delete 2607:9000:3000:33:2c22:7641:7f49:8887/128 for interface "{B3E51A89-B6D9-486C-ACB2-64ECBC165041}", not present. . 2026.09.27 16:59:39 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:59:39 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 16:59:39 - DNS IPv4 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:59:39 - DNS IPv6 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 16:59:39 - DNS leak protection with packet filtering disabled. . 2026.09.27 16:59:39 - Collect network information . 2026.09.27 16:59:39 - Connection terminated. I 2026.09.27 16:59:42 - Checking authorization ... ! 2026.09.27 16:59:43 - Connecting to Xamidimura (United States of America, Los Angeles) . 2026.09.27 16:59:43 - Routes, add 198.54.129.46/32 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 16:59:43 - WireGuard > Setup start . 2026.09.27 16:59:43 - WireGuard > Setup complete . 2026.09.27 16:59:43 - WireGuard > Setup interface . 2026.09.27 16:59:43 - WireGuard > Received first handshake . 2026.09.27 16:59:43 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2026.09.27 16:59:43 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2026.09.27 16:59:43 - DNS leak protection with packet filtering enabled. . 2026.09.27 16:59:44 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.128.0.1) . 2026.09.27 16:59:44 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:59:44 - DNS IPv4 of a network adapter forced (Eddie 1, from automatic to 10.128.0.1) . 2026.09.27 16:59:44 - DNS IPv6 of a network adapter forced (Eddie 1, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 16:59:44 - Routes, add 0.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:59:44 - Routes, add 128.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:59:44 - Routes, add ::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:59:44 - Routes, add 8000::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 16:59:44 - Routes, add 198.44.129.195/32 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:59:45 - Routes, add 2607:9000:3000:31:7309:4202:b8b8:7cb8/128 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 16:59:45 - Flushing DNS I 2026.09.27 16:59:45 - Checking route IPv4 . 2026.09.27 16:59:51 - Checking route (4° try) . 2026.09.27 16:59:55 - Checking route (5° try) E 2026.09.27 17:00:05 - Checking route IPv4 failed, last reason: Fetch url error:Timeout was reached ! 2026.09.27 17:00:05 - Disconnecting . 2026.09.27 17:00:05 - WireGuard > Stop request received . 2026.09.27 17:00:05 - WireGuard > Stopping . 2026.09.27 17:00:05 - WireGuard > Completed . 2026.09.27 17:00:06 - Routes, delete 198.54.129.46/32 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 17:00:06 - Routes, delete 198.44.129.195/32 for interface "{3811CA6E-9D4F-46DA-B0A7-C87FFE282281}", not present. . 2026.09.27 17:00:06 - Routes, delete 2607:9000:3000:31:7309:4202:b8b8:7cb8/128 for interface "{3811CA6E-9D4F-46DA-B0A7-C87FFE282281}", not present. . 2026.09.27 17:00:06 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 17:00:06 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 17:00:06 - DNS IPv4 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 17:00:06 - DNS IPv6 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 17:00:06 - DNS leak protection with packet filtering disabled. . 2026.09.27 17:00:06 - Collect network information . 2026.09.27 17:00:06 - Connection terminated. I 2026.09.27 17:00:09 - Checking authorization ... ! 2026.09.27 17:00:10 - Connecting to Revati (United States of America, Los Angeles) . 2026.09.27 17:00:10 - Routes, add 198.54.129.125/32 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 17:00:10 - WireGuard > Setup start . 2026.09.27 17:00:10 - WireGuard > Setup complete . 2026.09.27 17:00:10 - WireGuard > Setup interface . 2026.09.27 17:00:10 - WireGuard > Received first handshake . 2026.09.27 17:00:10 - Interface Eddie metric changed from Automatic to 3, layer IPv4 . 2026.09.27 17:00:10 - Interface Eddie metric changed from Automatic to 3, layer IPv6 . 2026.09.27 17:00:10 - DNS leak protection with packet filtering enabled. . 2026.09.27 17:00:10 - DNS IPv4 of a network adapter forced (Eddie, from automatic to 10.128.0.1) . 2026.09.27 17:00:10 - DNS IPv6 of a network adapter forced (Eddie, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 17:00:11 - DNS IPv4 of a network adapter forced (Eddie 1, from automatic to 10.128.0.1) . 2026.09.27 17:00:11 - DNS IPv6 of a network adapter forced (Eddie 1, from automatic to fd7d:76ee:e68f:a993::1) . 2026.09.27 17:00:11 - Routes, add 0.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 17:00:11 - Routes, add 128.0.0.0/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 17:00:11 - Routes, add ::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 17:00:11 - Routes, add 8000::/1 for interface "Eddie (Eddie Tunnel #2)", already exists. . 2026.09.27 17:00:11 - Routes, add 198.44.129.243/32 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 17:00:11 - Routes, add 2607:9000:3000:38:b26d:18f0:c661:ec18/128 for interface "Eddie (Eddie Tunnel #2)". . 2026.09.27 17:00:11 - Flushing DNS I 2026.09.27 17:00:11 - Checking route IPv4 ! 2026.09.27 17:00:14 - Disconnecting . 2026.09.27 17:00:15 - WireGuard > Stop request received . 2026.09.27 17:00:15 - WireGuard > Stopping . 2026.09.27 17:00:15 - WireGuard > Completed . 2026.09.27 17:00:15 - Routes, delete 198.54.129.125/32 for interface "Ethernet (Realtek Gaming 2.5GbE Family Controller)". . 2026.09.27 17:00:15 - Routes, delete 198.44.129.243/32 for interface "{19627361-D52D-4127-B23D-ECEF947194BC}", not present. . 2026.09.27 17:00:15 - Routes, delete 2607:9000:3000:38:b26d:18f0:c661:ec18/128 for interface "{19627361-D52D-4127-B23D-ECEF947194BC}", not present. . 2026.09.27 17:00:15 - DNS IPv4 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 17:00:15 - DNS IPv6 of a network adapter restored to original settings (Eddie, to automatic) . 2026.09.27 17:00:16 - DNS IPv4 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 17:00:16 - DNS IPv6 of a network adapter restored to original settings (Eddie 1, to automatic) . 2026.09.27 17:00:16 - DNS leak protection with packet filtering disabled. . 2026.09.27 17:00:16 - Collect network information . 2026.09.27 17:00:16 - Connection terminated. I 2026.09.27 17:00:16 - Cancel requested. . 2026.09.27 17:00:16 - Deactivation of Network Lock ! 2026.09.27 17:00:16 - Session terminated. .
-
Thank you for taking the time to review the paper in this much detail. This is exactly the kind of technical criticism I was hoping the publication would generate, and I agree that several parts of v1.0 need to be either narrowed, clarified, or supported with stronger evidence. On the firewall point, you are correct. The failure I observed was in my own persistent nftables configuration used alongside wg-quick; it was not a failure of Eddie or Network Lock. I did clarify that later in the paper, but I agree that it should have been made explicit much earlier, including in the abstract and in the section describing the initial failure. I will correct that in the next revision and make the distinction much more prominent. I also agree with the IPv6 criticism. The successful IPv6 request through airvpn demonstrated working IPv6 connectivity through the VPN, but the direct-interface result of Network is unreachable does not prove that nftables blocked an otherwise viable IPv6 path. The correct conclusion from the existing evidence is that no IPv6 escape was observed in that VMware environment. I plan to add a proper control with a known-working non-VPN IPv6 path so that firewall enforcement can be tested independently of IPv6 availability. The reboot/startup point is also well taken. What I demonstrated was that the expected firewall and WireGuard state existed after reboot and that nftables was ordered before network-pre.target. That is evidence of persistence and service ordering, but not proof that no traffic escaped during the entire shutdown/startup transition. I plan to repeat this with a packet capture taken outside the VM, covering the full reboot, so that any traffic leaving the guest before the VPN becomes available can be observed directly. On DNS, I agree that my wording needs to be more precise. WireGuard itself is not negotiating DNS settings. In this configuration the DNS values are present in the wg-quick profile and are applied locally through the resolver integration. I already have evidence in the boot logs showing wg-quick invoking resolvconf, and I will document exactly how that results in the AirVPN resolver addresses and the ~. route-only domain being associated with the tunnel. I will also make it clear that ~. is part of the resolver-selection logic rather than an unconditional guarantee on its own. The packet captures remain the stronger evidence for the individual DNS queries that were tested. I strongly agree with the reproducibility point. Version 1.0 describes the experiment and includes representative commands, but it does not provide enough underlying material for someone else to independently inspect or reproduce the work. I plan to add a sanitized artifact set to the GitHub repository containing the original and repaired nftables configurations, a sanitized WireGuard profile, software versions, routing tables, resolver state, relevant systemd dependency information, infrastructure lookups, and packet captures where practical. I will also separate ARIN registration, BGP origin, reverse DNS, geolocation, and the AirVPN DNS identity more carefully rather than treating them as interchangeable evidence of infrastructure or physical placement. I also agree with the point about the no-logging conclusion. The absence of a published independent audit should be described as an evidence gap, not as evidence that logging occurs. Likewise, published source code, provider statements, historical reports, and audits all provide different kinds of evidence and should not be treated as equivalent. An audit would itself only establish findings within its defined scope and period, not provide a permanent guarantee. I intend to leave v1.0 intact as the original published record and incorporate these corrections, additional controls, and reproducibility artifacts into a v1.1 release. That way the revision history remains transparent rather than silently changing the original publication. Thank you again for the detailed review. The central goal of the project was to separate what I could directly observe from what I was assuming, and your feedback has identified several places where that distinction can be made substantially stronger.
-
Swiss Servers always disconnects and packet loss?
Gandalf15 replied to Gandalf15's topic in Troubleshooting and Problems
Are there news? The situations does not seem to have changed? -
@Fragmented Sentinel Hello! Thank you for publishing your investigation and explaining the limits of what client-side testing can establish. We agree with the distinction between observing traffic on the client and verifying what happens to data on a provider's servers. Having reviewed version 1.0, we would like to suggest a few clarifications to help readers understand exactly what was tested and what the results establish. 1. Identify the firewall that failed The setup uses wg-quick with a separate persistent nftables ruleset. The reported boot failure concerns that local ruleset; the experiment does not demonstrate a failure of Eddie or Network Lock. Section 10 makes this distinction, but it would help to state it in the abstract and Section 3 as well. For example: "The test VM's custom persistent nftables firewall failed to load at boot." If the origin of those rules is known, please identify it. The comparison with RTINGS should specify the client version, operating system and startup conditions involved. A result from this custom Linux configuration can't confirm or refute the behavior of a different client setup. 2. Separate IPv6 connectivity from IPv6 firewall enforcement The successful IPv6 request through the tunnel demonstrates IPv6 connectivity through AirVPN in the tested configuration. However, "Network unreachable" on the direct-interface test could also mean that the VM had no usable non-VPN IPv6 route. Without a baseline demonstrating a working alternative IPv6 path, the supported conclusion is that no IPv6 escape was observed in this environment. Establishing that the firewall blocked an otherwise viable connection requires that additional control. The VMware NAT configuration is relevant here and should be documented. 3. Distinguish reboot persistence from protection throughout startup Finding the expected rules and service state after reboot supports persistence. It does not, by itself, establish that no traffic escaped during shutdown or startup. The systemd directives also need to be considered together with the complete unit dependencies. network-pre.target is passive and must be pulled into the transaction; the network-management service must participate in the ordering. Ordering alone does not make successful firewall loading a prerequisite for networking. https://systemd.io/NETWORK_ONLINE/ A capture from outside the rebooting VM, covering the whole transition, would provide stronger evidence. This is a limitation of the published evidence, not a finding that the repaired configuration leaks. 4. Identify how DNS settings were applied WireGuard itself does not negotiate or push DNS settings. In a wg-quick setup, those settings are applied locally through the profile and through supporting tools or hooks. Please specify the mechanism that configured systemd-resolved, including the ~. routing domain. https://git.zx2c4.com/wireguard-tools/tree/src/man/wg-quick.8 The ~. domain is also not an unconditional guarantee of exclusive DNS routing through one link: the complete resolver configuration matters. This does not invalidate the capture results for the queries you tested. Ordinary DNS carried inside the encrypted tunnel is not, merely because it is ordinary DNS, a DNS leak. 5. Make the experiment reproducible The reviewed deposit provides the paper and representative commands, but not the underlying artifacts. Sanitized original and repaired firewall rules, the WireGuard profile, software versions, routing and resolver state, service dependencies, and capture records would make independent checking much easier. Capture duration and dropped-packet statistics are useful too. For the infrastructure identification, please include the relevant public-address lookup records. Address registration, BGP origin and a DNS identity string are different kinds of evidence; none alone establishes physical placement. 6. Keep the no-logging conclusion within its evidential scope We agree that these tests cannot establish server-side non-retention, and that the absence of a published audit does not demonstrate logging. Provider statements, published source code, historical reports and operational audits should be assessed separately. Source availability does not prove what is deployed. Historical claims need supporting records. An audit has a defined scope and period rather than establishing a permanent guarantee. The central observation remains useful: after the local firewall was repaired, the reported tests found that the examined configuration carried the tested traffic through the VPN. These clarifications would make the attribution more precise and help others reproduce and extend your work. Kind regards
-
This time, it correctly routed my external IP to gateway 10.0.0.1 instead of 192.168.0.254. I checked the log before I restarted Eddie, and it showed the following for my public IP route, indicating it was trying to route to the proper gateway, but you can see from the route prints I copied above that it didn't. Routes, add 69.69.69.69/32 for interface "Ethernet (Intel(R) Ethernet Connection (2) I219-LM)". I'll keep an eye on it and comment again if it happens again.
-
Yes. No concern. Choose Specs in the sub-menu of the Home tab.
-
Just found out about this forum and AirVPN. Up until now I was using Shieldway for my VPN needs, mostly because they have the WireGuard protocol, which offers extra speed and security. So, I have got to question this, does AirVPN support the WireGuard protocol, like Shieldway or not?
-
-
I recently watched NetworkChuck’s video discussing what a VPN actually hides and, in particular, the idea that using a VPN shifts trust from the ISP to the VPN provider. I use AirVPN, so rather than treating that as a theoretical discussion, I decided to test my own setup and document what I could actually verify. The result turned into a fairly extensive lab exercise and eventually a short technical paper. My test environment was an Ubuntu VM using a manually configured AirVPN WireGuard connection rather than Eddie. I inspected Linux policy routing, captured traffic on both the physical and WireGuard interfaces, tested DNS behaviour, deliberately attempted IPv4 and IPv6 bypasses, forced applications to use the physical interface, tested hard-coded external DNS, stopped the VPN to test failure behaviour, and finally rebooted the VM to verify firewall ordering and persistence. One of the most useful findings actually had nothing to do with an AirVPN failure. My own custom nftables kill switch was broken. I had created a persistent nftables ruleset, but it used interface references that required the airvpn interface to exist when the firewall loaded. At boot, nftables started before WireGuard created that interface, so the firewall service failed. When I stopped WireGuard during testing, the VM silently fell back to its normal VMware NAT route and regained direct Internet access. That was a good reminder that having a security configuration present is not the same as demonstrating that it is operating. I corrected the ruleset to allow it to load before the WireGuard interface exists and then repeated the testing. After the repair, I tested: - IPv4 and IPv6 default routing through AirVPN - DNS visibility inside and outside the WireGuard tunnel - direct queries to the VMware/local DNS resolver - hard-coded DNS to 1.1.1.1 - applications explicitly binding to the physical interface - forced IPv4 and IPv6 escape attempts - WireGuard-down behaviour - reboot persistence - nftables/WireGuard boot ordering The hardened configuration failed closed as intended. The packet captures were particularly interesting. On the AirVPN interface I could plainly see normal DNS queries going to AirVPN’s internal resolver. On the VM’s physical interface, the same activity appeared only as encrypted UDP traffic to the AirVPN WireGuard endpoint. I could not see the individual DNS queries or direct connections to the websites being accessed. A hard-coded query to 1.1.1.1 also behaved as expected: it bypassed AirVPN’s DNS resolver, but did not bypass AirVPN itself. The DNS request still travelled through the WireGuard tunnel. I also queried the AirVPN resolver using CHAOS-class DNS records. version.bind returned "AirVPN DNS" and id.server identified the resolver as: unurgunite.airservers.org The server/network data pointed to the New York Unurgunite infrastructure on tzulo / AS11878. Using Akamai’s whoami.ds.akahelp.net resolver diagnostic, the recursive DNS egress appeared from the same IPv6 /64 as the VPN’s public IPv6 egress, although it was a different address. The response did not include an EDNS Client Subnet value. I also confirmed that the IPv4 WireGuard entry address and the public IPv4 exit address were different. The conclusion I came away with is slightly more precise than simply saying a VPN “hides metadata.” From the local/ISP side, AirVPN successfully hid substantial destination-related metadata. The ISP-side observer could still see the AirVPN endpoint, packet timing, sizes, traffic direction, volume and session duration, but could not directly see the individual DNS queries and destination connections carried inside WireGuard. That brings the investigation back to the trust question. Once traffic reaches the VPN endpoint, AirVPN is necessarily in a privileged network position. HTTPS still protects the application content end-to-end, but the VPN infrastructure is technically positioned to observe destination IPs, AirVPN DNS queries, timing and traffic volume. AirVPN states that it does not retain identifying traffic logs or inspect customer traffic, and a number of the architectural behaviours I could observe were consistent with a privacy-focused design. What I cannot verify externally is the production server-side logging configuration itself. That is the largest remaining evidence gap I identified: I could not find a published independent no-logs/infrastructure audit comparable to those some other VPN providers have commissioned. I would be particularly interested in clarification from AirVPN staff or anyone familiar with the infrastructure on a few points: 1. Does the resolver identified as unurgunite.airservers.org run directly on the same physical VPN host, or is the 10.128.0.1 service presented locally while recursion is handled elsewhere? 2. For the current tzulo New York servers, is the bare-metal hardware AirVPN-owned/colocated, rented dedicated hardware, or another arrangement? 3. Is an independent infrastructure/no-logging audit something AirVPN has considered or plans to pursue? 4. Is my interpretation of the separate entry/exit addressing and DNS architecture accurate, or is there anything important I have misunderstood? I’ve published the complete methodology, evidence, limitations and conclusions here: Paper / DOI: https://doi.org/10.5281/zenodo.22986653 GitHub: https://github.com/Fragmented-Sentinel/what-a-vpn-actually-hides The work is independent and is not affiliated with or sponsored by AirVPN, NetworkChuck, tzulo, or any other organization mentioned in the paper. I’d genuinely welcome technical corrections. The purpose of the exercise was not to prove that AirVPN is “good” or “bad,” but to separate what I could actually verify from what still depends on provider claims and trust.
-
-
do not see anything for windows 7 i wish to keep my old computer everything is expensive right now and i would like to use my computer with win7 until it dies thanks in advance
-
-
Eddie Desktop Edition 2.27 beta released
scooby0786 replied to Staff's topic in News and Announcement
Hola, Just a quick heads-up, as per posts below: And here: This still seems to be a problem on version 2.27.2 on a Windows 11 laptop/PC. Although, my issue isn't as bad as d3adf1sh's. It connects to the server for me after waking from sleep, but sites don't load unless I double click the server from the Eddie UI list and cycle the connection again which fixes the issue. Sometimes, very rarely, it gets stuck on "checking route to ipv4" where I have to completely close Eddie and relaunch. The longer the sleep, the more prevalent of the above issues happening. A short sleep cycle doesn't too often cause any issue when waking the machine. Please address/investigate this issue before releasing a stable version. A clean install with 2.26.2 or 2.27.2 doesn't fix the issue. A minor inconvenience, but an inconvenience nevertheless. Again, I repeat, salivating. Thanks for all the hard work behind the scenes. -
[SOLVED] Network lock protection lost when eddie-ui crashes
Staff replied to zebulon's topic in Eddie - AirVPN Client
Hello! Yes, totally expected, and not an Eddie's fault as explained earlier. It is intentional that when Eddie is shut down gracefully it releases Network Lock (i.e. it restores previous system firewall rules). It remains anyway to be seen how the pm and systemd act on a case by case basis on each distribution: Network Lock should not be relied on to remain active during an Eddie upgrade that stops its privileged service. Your approach of downloading first and installing offline avoids Internet traffic during installation. Please also take care when reconnecting: download the package and any required dependencies beforehand, disconnect the network, and install the update. Then start Eddie and activate Network Lock before restoring network connectivity. Resume sensitive activity only once the VPN connection is established. Kind regards -
[SOLVED] Network lock protection lost when eddie-ui crashes
cheeze replied to zebulon's topic in Eddie - AirVPN Client
Hello Staff, This happens with both linux mint and Mxlinux . It has been happening for at least the past 6 upgrades or spanning a few years. It is not a new or recent event. I run ping after the eddie interface closes, showing I'm still connected to internet, then I run curl ifconfig.me to see my IP, which shows my ISP IP. The only way I can update without leaking my IP is to download the package only, then go offline and install it. Thank you!
