All Activity
This stream auto-updates
- Past hour
-
Of course. The steps are as follows: 1. Configure Clash (agent software) Import proxy nodes using a proxy vendor link (proxy nodes can use any protocol). Clash settings - Port - Socks port - Enable - Set to 10000 (the port number can be anything). 2. Configure Eddie Eddie settings - Proxy/Tor - Type - socks - When - Always - Host - 127.0.0.1 - Port-10000 - Authentication - none Eddie Settings - Protocol - Select OpenVPN TCP 443 Eddie Settings - Network Lock - Uncheck "Ensure in Session" save 3. Connection To use it, first open Clash and connect to the proxy node using the system proxy mode, then open Eddie and connect to the server. 4. Diversion With this setup, all software still uses the proxy node and does not go through the AirVPN server, so traffic splitting is necessary. (There may be professional software for setting up traffic splitting rules, but I didn't use it; I'm just sharing my approach.) For browsers, the ProxySwitch plugin can be used to select direct connection mode. For other applications, they can listen on port 10003 of the AirVPN port forwarding service (this is different from the Socks port; it's port forwarding configured in the AirVPN panel). This allows you to route traffic through a proxy node for obfuscation before it passes through the AirVPN server, effectively enhancing the obfuscation effect.
-
Throughput Drop on IPTV (Strong8k) with WireGuard/OpenVPN
ASiC666 replied to kevinhjl's topic in Troubleshooting and Problems
I have the exact same issue, no matter which server I'm using. Did a lot of experimenting with different regions and servers to unfortunately bad results. I have a backup VPN just for this use case... -
-
-
-
- Today
-
-
-
-
-
-
-
-
-
-
-
-
that is very cool and easy but how are leaks handled?
-
Tech Jedi Alex started following https://1337x.to/ blocked on Denver servers and AirVPN Additional Proxy ...
-
I remember many people asking for direct Shadowsocks and other protocol support, which won't be implemented anytime soon, especially if usage of these protocols is possible in parallel with Eddie (and other VPN software supporting proxies). If it's not a big ask, could you provide a guide on how to set this up? I think you will meet some tangible demand.
-
https://1337x.to/ blocked on Denver servers
Tech Jedi Alex replied to Esoter1c's topic in Blocked websites warning
I expect an apology from both of you for baseless slander. -
-
-
Hello all, relatively new user here loving the service, but I’ve hit a specific wall regarding IPTV performance. Google TV Streamer 4K (hardwired 1GBps) connected to AirVPN via VPN Fusion on ASUS router (WireGuard/OpenVPN), analiti (speed test) shows speed of 400Mbps with and without VPN enabled. However, the moment I launch a stream, the bitrate collapses to below 100kBps. Without the VPN, the stream sustains 2-3Mbps without issue. Appreciate any help I could get, thanks!
-
-
Currently, AirVPN only has three options for bypassing the block: SSH SSL and AmneziaWG, which is already quite excellent for a VPN provider. However, these options are still insufficient in the face of the ever-evolving GFW and other national firewalls. Perhaps we can outsource the protocol obfuscation part to other proxy providers, while leaving the basic privacy protection part to AirVPN. I have implemented the addition of dedicated proxies from other vendors in Eddie. I set a hybrid proxy port x in the Clash software and set a SOCKS proxy 127.0.0.1:x in Eddie. This way, traffic goes through the proxy first and then is forwarded to the AirVPN server. I can use the obfuscation performance of the proxy protocol to obfuscate AirVPN traffic. This makes a wide variety of obfuscation protocols available, such as Vless, AnyTLS, Hysteria2, Shadowsocks, Trojan, and Vmess. Using a proxy provider combined with a VPN provider allows me to bypass internet censorship smoothly, which is a good idea.
-
Helllo everyone, I run a NAS Qnap TS-464-8g. I mainly use it for torrenting and media server. Currently it runs docker image that containes qbittorrent + gluetun with airvpn configuration. It works fine and connected easily, however, I see slow speeds. Since I tried another vpn , the speeds are way better. I chose closes servers to me, which are Latvia and Estonia. Could someone tell me if avg speeds of 2mb/s is what expected with airvpn? I seed quite a lot of torrents, about 30active all the time, and speeds should be way higher since i've seen greated with different provider. Thanks. EDIT: I've added - WIREGUARD_MTU=1280 after I created the thread. with no impact to speeds. still avg 2mb/s upload. EDIT2: While docker exec'd into gluetun container, and running flat downloadi get 300-350 (40mb/s) mbps speeds EDIT3: I've noticed that just after starting the container with qbit+gluetun+airvpn(wireguard) i see my torrents uploading at 10mb/s, which would indicate the speeds can be higher, but after a minute, the speed drops to 2mb/s services: # ===================== # VPN # ===================== gluetun: image: qmcgaw/gluetun:latest container_name: gluetun cap_add: - NET_ADMIN devices: - /dev/net/tun:/dev/net/tun ports: - 8081:8081 # qBittorrent WebUI - 6881:6881 - 6881:6881/udp volumes: - /share/CACHEDEV1_DATA/Container/gluetun/config:/config - /share/CACHEDEV1_DATA/Container/gluetun:/gluetun environment: - VPN_SERVICE_PROVIDER=airvpn - VPN_TYPE=wireguard - TZ=redacted - WIREGUARD_PRIVATE_KEY=redacted - WIREGUARD_PRESHARED_KEY=redacted - WIREGUARD_ADDRESSES=redacted - WIREGUARD_MTU=1280 - SERVER_COUNTRIES=Latvia,Estonia - FIREWALL_VPN_INPUT_PORTS=3228 - LOGLEVEL=debug - LOCAL_NETWORK=192.168.0.0/24 - FIREWALL_INPUT_PORTS=8081 - PUID=0 - PGID=0 networks: - proxy restart: unless-stopped # ===================== # QBITTORRENT # ===================== qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent network_mode: "service:gluetun" depends_on: gluetun: condition: service_healthy restart: true environment: - PUID=0 - PGID=0 - TZ=redacted - WEBUI_PORT=8081 volumes: - /share/CACHEDEV1_DATA/'redacted'/qbittorrent:/config - /share/CACHEDEV2_DATA/'redacted':/downloads - /share/CACHEDEV3_DATA/'redacted':/downloads2 - /share/CACHEDEV4_DATA/'redacted':/downloads3 restart: unless-stopped networks: proxy: external: true
-
https://1337x.to/ blocked on Denver servers
bluesjunior replied to Esoter1c's topic in Blocked websites warning
Here is a copy of the message on the current happenings. - Yesterday
-
https://1337x.to/ blocked on Denver servers
bluesjunior replied to Esoter1c's topic in Blocked websites warning
The site has been under a DDOS attack for a while and the owner blacklisted heavy usage servers as one of a series of countermeasures. He apologised for some innocent victims of this but the site seemed to be working fine this morning, so hopefully it is back to normal now.. -
-
https://1337x.to/ blocked on Denver servers
Nicolas3011 replied to Esoter1c's topic in Blocked websites warning
Yeah the guy blacklisted all the servers now amazing 😀 f him -
-
I've now tried an ASUS router running Merlin, and Outlook can't even see mail.btinternet.com once the VPN is up and running
-
Internet Blocked When Eddie VPN off
Tech Jedi Alex replied to VortexSimp482's topic in Eddie - AirVPN Client
Erm.. wow, that's quite the overreaction, to be honest. It's most probably DNS, and even if not, it's completely on your computer's side since it was Eddie (or, rather, OpenVPN/Wireguard behind it) that changed some network settings; a new router will do you no good here. What's the OS? -
-
Hi everyone, I have installed eddie to mixed results. Sometimes it works, sometimes it doesn't. The results are poorly reproducible. Key pattern as follows: System boots - eddie starts If VPN connects - works for approximately 3 hours, then issues with connecting to VPN I then restart PC - Will sometimes connect, sometimes never connect So far I have been repeatedly restarting PC until the VPN connects I have tried changing protocols - seems to make no difference Please see attached system logs - from an instance where the VPN is working and an instance where the VPN is not working. Apologies if I am missing something big - I previously just used mullvad/proton - very simple clients. I have little knowledge of networking working vpn.txt not working vpn log.txt
-
-
-
Apologies about the long delay. About my config, Table = off is why not all traffic is routed through airvpn despite the "allowed IPs" line. I'm happy to provide more information to investigate this further if it is interesting but I wouldn't know where to start. I would like to avoid leaking my IP in this forum, but I'm fine providing traces and other things in private messages if that is useful for you.
-
- Last week
-
-
https://1337x.to/ blocked on Denver servers
bungusmccrungus replied to Esoter1c's topic in Blocked websites warning
For whatever reason the lovely site owner who is totally not mentally ill decided to blacklist the Denver servers on AirVPN. Gotta love him, right? Figured I'd warn people about it. -
I can't connect to the internet (wired or wireless) without Eddie Air VPN on. Contacted ISP and they are sending a new router but I also bought a new router and that didn't work, tried uninstalling Eddie (didn't work) I think it may be a DNS issue or IP address issue or some setting blocking internet when VPN is off.. Has anybody else had this issue with Eddie blocking wired and wireless connections when not using VPN? Any help would be greatly appreciated
-
https://airvpn.org/routes/?q=https%3A%2F%2F1337x.to%2Fcat%2FMovies%2F1%2F
-
-
-
@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
-
@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
