Jump to content
Not connected, Your IP: 216.73.217.33

All Activity

This stream auto-updates     

  1. Past hour
  2. Today
  3. @ExcitingDaydream Hello! "Checking route IPv4", "Checking route IPv6" and "Checking DNS" are the checks Eddie runs after the tunnel is up, to verify that your traffic and your DNS queries really go through the VPN. When a check does not pass, Eddie gives up after about a minute, disconnects and tries again, so it looks stuck. Since a system restart fixes it and restarting Eddie does not, we assume something left over on the system by a previous session, not the server. On Windows with WireGuard we have seen exactly this: a tunnel adapter from a session that did not close properly (crash, sleep or shutdown while connected) stays up as "Eddie 1" and keeps the VPN routes, so the new tunnel's traffic goes to the old adapter and the checks time out. Closing Eddie does not remove it, because the network part runs in the "Eddie Elevation Service", which keeps running in the background. If you use Windows, next time it happens please try this before restarting: 1. Close Eddie. 2. Open Services (services.msc), right-click "Eddie Elevation Service" and choose Restart. 3. Start Eddie and connect again. Tell us whether that is enough. When you do need to restart Windows, use Start > Power > Restart rather than Shut down: with Fast Startup (the default) a shutdown does not fully reset the system. If it does not help, or you do not use Windows, please tell us your operating system, Eddie version and protocol (WireGuard or OpenVPN), and post a system report generated right after a failed attempt, before restarting the system: https://airvpn.org/forums/topic/50663-youve-been-asked-for-a-support-filesystem-report-–-heres-what-to-do Kind regards
  4. @MadeUpName12 Hello! We assume you are on Windows, because the "Block untunneled traffic (kill-switch)" checkbox exists only in WireGuard for Windows. Please tell us if that is not the case. What you see is how that client works: - With the kill switch on, the client's firewall lets through only the tunnel, loopback, DHCP and DNS queries to the servers in the "DNS =" line. Everything else is blocked, including your LAN, and there is no option for a LAN exception. Putting the Pi-hole's address in the "DNS =" line would let DNS reach it, but the rest of the LAN would stay blocked. - With the kill switch off, there is no firewall, so Windows can also send DNS queries to the resolver of your network adapter (your Pi-hole or your router, possibly an IPv6 resolver announced by the router). There is also a second point: the Pi-hole forwards queries to its upstream servers from the Linux PC's own Internet connection, outside the tunnel. So when a leak test shows your ISP's or a public resolver, it is a real leak, not a false alarm. Keeping the Pi-hole without leaks means the Pi-hole itself must resolve through AirVPN. You have two options. 1. Eddie with WireGuard (simplest) Install Eddie, log in, and in Preferences > Protocols select a WireGuard protocol. Enable Network Lock. In Preferences > Network Lock, "Allow lan/private" is on by default, so your LAN stays reachable while everything else is locked to the tunnel. DNS: use Eddie 2.27.2 (experimental, https://airvpn.org/forums/topic/81340-eddie-desktop-edition-227-beta-released/ ), which blocks every DNS query outside the tunnel. With 2.26.2 (current stable), you must enable Preferences > DNS > "Force all network interfaces for DNS", otherwise Windows can keep asking the Pi-hole and you leak again. Either way, this PC will no longer use the Pi-hole. For ad blocking, enable our DNS block lists at https://airvpn.org/dns/ . The VPN DNS server applies them. Your other LAN devices can keep using the Pi-hole. 2. Keep the Pi-hole and make it resolve through AirVPN In the Client Area, add a new device for the Linux PC and generate a WireGuard configuration for it (do not use the same configuration on two machines at once). On the Linux PC, bring the tunnel up with wg-quick (for example, save it as /etc/wireguard/airvpn.conf, then "sudo wg-quick up airvpn" and "sudo systemctl enable wg-quick@airvpn"). wg-quick keeps your LAN routes, so the other devices should still reach the Pi-hole. In the Pi-hole, Settings > DNS: untick all the preset upstream servers and set 10.128.0.1 as the only custom upstream. That address answers only inside the tunnel, so if the tunnel goes down, the Pi-hole stops resolving instead of leaking. On Windows, keep the kill switch off and put the Pi-hole's LAN address in the "DNS =" line of your WireGuard configuration. The drawback of option 2: Windows has no kill switch, so if its tunnel drops, your traffic goes out in the clear. Then test on https://ipleak.net with your browser's secure DNS (DNS over HTTPS) turned off, otherwise the test shows the DoH provider. Every DNS server listed should belong to AirVPN. With option 2 it may be a different AirVPN server than the one your PC uses (the one the Pi-hole uses). That is fine. If it still does not work, tell us your client, OS and what the leak test shows, and post your WireGuard configuration without the PrivateKey and PresharedKey lines. Kind regards
  5. @Revhead Hello, Network lock is not the cause here: when it is off, Eddie should not leave any firewall rule behind after it exits. The likelier cause is the system DNS. While connected, Eddie points DNS at the VPN DNS server, which can only be reached through the tunnel. Eddie should put your original DNS back when it disconnects. If that restore fails, name resolution keeps going to a server you can no longer reach. Connecting again makes that server reachable, which would explain why Chrome starts working again. Please check this quickly. Disconnect, exit Eddie, then run: sudo systemctl restart NetworkManager Wait a few seconds, then try Chrome again. If you don't use NetworkManager, turning your network connection off and on again does the same. If Chrome works after that, it's DNS. Then please post the following, so we can see why the restore failed: 1. The Eddie version (Help > About) and how you installed it (.deb, AppImage, distribution package). 2. While Chrome is failing, the output of: ls -l /etc/resolv.conf* /etc/systemd_resolve_netif_* resolvectl status sudo nft list tables 3. The Eddie log of one session where you connect, disconnect and exit (Logs tab, copy or save to file). Also tell us: - Whether other programs fail at the same time, e.g. another browser or "ping airvpn.org" in a terminal. - Chrome's exact error, e.g. ERR_NAME_NOT_RESOLVED or ERR_INTERNET_DISCONNECTED. If restarting NetworkManager does not fix it, the output above is still what we need to find the cause. Kind regards
  6. @Millennium Falcon Hello! Both messages mean that the installer could not overwrite two files of the previous Eddie installation, Eddie-CLI-Elevated.exe and wireguard.dll, because they were still in use. Eddie-CLI-Elevated.exe is Eddie's elevated helper, and wireguard.dll is loaded by it while a WireGuard connection is active, so most probably the previous Eddie, or a WireGuard tunnel it had started, was still running during the installation. Please do the following: 1. Click Abort to close the installer. If you already clicked Ignore, the installation is incomplete (old and new files mixed), so do not use it as it is. 2. If Eddie is open, disconnect and then exit it from its menu or from the tray icon. Closing the window is not enough. 3. Restart Windows (use Restart, not Shut down and power on). 4. Run the installer again before you start Eddie. If the same error comes back after the restart: - Uninstall Eddie from Settings > Apps, restart Windows, delete the folder C:\Program Files\AirVPN if it is still there, then run the installer again. Your Eddie settings are stored in a different folder (%LOCALAPPDATA%\Eddie) and are not affected. If Windows refuses to delete the folder because files are in use, restart in Safe Mode, delete it, then restart normally and install. - Check the protection history of your antivirus or Windows Security, in case it blocked or quarantined an Eddie file. If it still fails, please tell us the name of the installer file you downloaded, your Windows version, and whether the error shows other file names too. Kind regards
  7. Eddie is blocking Chrome on Ubuntu although network lock is switched off. Even if I restart Eddie and exit again, Chrome still locks? I open Eddie and connect to recommended server, and Chrome works again? I'm on Winux/Ubuntu 11.26.11 (11.26 Noble) Annoying.
  8. Yesterday
  9. Hi, I get error message's when installing latest AirVPN, any help please? Thanks, 🍿
  10. I was trying various different VPN's recently, was important for me to have port-forwarding so I tried Proton and then Windscribe, and always connected to Netherlands. Airvpn has the lowest ping from me to a netherlands server and the fastest speeds. Also I love how the port doesn't change. Also (compared to Windscribe) no data limits. I bought it for 3 months but now I'm sure I'll be a forever member, cheers
  11. Here's the System Report: https://eddie.website/report/c1f4f9d7/ This morning the internet was accessible, maybe unchecking "Fast Startup" was the solution. As of this AM I would say you solved my problem. I will check tomorrow to see if it's still working fine. Thank you, Marc
  12. Last week
  13. Thank you for raising these issues, they are now fixed. Please let me know if anything else comes up.
  14. For now I'll try option 1 with the IPv4 address. If it costs too many peers on a little seeded torrent then I`ll try option 2. Networklock has always worked so far. Thank you for your extensive and clear explanation.
  15. I setup Wireguard, imported the generated configs, it was all very easy but... My LAN is completely blocked while connected to the VPN now. If I turn off the kill switch in Wireguard, I can access the LAN but all my DNS stops going through the tunnel. Note: I run a pi-hole on a Linux PC and use it's LAN address for my DNS. I would think a million people have the same question but I can't find a definitive answer.
  16. Eddie hangs / gets stuck on connecting to ipv4, ipv6 or searching for DNS. If I restart the system it connects instantly. shutting down the program and switching it back on doesn't work.
  17. Added another year. Thanks for the Linux support
  18. 1) When I start my computer - no websites will load, and no email comes in. 2) I then start Eddie-UI WITHOUT any commandline switches - that's when I see DeActivate Network Lock. I went into Preferences and turned off "Activate Network Lock at startup". 3) The shutdown is accomplished through Task Scheduler running the batch file you sent me at the beginning of the thread: @echo off taskkill /IM Eddie-UI.exe set /a n=0 :wait timeout /t 5 /nobreak >nul tasklist /FI "IMAGENAME eq Eddie-UI.exe" | find /I "Eddie-UI.exe" >nul || goto off set /a n+=1 if %n% lss 12 goto wait :off shutdown /s /t 0 4) The Task History shows this batch file was run successfully last night. 5) I unchecked "Fast Startup" in the Control Panel Section you mention (it was on) (I'm running Windows 10). 6) I had already Deactivated the Network Lock in Eddie (I could not navigate here if I hadn't), so I cannot run the System Report you requested. I'll try to run it tomorrow. Thanks, Marc
  19. Sorry, I just saw this. I will get to this once I have the time, hopefully soon. Thank you for your ongoing interest in this project!
  20. Thanks. 3 years added 👍 My 10 year AirVPN anniversary this year.
  21. Thank you, that works fine. I will probably make the switch to Wireguard in the near future. For now, your services are replacing my previous provider and I followed old habits.
  22. @MadeUpName12 Hello! There are two separate things in your configuration. 1. Please remove the line "auth-user-pass ...". AirVPN does not use a username and password for OpenVPN: the connection is authenticated by the certificate and the key that are already inside the file built by the Config Generator, and the Config Generator never adds auth-user-pass. With that line, OpenVPN asks for a username and a password, or reads them from the file you name there. If that file is missing or cannot be read, OpenVPN stops before it connects. 2. About IPv6. Our OpenVPN servers offer IPv6 inside the tunnel to every OpenVPN client. So with OpenVPN, the IPv4-only exit setting of the Config Generator is not enough by itself, and that is why you still saw IPv6 at the exit. The line that solves it is one of the lines you added: pull-filter ignore "ifconfig-ipv6" With WireGuard, instead, the IPv4-only exit setting of the Config Generator works as expected: the WireGuard file gets only an IPv4 address and routes only IPv4 into the tunnel. In that case IPv6 is not routed into the tunnel at all, so the same note below applies: keep IPv6 disabled on your network adapters. The line with "route-ipv6" does no harm and can stay. The line with "tun-ipv6" can be removed: that option has no effect in OpenVPN 2.6. The warning comes from another option that the server sends, "redirect-gateway ipv6". It routes all the IPv6 traffic of your computer into the tunnel, so that IPv6 can never go out outside the VPN. The tunnel now has no IPv6 address, so OpenVPN warns that the IPv6 routes may not work. This is exactly what you want: IPv6 has nowhere to go. The warning is harmless, and we suggest to keep the configuration as it is. If you still want to remove the warning, you can replace that server option with an IPv4-only one, by adding these two lines: pull-filter ignore "redirect-gateway" redirect-gateway def1 bypass-dhcp After this change IPv6 is no longer routed into the tunnel. Do it only while IPv6 is disabled on all your network adapters. If Windows gets IPv6 back (for example after an update, or on a new adapter), your IPv6 traffic would go out outside the VPN. If the log window still stays open after these changes, please paste here the lines of the log from "Initialization Sequence Completed" on. If you paste the configuration again, remove the certificate and key blocks first. Kind regards
  23. @major4579 Hello! The "Deactivate Network Lock" button you see after starting Eddie in the morning refers only to the Eddie session you just started, so it can't tell whether the overnight exit worked. When Eddie starts, it first removes any Network Lock rules left by a previous session, then it activates a new Network Lock because of --netlock in your command line or "Activate Network Lock at startup" in Preferences > General. Note that saving the Preferences from a session started with --netlock stores that option as ticked, so it may be active even if you never ticked it yourself. There is no command line switch that tells a running Eddie to deactivate the Network Lock and exit: command line options are read only when Eddie starts. Please check one thing tomorrow morning. Before you start Eddie, open a web page in your browser. Does it load? If the page loads, the batch file works. Your batch file ends with a full shutdown, and a full shutdown removes all Network Lock rules. So no rules are left from the night before. In this case, what you should change depends on what you want in the morning. If you want to be connected to the VPN: - Create a task in Task Scheduler with the trigger "At log on". - The task must start Eddie with your usual command line. - Do not use the "Start with System" option of Eddie for this. That option starts Eddie without your command line options. If you want normal internet until you connect: - In Eddie, go to Preferences > General and untick "Activate Network Lock at startup". - Remove --netlock from the shortcut or command that you use in the morning. If it does not load: please tell us what really turns the computer off. Has the previous scheduled shutdown been removed? Is it a real shutdown, or sleep or hibernation? Does the History tab (or "Last Run Result") of the task in Task Scheduler show that the batch file ran? Please also disable Fast Startup (Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable > untick "Turn on fast startup"). In this case, starting Eddie removes the leftover rules by itself. In both cases, start Eddie as usual and, before you deactivate the Network Lock, publish a system report as explained here: https://airvpn.org/forums/topic/50663-youve-been-asked-for-a-support-filesystem-report-–-heres-what-to-do The line "Windows WFP, recovery of pending rules." in the log shows that rules from the previous session were really still there. @pHxaq thank you for the suggestion; the DNS problem you describe is a different symptom, and Marc has already ruled it out. Kind regards
  24. @NL99 Hello! What you see is how the two programs work together today, not a problem with your qBittorrent installation, so a reinstall can't change it. With WireGuard, Eddie 2.26.2 on Windows creates the "Eddie" adapter when a connection starts and removes it when the connection ends. A server change is a new connection, so it gets a new adapter: same name, "Eddie", but a new identity for Windows (a new GUID and a new interface identifier). qBittorrent does not store the name you see in the list. It stores that identifier (the "iftype..." value in Session\Interface) and passes the adapter GUID to libtorrent when the setting is applied, that is at startup or when you change the setting. After a server change the old adapter no longer exists, so qBittorrent can neither send nor receive anything (it fails closed, so nothing leaks), and it does not move to the new adapter by itself. The second "Eddie" entry in the list is qBittorrent showing the saved interface that no longer exists, next to the current one. Selecting the interface again, or restarting qBittorrent, applies the setting again, and that's why both work. About qBittorrent.ini: changes there count only if qBittorrent is completely closed (tray icon included) while you edit the file, otherwise it writes its own settings back when it exits. It's easier to change these settings from the qBittorrent window. We see two options. 1. Bind to the WireGuard address instead of the adapter. In qBittorrent > Tools > Options > Advanced set "Network interface" to "Any interface" and "Optional IP address to bind to" to the IPv4 address of your WireGuard connection (10.x.x.x). You can read it in Eddie, Stats tab, "VPN IP", or with ipconfig on the Eddie adapter while connected. With WireGuard this address belongs to your device key and is the same on every AirVPN server, so the binding survives server changes: libtorrent re-opens its sockets when the address comes back on the new adapter. When the tunnel is down the address does not exist and qBittorrent can't connect, the same protection you have now. Limits: qBittorrent accepts one address only, so with an IPv4 address you will not connect to IPv6 peers; the address changes if you connect with a different device in Eddie or renew that device's key (set it again in that case); it does not work with OpenVPN, where the address can change at every connection. 2. Set "Network interface" to "Any interface" and rely on Eddie's Network Lock. Network Lock stays active while Eddie changes server, so qBittorrent can't go out of the tunnel during the switch. Note that when Network Lock is activated automatically at connection (the default), Eddie removes it when you disconnect. If you want qBittorrent to stay blocked while Eddie is disconnected too, activate Network Lock from Eddie's main window: it stays active until you deactivate it or close Eddie. If you go for option 1, you can still keep Network Lock active, as an extra protection for everything else on your system. Kind regards
  25. Hello! We're glad to inform you that AirVPN Suite for Linux next release will include AmneziaWG support with full integration with AirVPN, similarly to Eddie Android edition. We should be able to make a preview publicly available before the end of November. Kind regards
  26. I need an AmneziaWG Eddie support for Linux so much. Right now I have to run airvpn from terminal in order to use AmneziaWG.
  27. Hello people, new here, happy so far. Win 11 pro 25H2 OpenVPN 2.6.14 OpenVPN GUI 11.55.0.0 I used the config generator, that is really slick by the way, selected the specific servers I wanted, and set it to IPV4 only but, I'm still seeing IPV6 connections on the outside. Well, I was until I added these last 3 lines to the config. Now I just see errors (below) in the connection log telling me it's doing what I want but, why is it trying to make these connections at all? All the little IPV6 check boxes are unchecked everywhere on the LAN. Can I stop it from trying? It makes the log popup and stay on the screen when I connect. Just a small annoyance but little errors bug me, especially when I have to respond to them every time, even with a single click. WARNING: OpenVPN was configured to add an IPv6 route. However, no IPv6 has been configured for OpenVPN Data Channel Offload, therefore the route installation may fail or may not work as expected. client dev tun remote 198.44.129.210 1194 resolv-retry infinite nobind persist-key persist-tun auth-nocache verb 3 explicit-exit-notify 5 rcvbuf 262144 sndbuf 262144 remote-cert-tls server data-ciphers AES-256-GCM:AES-192-GCM:AES-128-GCM data-ciphers-fallback AES-256-GCM proto udp auth SHA512 block-outside-dns auth-user-pass xxxxxxxxxxx pull-filter ignore "ifconfig-ipv6" pull-filter ignore "route-ipv6" pull-filter ignore "tun-ipv6"
  28. Go to the buy page and scroll all the way down to Gift voucher.
  1. Load more activity
×
×
  • Create New...