Not connected, Your IP: 216.73.217.13
Online: 42636 users - 534556 Mbit/s total BWAll Activity
This stream auto-updates
- Past hour
-
-
- Yesterday
-
-
-
-
-
-
-
-
-
-
-
https://eddie.website/report/0416538d/ Here is my system report. Please take a look. So, the fact that nft isn't showing up in Network Lock wasn't Eddie's problem—it was mine. I apologize. -
@lexsilico Hello! Thank you. We now have all the data. We will update this thread when we have more definite information. In the meantime keep using the successful patch you have already applied. Kind regards
-
.thumb.png.8be84fd39f94c1640ac8c5456fbf3449.png)
@72MqavduqVa286gd Hello! Nothing changed in Eddie's choice order about which firewall utility to run for the Network Lock rules. If both iptables-legacy and nft utilities are available Eddie picks iptables to avoid mixing up nft and iptables rules in various distributions running daemons at startup that, in turn, still run iptables (mixing up nft and iptables causes problems). You may force Eddie to use nft in "Preferences" > "Network Lock" windows, provided that the nft utility is in the command path. However this is probably irrelevant because, for Network Lock purposes, iptables and nft rules are identical. DNS leaks are not strictly related to network lock: we mean that in general there must be no DNS leak with or without Network Lock. Feel free to publish a system report generated by Eddie for further investigation. Kind regards -
Hi! i has been looking another post in the forum but not gettig a idea what it colud be the problem what is running good in my Ubuntu KDE desktop I just get a Raspberry PI 5 4 gb and the lastest official release of ubuntu for rasp 4 gb avaible ( 24.04.4 LTS ? ) from the official website 24.04.4 LTS First at all i tried the EDDI UI from this section https://airvpn.org/linux/eddie/I ( Linux -> ARM64 ( adecuate for Rasp 5 4gb) --> Eddi Gui-Cli --> Debian -> Grapich UI .. and apparently it install goes well, and the icon appears on the Ubuntu Raspb. But you click on it and apparently Eddi has no response. A have read another similiar topics but n idea what could happens. I tried unistall, and re install but the entire SUITE this time. ( i only undestand the UI not the terminal thing ) And the the Suit apparently is running in the process, but the installed icon on Ubuntu Rasp dont lauch the UI interface Its not a major issue for me, but really would use AirVpn on my Rasp 5 , 4gb as backup pc from time to time ( i dont have much skills on linux terminal ) Any idea ? Thanks ! -
I am using DD-WRT, and want to exclude my mail server, as my ISP keeps blocking emails sent / received via VPN connections Can see that I can use policy based routing to exclude certain IP address, however my ISP uses dynamic IP addresses in different ranges, Google reports that mail.btinternet.com often resolves to 40.92.0.0/15 or 104.47.0.0/17 ranges How to I configure DD-WRT to exclude this domain?
-
Hi, before bluetit startup: root@pi:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG 100 0 0 end0 0.0.0.0 192.168.1.254 0.0.0.0 UG 600 0 0 wlan0 192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 end0 192.168.1.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0 root@pi:~# ip route get 141.98.100.148 141.98.100.148 via 192.168.1.254 dev end0 src 192.168.1.52 uid 0 cache root@pi:~# ip -6 route get 2001:ac8:31:368:e619:164f:9446:ff2e 2001:ac8:31:368:e619:164f:9446:ff2e from :: via fe80::8e97:eaff:fe32:b526 dev end0 proto ra src 2a01:e0a:28:f0c0:d38d:33af:741e:3159 metric 100 pref medium bluetit startup log: Apr 19 11:42:23 pi systemd[1]: Starting bluetit.service - AirVPN Bluetit Daemon... Apr 19 11:42:23 pi hummingbird[1366]: Hummingbird - WireGuard/OpenVPN3 Client 2.0.0 - 22 July 2025 Apr 19 11:42:23 pi hummingbird[1366]: OpenVPN core 3.12 AirVPN (20250606) linux arm64 64-bit Apr 19 11:42:23 pi hummingbird[1366]: Copyright (C) 2012- OpenVPN Inc. All rights reserved. Apr 19 11:42:23 pi hummingbird[1366]: OpenSSL 3.5.5 27 Jan 2026 Apr 19 11:42:23 pi hummingbird[1366]: AirVPN WireGuard Client 2.0.0 Linux aarch64 64-bit Apr 19 11:42:23 pi hummingbird[1366]: Sun Apr 19 11:42:23.341 2026 Scanning for system DNS addresses Apr 19 11:42:23 pi hummingbird[1366]: Sun Apr 19 11:42:23.344 2026 Found system IPv4 DNS 1.1.1.1 Apr 19 11:42:23 pi hummingbird[1366]: Sun Apr 19 11:42:23.344 2026 Found system IPv4 DNS 8.8.8.8 Apr 19 11:42:23 pi hummingbird[1366]: Sun Apr 19 11:42:23.344 2026 Found system IPv4 DNS 192.168.1.254 Apr 19 11:42:23 pi hummingbird[1366]: Sun Apr 19 11:42:23.344 2026 Found 3 system DNS addresses Apr 19 11:42:23 pi hummingbird[1366]: It seems this program has properly exited in its last run and it has already Apr 19 11:42:23 pi hummingbird[1366]: restored network settings on exit. Apr 19 11:42:23 pi hummingbird[1366]: Network recovery is not needed. Apr 19 11:42:23 pi bluetit[1375]: Starting Bluetit - AirVPN WireGuard/OpenVPN3 Service 2.0.0 - 22 July 2025 Apr 19 11:42:23 pi bluetit[1375]: OpenVPN core 3.12 AirVPN (20250606) linux arm64 64-bit Apr 19 11:42:23 pi bluetit[1375]: Copyright (C) 2012- OpenVPN Inc. All rights reserved. Apr 19 11:42:23 pi bluetit[1375]: SSL Library: OpenSSL 3.5.5 27 Jan 2026 Apr 19 11:42:23 pi bluetit[1375]: AirVPN WireGuard Client 2.0.0 Linux aarch64 64-bit Apr 19 11:42:23 pi bluetit[1378]: Bluetit daemon started with PID 1378 Apr 19 11:42:23 pi bluetit[1378]: Reading run control directives from file /etc/airvpn/bluetit.rc Apr 19 11:42:23 pi bluetit[1378]: Network check mode is gateway Apr 19 11:42:23 pi bluetit[1378]: Creating AirVPN Boot server list Apr 19 11:42:23 pi systemd[1]: Started bluetit.service - AirVPN Bluetit Daemon. Apr 19 11:42:23 pi bluetit[1378]: Added server http://63.33.78.166 Apr 19 11:42:23 pi bluetit[1378]: Added server http://54.93.175.114 Apr 19 11:42:23 pi bluetit[1378]: Added server http://82.196.3.205 Apr 19 11:42:23 pi bluetit[1378]: Added server http://63.33.116.50 Apr 19 11:42:23 pi bluetit[1378]: Added server http://[2a03:b0c0:0:1010::9b:c001] Apr 19 11:42:23 pi bluetit[1378]: Added server http://bootme.org Apr 19 11:42:23 pi bluetit[1378]: Boot server http://bootme.org resolved into IPv6 2a03:b0c0:0:1010::9b:c001/128 IPv4 82.196.3.205/32 Apr 19 11:42:23 pi bluetit[1378]: AirVPN Boot server list successfully created. Added 6 servers. Apr 19 11:42:23 pi bluetit[1378]: External network is reachable via IPv4 gateway 192.168.1.254 through interface wlan0 Apr 19 11:42:23 pi bluetit[1378]: External network is reachable via IPv6 gateway 192.168.1.254 through interface wlan0 Apr 19 11:42:23 pi bluetit[1378]: Successfully connected to D-Bus Apr 19 11:42:23 pi bluetit[1378]: IPv6 is available in this system Apr 19 11:42:23 pi bluetit[1378]: Default VPN type for AirVPN connections is set to WireGuard Apr 19 11:42:23 pi bluetit[1378]: Bluetit successfully initialized and ready Apr 19 11:42:23 pi bluetit[1378]: Scanning for system DNS addresses Apr 19 11:42:23 pi bluetit[1378]: Found system IPv4 DNS 1.1.1.1 Apr 19 11:42:23 pi bluetit[1378]: Found system IPv4 DNS 8.8.8.8 Apr 19 11:42:23 pi bluetit[1378]: Found system IPv4 DNS 192.168.1.254 Apr 19 11:42:23 pi bluetit[1378]: Found 3 system DNS addresses Apr 19 11:42:23 pi bluetit[1378]: Requesting network IP and country to AirVPN ipleak.net via secure connection Apr 19 11:42:23 pi bluetit[1378]: Network IP: 2a01:e0a:28:f0c0:d38d:33af:741e:3159 Apr 19 11:42:23 pi bluetit[1378]: System country: FR Apr 19 11:42:23 pi bluetit[1378]: AirVPN Manifest updater thread started Apr 19 11:42:23 pi bluetit[1378]: Default AirVPN Manifest update interval is 15 minutes Apr 19 11:42:23 pi bluetit[1378]: AirVPN Manifest update suspended: AirVPN boot connection initialization in progress Apr 19 11:42:23 pi bluetit[1378]: Trying to load the local instance of AirVPN Manifest Apr 19 11:42:23 pi bluetit[1378]: Starting AirVPN WireGuard boot connection Apr 19 11:42:23 pi bluetit[1378]: IPv6 over IPv4 is enabled Apr 19 11:42:23 pi bluetit[1378]: Network filter and lock are using nftables Apr 19 11:42:23 pi bluetit[1378]: AirVPN Manifest successfully retrieved from local instance Apr 19 11:42:23 pi bluetit[1378]: Kernel module nf_tables is already loaded Apr 19 11:42:23 pi bluetit[1378]: Network filter successfully initialized Apr 19 11:42:23 pi bluetit[1378]: Private network is allowed to pass the network filter Apr 19 11:42:23 pi bluetit[1378]: Ping output is allowed to pass the network filter Apr 19 11:42:23 pi bluetit[1378]: IPv6 NDP is allowed to pass the network filter Apr 19 11:42:25 pi bluetit[1378]: Session network filter and lock successfully enabled. Private network is allowed. Apr 19 11:42:25 pi bluetit[1378]: Adding AirVPN bootstrap server 63.33.78.166/32 to network filter Apr 19 11:42:25 pi bluetit[1378]: Adding AirVPN bootstrap server 54.93.175.114/32 to network filter Apr 19 11:42:25 pi bluetit[1378]: Adding AirVPN bootstrap server 82.196.3.205/32 to network filter Apr 19 11:42:25 pi bluetit[1378]: Adding AirVPN bootstrap server 63.33.116.50/32 to network filter Apr 19 11:42:25 pi bluetit[1378]: Adding AirVPN bootstrap server 2a03:b0c0:0:1010::9b:c001/128 to network filter Apr 19 11:42:25 pi bluetit[1378]: Adding AirVPN bootstrap server 2a03:b0c0:0:1010::9b:c001/128 to network filter Apr 19 11:42:25 pi bluetit[1378]: Adding AirVPN bootstrap server 82.196.3.205/32 to network filter Apr 19 11:42:25 pi bluetit[1378]: Updating AirVPN Manifest Apr 19 11:42:25 pi bluetit[1378]: AirVPN bootstrap servers are now allowed to pass through the network filter Apr 19 11:42:25 pi bluetit[1378]: Logging in AirVPN user lexsilico Apr 19 11:42:25 pi bluetit[1378]: Trying connection to AirVPN bootstrap server at http://63.33.78.166 Apr 19 11:42:25 pi bluetit[1378]: Trying connection to AirVPN bootstrap server at http://63.33.78.166 Apr 19 11:42:25 pi bluetit[1378]: AirVPN user lexsilico successfully logged in Apr 19 11:42:25 pi bluetit[1378]: Selected user key: PI Apr 19 11:42:25 pi bluetit[1378]: Starting WireGuard connection to AirVPN server Arber, London (United Kingdom) Apr 19 11:42:25 pi bluetit[1378]: Local interface lo - IPv4 127.0.0.1 IPv6 ::1 Apr 19 11:42:25 pi bluetit[1378]: Local interface end0 - IPv4 192.168.1.52 IPv6 2a01:e0a:28:f0c0:d38d:33af:741e:3159 IPv6 fe80::3c39:6635:ed98:53a4 Apr 19 11:42:25 pi bluetit[1378]: Local interface wlan0 - IPv4 192.168.1.58 IPv6 2a01:e0a:28:f0c0:5b03:a4c1:9a28:18b3 IPv6 fe80::fca1:6d80:5ad6:a4ef Apr 19 11:42:25 pi bluetit[1378]: Default IPv4 gateway via 192.168.1.254 dev wlan0 Apr 19 11:42:25 pi bluetit[1378]: Default IPv6 gateway via 192.168.1.254 dev wlan0 Apr 19 11:42:25 pi bluetit[1378]: Starting WireGuard boot connection Apr 19 11:42:25 pi bluetit[1378]: AirVPN Manifest successfully retrieved from server Apr 19 11:42:25 pi bluetit[1378]: AirVPN Manifest update interval is now set to 30 minutes Apr 19 11:42:25 pi bluetit[1378]: Successfully loaded kernel module wireguard Apr 19 11:42:25 pi bluetit[1378]: WireGuard client successfully created and initialized. Apr 19 11:42:25 pi bluetit[1378]: Ping output is allowed to pass the network filter Apr 19 11:42:25 pi bluetit[1378]: IPv6 NDP is allowed to pass the network filter Apr 19 11:42:25 pi bluetit[1378]: Allowing system IPv4 DNS 1.1.1.1 to pass through the network filter Apr 19 11:42:25 pi bluetit[1378]: Allowing system IPv4 DNS 8.8.8.8 to pass through the network filter Apr 19 11:42:25 pi bluetit[1378]: Allowing system IPv4 DNS 192.168.1.254 to pass through the network filter Apr 19 11:42:27 pi bluetit[1378]: Setting up WireGuard network interface tun0 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 0.0.0.0/0 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv6 ::/0 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 0.0.0.0/5 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 8.0.0.0/7 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 11.0.0.0/8 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 12.0.0.0/6 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 16.0.0.0/4 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 32.0.0.0/3 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 64.0.0.0/2 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 128.0.0.0/3 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 160.0.0.0/5 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 168.0.0.0/6 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 172.0.0.0/12 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 172.32.0.0/11 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 172.64.0.0/10 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 172.128.0.0/9 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 173.0.0.0/8 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 174.0.0.0/7 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 176.0.0.0/4 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 192.0.0.0/9 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 192.128.0.0/11 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 192.160.0.0/13 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 192.169.0.0/16 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 192.170.0.0/15 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 192.172.0.0/14 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 192.176.0.0/12 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 192.192.0.0/10 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 193.0.0.0/8 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 194.0.0.0/7 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 196.0.0.0/6 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 200.0.0.0/5 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 208.0.0.0/4 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv4 224.0.0.0/3 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv6 8000::/2 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv6 c000::/3 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv6 e000::/4 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv6 f000::/5 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv6 f800::/6 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv6 fc00::/8 Apr 19 11:42:27 pi bluetit[1378]: Allowing IPv6 fe00::/7 Apr 19 11:42:27 pi bluetit[1378]: WireGuard end point set to IPv4 141.98.100.146, port 1637 Apr 19 11:42:27 pi bluetit[1378]: Successfully created WireGuard device tun0 Apr 19 11:42:27 pi bluetit[1378]: WireGuard interface tun0 set to IPv4 10.162.161.237/32 Apr 19 11:42:27 pi bluetit[1378]: WireGuard interface tun0 set to IPv6 fd7d:76ee:e68f:a993:f55b:14f8:7d12:5913/128 Apr 19 11:42:27 pi bluetit[1378]: WireGuard interface tun0 successfully configured Apr 19 11:42:27 pi bluetit[1378]: MTU WireGuard network interface tun0 set to 1320 Apr 19 11:42:27 pi bluetit[1378]: WireGuard network interface tun0 successfully initialized and ready Apr 19 11:42:27 pi bluetit[1378]: Adding IPv4 server 141.98.100.146 to network filter Apr 19 11:42:28 pi bluetit[1378]: Network filter and lock successfully activated Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 0.0.0.0/0 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv6 ::/0 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 0.0.0.0/5 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 8.0.0.0/7 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 11.0.0.0/8 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 12.0.0.0/6 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 16.0.0.0/4 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 32.0.0.0/3 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 64.0.0.0/2 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 128.0.0.0/3 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 160.0.0.0/5 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 168.0.0.0/6 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 172.0.0.0/12 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 172.32.0.0/11 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 172.64.0.0/10 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 172.128.0.0/9 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 173.0.0.0/8 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 174.0.0.0/7 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 176.0.0.0/4 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 192.0.0.0/9 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 192.128.0.0/11 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 192.160.0.0/13 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 192.169.0.0/16 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 192.170.0.0/15 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 192.172.0.0/14 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 192.176.0.0/12 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 192.192.0.0/10 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 193.0.0.0/8 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 194.0.0.0/7 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 196.0.0.0/6 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 200.0.0.0/5 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 208.0.0.0/4 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 224.0.0.0/3 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv6 8000::/2 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv6 c000::/3 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv6 e000::/4 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv6 f000::/5 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv6 f800::/6 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv6 fc00::/8 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv6 fe00::/7 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 128.0.0.0/1 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv6 8000::/1 dev tun0 Apr 19 11:42:28 pi bluetit[1378]: Network gateway is IPv4 192.168.1.254/32 via interface wlan0 Apr 19 11:42:28 pi bluetit[1378]: Added route IPv4 141.98.100.146/32 via 192.168.1.254 dev wlan0 Apr 19 11:42:28 pi bluetit[1378]: Successfully initialized WireGuard device tun0 Apr 19 11:42:28 pi bluetit[1378]: Connected to AirVPN server Arber, London (United Kingdom) (WireGuard) Apr 19 11:42:28 pi bluetit[1378]: VPN Server has pushed DNS IPv4 10.128.0.1 Apr 19 11:42:28 pi bluetit[1378]: Setting pushed IPv4 DNS server 10.128.0.1 in resolv.conf Apr 19 11:42:28 pi bluetit[1378]: VPN Server has pushed DNS IPv6 fd7d:76ee:e68f:a993::1 Apr 19 11:42:28 pi bluetit[1378]: Setting pushed IPv6 DNS server fd7d:76ee:e68f:a993::1 in resolv.conf Apr 19 11:42:28 pi bluetit[1378]: Server has pushed its own DNS. Rejecting system DNS from network filter. Apr 19 11:42:28 pi bluetit[1378]: System IPv4 DNS 1.1.1.1 is now rejected by the network filter Apr 19 11:42:28 pi bluetit[1378]: System IPv4 DNS 8.8.8.8 is now rejected by the network filter Apr 19 11:42:28 pi bluetit[1378]: System IPv4 DNS 192.168.1.254 is now rejected by the network filter Apr 19 11:42:28 pi bluetit[1378]: WireGuard connection monitor thread started Apr 19 11:42:28 pi bluetit[1378]: Connected to AirVPN server Arber, London (United Kingdom) IP address 141.98.100.146 - VPN Type WireGuard - Port 1637 - Protocol UDPv4 - Cipher CHACHA20-POLY1305 Apr 19 11:42:28 pi bluetit[1378]: Pushed DNS: 10.128.0.1 (IPv4) fd7d:76ee:e68f:a993::1 (IPv6) Apr 19 11:42:28 pi bluetit[1378]: Connection monitor thread started After stopping bluetit: root@pi:~# ip route get 141.98.100.148 141.98.100.148 via 192.168.1.254 dev end0 src 192.168.1.52 uid 0 cache root@pi:~# ip -6 route get 2001:ac8:31:368:e619:164f:9446:ff2e 2001:ac8:31:368:e619:164f:9446:ff2e from :: via fe80::8e97:eaff:fe32:b526 dev end0 proto ra src 2a01:e0a:28:f0c0:d38d:33af:741e:3159 metric 100 pref medium Regards
-
-
Until a few days ago, I was able to use nftables with Eddie’s Network-Lock, and I wasn’t experiencing any DNS leaks. However, when I checked Eddie yesterday, I found that these options had been removed from the Network-Lock settings, leaving me with only iptables-legacy as an option. I had no choice but to try using iptables-legacy, but now I’m experiencing DNS leaks, which is causing me some trouble. OS: Arch Linux (6.19.11-arch1-1) Eddie Version: v2.25.1
-
Hello! Thanks. Now let's see which route the kernel picks to reach WireGuard's EndPoint. Pick a specific server and verify that the connection takes place through wlan0. From your initial message we see that you may have picked a UK server, let's say Arber (entry-IP addresses 3: 141.98.100.148 and 2001:ac8:31:368:e619:164f:9446:ff2e). Connect to Arber (not to UK in general, connect to this specific server) and verify from the log that WireGuard picks wlan0. Disconnect, shut down Bluetit (sudo systemctl stop bluetit), and check the route the kernel picks on its own: ip route get 141.98.100.148 ip -6 route get 2001:ac8:31:368:e619:164f:9446:ff2e Publish the whole output. Kind regards
-
DeepAnger reacted to a post in a topic:
Title: IPv6 not routing through AirVPN on OpenWrt (WireGuard) ...
- Last week
-
root@pi:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether dc:a6:32:ef:f9:dc brd ff:ff:ff:ff:ff:ff altname enxdca632eff9dc inet 192.168.1.52/24 brd 192.168.1.255 scope global dynamic noprefixroute end0 valid_lft 43166sec preferred_lft 43166sec inet6 2a01:e0a:28:f0c0:d38d:33af:741e:3159/64 scope global dynamic noprefixroute valid_lft 86367sec preferred_lft 86367sec inet6 fe80::3c39:6635:ed98:53a4/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether dc:a6:32:ef:f9:dd brd ff:ff:ff:ff:ff:ff inet 192.168.1.58/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0 valid_lft 43199sec preferred_lft 43199sec inet6 2a01:e0a:28:f0c0:5b03:a4c1:9a28:18b3/64 scope global dynamic noprefixroute valid_lft 86388sec preferred_lft 86388sec inet6 fe80::fca1:6d80:5ad6:a4ef/64 scope link noprefixroute valid_lft forever preferred_lft forever root@pi:~# ip route show default via 192.168.1.254 dev end0 proto dhcp src 192.168.1.52 metric 100 default via 192.168.1.254 dev wlan0 proto dhcp src 192.168.1.58 metric 600 192.168.1.0/24 dev end0 proto kernel scope link src 192.168.1.52 metric 100 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.58 metric 600
-
Hello! Please send also the output of ip a ip route show before you start Bluetit and/or WireGuard. Kind regards
-
Please re-read. Your question: "any plan ...?". Answer: "Yes ...". Kind regards
-
If there is support, why can't I connect to the servers if I set H1-H4 values greater than 4 and S1-S4 values greater than 0?
-
root@pi:~# nmcli connection show NAME UUID TYPE DEVICE Wired connection 1 1693fcab-84c6-3f41-bc4e-31c30b6a8c08 ethernet end0 preconfigured 9b934a92-9fe6-431c-b425-4211bcaa1166 wifi wlan0 lo ace10a9f-6ae4-4b51-a444-560071316ec0 loopback lo tun0 65f15452-619d-4848-9793-a519f7b08139 wireguard tun0 Please let me know what other info on configuration you would need
-
root@pi:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.1.254 0.0.0.0 UG 100 0 0 end0 default 192.168.1.254 0.0.0.0 UG 600 0 0 wlan0 192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 end0 192.168.1.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0 root@pi:~# systemctl start bluetit root@pi:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 0.0.0.0 248.0.0.0 U 0 0 0 tun0 0.0.0.0 0.0.0.0 128.0.0.0 U 0 0 0 tun0 default 192.168.1.254 0.0.0.0 UG 100 0 0 end0 default 192.168.1.254 0.0.0.0 UG 600 0 0 wlan0 8.0.0.0 0.0.0.0 254.0.0.0 U 0 0 0 tun0 11.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 tun0 12.0.0.0 0.0.0.0 252.0.0.0 U 0 0 0 tun0 16.0.0.0 0.0.0.0 240.0.0.0 U 0 0 0 tun0 32.0.0.0 0.0.0.0 224.0.0.0 U 0 0 0 tun0 64.0.0.0 0.0.0.0 192.0.0.0 U 0 0 0 tun0 128.0.0.0 0.0.0.0 224.0.0.0 U 0 0 0 tun0 128.0.0.0 0.0.0.0 128.0.0.0 U 0 0 0 tun0 141.98.100.146 192.168.1.254 255.255.255.255 UGH 0 0 0 wlan0 160.0.0.0 0.0.0.0 248.0.0.0 U 0 0 0 tun0 168.0.0.0 0.0.0.0 252.0.0.0 U 0 0 0 tun0 172.0.0.0 0.0.0.0 255.240.0.0 U 0 0 0 tun0 172.32.0.0 0.0.0.0 255.224.0.0 U 0 0 0 tun0 172.64.0.0 0.0.0.0 255.192.0.0 U 0 0 0 tun0 172.128.0.0 0.0.0.0 255.128.0.0 U 0 0 0 tun0 173.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 tun0 174.0.0.0 0.0.0.0 254.0.0.0 U 0 0 0 tun0 176.0.0.0 0.0.0.0 240.0.0.0 U 0 0 0 tun0 192.0.0.0 0.0.0.0 255.128.0.0 U 0 0 0 tun0 192.128.0.0 0.0.0.0 255.224.0.0 U 0 0 0 tun0 192.160.0.0 0.0.0.0 255.248.0.0 U 0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 end0 192.168.1.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0 192.169.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 192.170.0.0 0.0.0.0 255.254.0.0 U 0 0 0 tun0 192.172.0.0 0.0.0.0 255.252.0.0 U 0 0 0 tun0 192.176.0.0 0.0.0.0 255.240.0.0 U 0 0 0 tun0 192.192.0.0 0.0.0.0 255.192.0.0 U 0 0 0 tun0 193.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 tun0 194.0.0.0 0.0.0.0 254.0.0.0 U 0 0 0 tun0 196.0.0.0 0.0.0.0 252.0.0.0 U 0 0 0 tun0 200.0.0.0 0.0.0.0 248.0.0.0 U 0 0 0 tun0 208.0.0.0 0.0.0.0 240.0.0.0 U 0 0 0 tun0 224.0.0.0 0.0.0.0 224.0.0.0 U 0 0 0 tun0 root@pi:~# uname -a Linux pi 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64 GNU/Linux
-
Hello! We're glad to know it. Consider that when OpenVPN finds two interfaces with the same default gateway it stops immediately by throwing a critical error due to the ambiguity. Can you publish the system's routing table and the various interface settings before WireGuard is launched? Kind regards
-
Hello, Thanks for this HowTo! I'd like to setup a second interface to a second country and route other parts of my network to that different country. However, in this tutorial, the gateway IP address is static: 10.128.0.1 I cannot find documentation which could explain what IP addresses are available. Could you please help me?
-
Thanks a lot for your detailed answer. FYI, I have changed the route on the fly to use wired connection instead of wireless. And it seems after bluetit restart, it now uses the wired one. Also, to be sure I get only one default route at a time, I have setup a network manager dispatch script (/etc/NetworkManager/dispatcher.d/70-wifi-wired-exclusive.sh) that will disable wifi if wired ethernet is connected, and enable it if it is disconnected (I may also add to restart bluetit service in such case so that routing is recreated correctly in such case). BTW, by default on debian I think both wired & wifi are always up, so my case is probably the general one ! Thx again
-
ANSWERED Windows Wiresock + Port Forward
Staff replied to Scolexis's topic in Troubleshooting and Problems
Solution. Kind regards -
@lexsilico Hello! You still have the option to configure policy-based routing using ip to force WireGuard traffic to go through a specific interface, regardless of the default gateway metric. This specific configuration must be created by you as you have no options to force Bluetit to bypass WireGuard (kernel) decisions, and you have no option to tell WireGuard to do the same. You can add your command(s) on the PostUp and PostDown directives to ensure the correct interface is used during the WireGuard connection lifecycle. Note that in this case you will have to use your own profile with Hummingbird (or with Bluetit and Goldcrest), and not the AirVPN integrated Bluetit/Goldcrest connection mode. We will also consult with the Suite development team to study your case in more details and we will update this thread if necessary. We do not rule out the possibility to add in the future special options to compile PostUp and PostDown commands directly from within Bluetit run control file (possibly not via Goldcrest because WireGuard runs PostUp and PostDown specified executable files with root privileges). Kind regards
-
I have updated awg_conf_patch with support for the AmneziaWG 2.0 parameters: https://github.com/zimbabwe303/awg_conf_patch. The old awg version is still supported: use the -o option. I have also updated the default parameters with better ones: the shuffled H1..4 parameters stopped working recently for some reason (at least for me) so I replaced them with the old generic ones. To still use the shuffled ones set amnezia_CustomH=0 in the script itself.
-
-
awg_conf_patch was updated with support for awg 2.0: https://github.com/zimbabwe303/awg_conf_patch
-
Good afternoon, I recently configured Wiresock by generating a config file, everything was working fine yesterday. However, after a reboot and no other setting changes the port forward isn't working properly through the Wiresock connection any longer. I've tried generating a new config file just to see and same issue. I removed all my ports except for one to see if I just had too many and it was just getting confused. Does anyone know if there's anything specific to configure inside of Wiresock? I've only setup split tunnelling for a couple of specific applications and enabled the virtual adapter setting; everything else is left at the default. I am also running Tailscale if that matters at all, not sure if it would interfere, but killing that connection doesn't seem to have any effect. I do have AirVPN installed on my other machine and port forwarding seems to be working fine there, so I think it's a misconfiguration with Wiresock; I'm just unsure where to check. Any help or nudges in the right direction would be appreciated. Edit: I figured it out; I had to allow qBittorrent in my firewall rules for the public network. Feel free to close this thread.
-
Hi, I'm using the AirVPN Suite for Linux 2.0.0 installed on my raspberry, with wireguard. Everything works fine, but I noticed that it seems that when mounting tun0, bluetit is choosing my wifi interface instead of my wired interface for routing. From the logs I can see : Network gateway is IPv4 192.168.1.254/32 via interface wlan0 Added route IPv4 141.98.XXX.XXX/32 via 192.168.1.254 dev wlan0 Successfully initialized WireGuard device tun0 I have both interfaces enabled on my raspberry (wired : end0 and wifi wlan0), but my wired interface has a lower metric for routing, so I was expecting bluetit to use end0 instead of wlan0. I would prefer to use end0 instead of wlan0 for my vpn. Can you help me to use wlan0 as a first choice ? (btw I don't want to disable wifi interface). Thx
-
Just as a note, since the first days of April the situation with VPNs in Russia is going into the real Cheburnet phase: Spyware VPN detectors will be inserted into all the major commercial mobile apps (Max, VK, Yandex, banks, phone carriers, etc.), every detected endpoint IP will most likely go into the country-wide blacklist The increase of the cross-border backbone bandwidth has already been vetoed because it has grown over the top in the last year due to the VPNs Because of that there are rumors that more than 15 GB/month of cross-border traffic will have added cost for every end user VPN software will be detected on every in-country VPS hosting provider to prevent using them as bridges (it is already a common practice to circumvent white list blocks) Recently there were wired Internet shutdowns looking very much like tests of white list blocks (before that only mobile Internet had white lists) By the way, it's very hard to find any AirVPN server which is not yet blocked. But I can still find some (mostly in Netherlands) by automated scanning. AmneziaWG is necessary, of course.
-
-
-
-
increasing efficiency in blocking ads and trackers
Staff replied to Tionni's topic in General & Suggestions
Hello! We already implemented it in 2021. Any domain which must be blocked includes all of its subdomains too. Besides, different matching methods are available for your additions and exceptions: Exact (exact FQDN), Domain (domain and its subdomains), Wildcard (with * and ? as wildcards), Contain, Start with, End with. Kind regards
