Search the Community
Showing results for '{query}'.
Found 598 results
-
DoT and DoH not returning custom responses
bot3291198 posted a topic in Troubleshooting and Problems
I've configured custom responses for DNS. When I query 10.128.0.1:53, I get back the custom A records I've set. When I query 10.128.0.1 over DoT or DoH, I don't get the custom responses but rather the public DNS responses. Shouldn't DoT and DoH return the same responses as port 53? Took me a while to track this down. I have a device that attempts DoT on startup and will use DoT if available. For now, I've blocked port 853 for that device then it drops down to plain 53, but thinking that all 3 of plain, DoT and DoH should return the custom responses? -
Hello, I've tried searching the forums for anything similar to the behavior I'm noticing but it seems no one has experienced / posted about this, or maybe I missed it. The issue: Selected IP layer is IPv4, xxxx_airdns.org is currently returning IPv4 via dig which is great but when connecting to it, IPv6 is used. Expectation: Airdns.org DDNS service should adhere to the selected IP layer (IPv4, IPv6 or IPv4+IPv6) and only create the relevant A and/or AAAA records. I spent several hours yesterday troubleshooting the router's iptables/nat script, which I know works 100%, only to realize that using the DDNS hostname was the culprit. As soon as I switched my connecting device to use the IPv4 address did it start working! ➜ ~ dig xxxx.airdns.org ; <<>> DiG 9.10.6 <<>> xxxx.airdns.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40918 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;xxxx.airdns.org. IN A ;; ANSWER SECTION: xxxx.airdns.org. 15 IN A 37.46.199.87 ;; Query time: 2 msec ;; SERVER: 10.10.10.1#53(10.10.10.1) ;; WHEN: Sat Feb 14 12:43:35 +04 2026 ;; MSG SIZE rcvd: 61 ➜ ~ telnet xxxx.airdns.org 12345 Trying 2a00:dd0:aaaa:X:XXX:XXXX:XXXX:XXXX...
-
Default DNS not resolving existing domain
Tech Jedi Alex replied to Nikolozik's topic in Blocked websites warning
Can reproduce. ❯ dig a in www.magticom.ge ; <<>> DiG 9.20.17 <<>> a in www.magticom.ge ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 43225 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ; EDE: 22 (No Reachable Authority): (delegation magticom.ge) ;; QUESTION SECTION: ;www.magticom.ge. IN A ;; Query time: 3205 msec ;; SERVER: 10.76.134.1#53(10.76.134.1) (UDP) ;; WHEN: Fri Jan 16 19:13:01 CET 2026 ;; MSG SIZE rcvd: 72 ~ took 3s . -
Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: Note: --data-ciphers-fallback with cipher 'AES-256-CBC' disables data channel offload. Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: OpenVPN 2.6.14 aarch64-openwrt-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] [DCO] Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: library versions: OpenSSL 3.0.18 30 Sep 2025, LZO 2.10 Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: DCO version: N/A Mon Dec 15 10:16:00 2025 daemon.warn openvpn(airvpn)[3559]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: TCP/UDP: Preserving recently used remote address: [AF_INET]194.187.251.90:443 Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: Socket Buffers: R=[131072->131072] S=[16384->16384] Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: Attempting to establish TCP connection with [AF_INET]194.187.251.90:443 Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: TCP connection established with [AF_INET]194.187.251.90:443 Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: TCPv4_CLIENT link local: (not bound) Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: TCPv4_CLIENT link remote: [AF_INET]194.187.251.90:443 Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: TLS: Initial packet from [AF_INET]194.187.251.90:443, sid=045ec4f4 d2c2a118 Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: VERIFY KU OK Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: Validating certificate extended key usage Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: VERIFY EKU OK Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Capricornus, emailAddress=info@airvpn.org Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, peer certificate: 4096 bits RSA, signature: RSA-SHA512, peer temporary key: 253 bits X25519 Mon Dec 15 10:16:00 2025 daemon.notice openvpn(airvpn)[3559]: [Capricornus] Peer Connection Initiated with [AF_INET]194.187.251.90:443 Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1 Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: TLS: tls_multi_process: initial untrusted session promoted to trusted Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: SENT CONTROL [Capricornus]: 'PUSH_REQUEST' (status=1) Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.12.177.1,dhcp-option DNS6 fde6:7a:7d20:8b1::1,tun-ipv6,route-gateway 10.12.177.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:7d20:8b1::1000/64 fde6:7a:7d20:8b1::1,ifconfig 10.12.177.2 255.255.255.0,peer-id 0,cipher CHACHA20-POLY1305,protocol-flags cc-exit tls-ekm dyn-tls-crypt,tun-mtu 1500' Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: OPTIONS IMPORT: --ifconfig/up options modified Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: OPTIONS IMPORT: route options modified Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: OPTIONS IMPORT: route-related options modified Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: OPTIONS IMPORT: tun-mtu set to 1500 Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: net_route_v4_best_gw query: dst 0.0.0.0 Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: net_route_v4_best_gw result: via 192.168.8.8 dev wan Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: GDG6: remote_host_ipv6=n/a Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: net_route_v6_best_gw query: dst :: Mon Dec 15 10:16:01 2025 daemon.warn openvpn(airvpn)[3559]: sitnl_send: rtnl: generic error (-101): Network unreachable Mon Dec 15 10:16:01 2025 daemon.notice netifd: Interface 'airvpn' is enabled Mon Dec 15 10:16:01 2025 daemon.notice netifd: Network device 'tun0' link is up Mon Dec 15 10:16:01 2025 daemon.notice netifd: Interface 'airvpn' has link connectivity Mon Dec 15 10:16:01 2025 daemon.notice netifd: Interface 'airvpn' is setting up now Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: TUN/TAP device tun0 opened Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: net_iface_mtu_set: mtu 1500 for tun0 Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: net_iface_up: set tun0 up Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: net_addr_v4_add: 10.12.177.2/24 dev tun0 Mon Dec 15 10:16:01 2025 daemon.notice netifd: Interface 'airvpn' is now up Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: net_iface_mtu_set: mtu 1500 for tun0 Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: net_iface_up: set tun0 up Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: net_addr_v6_add: fde6:7a:7d20:8b1::1000/64 dev tun0 Mon Dec 15 10:16:01 2025 daemon.warn openvpn(airvpn)[3559]: sitnl_send: rtnl: generic error (-13): Permission denied Mon Dec 15 10:16:01 2025 daemon.err openvpn(airvpn)[3559]: Linux can't add IPv6 to interface tun0 Mon Dec 15 10:16:01 2025 daemon.notice openvpn(airvpn)[3559]: Exiting due to fatal error Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan Mon Dec 15 10:16:01 2025 daemon.notice netifd: Interface 'airvpn' is now down Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind Mon Dec 15 10:16:01 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan Mon Dec 15 10:16:01 2025 user.notice firewall: Reloading firewall due to ifup of airvpn (tun0) Mon Dec 15 10:16:01 2025 daemon.notice netifd: Interface 'airvpn' is disabled Mon Dec 15 10:16:01 2025 daemon.notice netifd: Network device 'tun0' link is down Mon Dec 15 10:16:01 2025 daemon.notice netifd: Interface 'airvpn' has link connectivity loss
-
ANSWERED Security Issue - DNS leak via Firefox/Waterfox
Staff replied to Kunuyana's topic in Troubleshooting and Problems
Hello! This does not seem to be the case, the DNS query is tunneled, even when the destination is an "alien" DNS. If you have gathered evidence that in some way the DNS query is tunneled outside the VPN tunnel (with Network Lock enabled) can you please tell us how to reproduce step by step so we can re-check with tools like Wireshark? The only thing we can think of is when Firefox forces a DNS query to the gateway, the gateway is your router, and you keep your own ISP DNS configured on the router (so DNS queries to the router are not blocked by Network Lock, which allows anything to the router, and then the router forwards the DNS query to your ISP DNS), is this your case? Kind regards -
Hello! That's correct, the routing and the firewall rules are not infringed and the queries are not treated differently. However, you may create specific environments where DNS queries are not tunneled even when everything is properly set up and Network Lock is enabled. A typical example is when you force your router address as DNS server of the machine connected to the Internet. Network Lock won't stop the traffic to this router, thus DNS query will go to the router (outside the VPN tunnel, according to the table) and then the router will forward it on to the Internet from its physical network interface with its "real" (ISP assigned) IP address. The system is adhering precisely to what it has been told to do, so it is not a DNS leak, but at the end of the day the outcome is equivalent on the client's point of view. Yes, good solution at a first glance. BIND, dnsmasq, Unbound and PowerDNS offer this feature. Kind regards
-
So openvpn config now has: pull-filter ignore "ifconfig-ipv6" pull-filter ignore "route-ipv6" pull-filter ignore "redirect-gateway ipv6" pull-filter ignore "dhcp-option DNS6" pull-filter ignore "tun-ipv6" pull-filter ignore "redirect-gateway" redirect-gateway def1 bypass-dhcp And the log is: Sat Dec 20 11:34:18 2025 daemon.notice netifd: Interface 'wan' is now up Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind Sat Dec 20 11:34:18 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan Sat Dec 20 11:34:18 2025 user.notice firewall: Reloading firewall due to ifup of wan (wan) Sat Dec 20 11:34:19 2025 daemon.warn openvpn(airvpn)[2294]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TCP/UDP: Preserving recently used remote address: [AF_INET]194.187.251.90:443 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Socket Buffers: R=[131072->131072] S=[16384->16384] Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Attempting to establish TCP connection with [AF_INET]194.187.251.90:443 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TCP connection established with [AF_INET]194.187.251.90:443 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TCPv4_CLIENT link local: (not bound) Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TCPv4_CLIENT link remote: [AF_INET]194.187.251.90:443 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TLS: Initial packet from [AF_INET]194.187.251.90:443, sid=a904da59 0707d733 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: VERIFY KU OK Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Validating certificate extended key usage Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: VERIFY EKU OK Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Columba, emailAddress=info@airvpn.org Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, peer certificate: 4096 bits RSA, signature: RSA-SHA512, peer temporary key: 253 bits X25519 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: [Columba] Peer Connection Initiated with [AF_INET]194.187.251.90:443 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TLS: tls_multi_process: initial untrusted session promoted to trusted Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.14.145.1,dhcp-option DNS6 fde6:7a:7d20:a91::1,tun-ipv6,route-gateway 10.14.145.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:7d20:a91::1000/64 fde6:7a:7d20:a91::1,ifconfig 10.14.145.2 255.255.255.0,peer-id 0,cipher CHACHA20-POLY1305,protocol-flags cc-exit tls-ekm dyn-tls-crypt,tun-mtu 1500' Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Pushed option removed by filter: 'redirect-gateway ipv6 def1 bypass-dhcp' Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Pushed option removed by filter: 'dhcp-option DNS6 fde6:7a:7d20:a91::1' Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Pushed option removed by filter: 'tun-ipv6' Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Pushed option removed by filter: 'ifconfig-ipv6 fde6:7a:7d20:a91::1000/64 fde6:7a:7d20:a91::1' Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: OPTIONS IMPORT: --ifconfig/up options modified Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: OPTIONS IMPORT: route-related options modified Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: OPTIONS IMPORT: tun-mtu set to 1500 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_route_v4_best_gw query: dst 0.0.0.0 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_route_v4_best_gw result: via 192.168.1.1 dev wan Sat Dec 20 11:34:19 2025 daemon.notice netifd: Interface 'airvpn' is enabled Sat Dec 20 11:34:19 2025 daemon.notice netifd: Network device 'tun0' link is up Sat Dec 20 11:34:19 2025 daemon.notice netifd: Interface 'airvpn' has link connectivity Sat Dec 20 11:34:19 2025 daemon.notice netifd: Interface 'airvpn' is setting up now Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: TUN/TAP device tun0 opened Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_iface_mtu_set: mtu 1500 for tun0 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_iface_up: set tun0 up Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_addr_v4_add: 10.14.145.2/24 dev tun0 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: /usr/libexec/openvpn-hotplug up airvpn tun0 1500 0 10.14.145.2 255.255.255.0 init Sat Dec 20 11:34:19 2025 daemon.notice netifd: Interface 'airvpn' is now up Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_route_v4_add: 194.187.251.90/32 via 192.168.1.1 dev [NULL] table 0 metric -1 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_route_v4_add: 0.0.0.0/1 via 10.14.145.1 dev [NULL] table 0 metric -1 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: net_route_v4_add: 128.0.0.0/1 via 10.14.145.1 dev [NULL] table 0 metric -1 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Initialization Sequence Completed Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Data Channel: cipher 'CHACHA20-POLY1305', peer-id: 0, compression: 'stub' Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Timers: ping 10, ping-restart 60 Sat Dec 20 11:34:19 2025 daemon.notice openvpn(airvpn)[2294]: Protocol options: protocol-flags cc-exit tls-ekm dyn-tls-crypt Sat Dec 20 11:34:19 2025 daemon.info dnsmasq[1]: exiting on receipt of SIGTERM Sat Dec 20 11:34:19 2025 user.notice firewall: Reloading firewall due to ifup of airvpn (tun0) Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: started, version 2.90 cachesize 1000 Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: DNS service limited to local subnets Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: UBus support enabled: connected to system bus Sat Dec 20 11:34:24 2025 daemon.info dnsmasq-dhcp[1]: DHCP, IP range 192.168.8.100 -- 192.168.8.249, lease time 12h Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using nameserver 10.4.0.1#53 Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: read /etc/hosts - 12 names Sat Dec 20 11:34:24 2025 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 2 names Sat Dec 20 11:34:24 2025 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses I think log no longer shows an error, but does this look right? ipleak.net tells there is airvpn server DNS ipv6 reachable
-
ANSWERED AirVPN API - Status Endpoint Discussion
Tech Jedi Alex replied to Esurient's topic in General & Suggestions
You are technically not getting assigned the IP, you're using the address of the server. But anyway, entry and exit IP addresses have been separate since time immemorial, the latter of which is irrelevant for clients wanting to connect, so it's not emitted by the status API. There are two ways to get that info, though. Query servername_exit.airservers.org. This one is used by Eddie for route checks. When connected, curl check.airservers.org (with /api for JSON, and prepend ipv4./ipv6. for specific IP version), see Specs, section VPN DNS Server > Special resolution & URLs. Actually, I was trying to find some documentation on that separation, but neither the FAQ nor the specs mention this. But it's in every server and sale announcement. Little bit of inconsistency there. So, now you know. -
ANSWERED AirVPN API - Status Endpoint Discussion
Esurient replied to Esurient's topic in General & Suggestions
That was just an example, I did a check now on Germany, Adhil, Connected I have the IP 37.46.199.70, however reading the status API only 37.46.199.66, 37.46.199.67, 37.46.199.68 and 37.46.199.69 are exposed in the IPv4 entry whilst the client is stating it is using entry 3 (x.68), If I'm not wrong, if I were to do a DNS query on all DE servers, I get dig ANY de.all.vpn.airdns.org @dns1.airvpn.org +short 141.98.102.234 185.189.112.18 83.143.245.50 185.189.112.26 37.46.199.50 185.104.184.42 37.46.199.66 37.46.199.82 141.98.102.178 37.120.217.242 141.98.102.186 141.98.102.242 141.98.102.226 185.189.112.10 On the IPv4 section, which still does not match up the IP address I'm assigned. Edit: I have geo routing disabled. -
Is blacklisting for Air IP addresses getting worse?
Staff replied to inthemeantime's topic in Blocked websites warning
Do any readers know whether it is would be normal for VPN providers to liaise with the biggest blocklists? (I would imagine it would be a lot of manual work, so I could understand why Air would not want to take it on). Hello! We confirm that we actively keep "our" IP addresses out of major blacklists, including the sector leader Spamhaus. Most address providers mandate that this is done as they want to keep their addresses "clean". Unfortunately there are thousands of black lists so it is not possible to know and intervene on all of them. About the IP address you mention, you can see here that it's "clean" on almost 100% of the minor black lists and on 100% of the major ones. https://check.spamhaus.org/results/?query=213.152.187.235 https://whatismyipaddress.com/blacklist-check https://dnschecker.org/ip-blacklist-checker.php?query=213.152.187.235 https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a213.152.187.235&run=toolpage Also, please be aware that some minor lists that you see above include an IP address simply because it is shared, regardless of anything else. Kind regards -
Hey. Would you consider adding a single server query to the status API (e.g. api/status/?server=server_name)? It seems a bit wasteful to pull the whole list if you just want stats for a single server. BR
-
Hi All, I noticed my IP wasn't an AirVPN one and went to investigate on my Router (Asus RT-AC86U with Asuswrt-Merlin) in the logs I see this: Nov 28 13:40:45 rc_service: httpd 1285:notify_rc start_vpnclient1 Nov 28 13:40:45 ovpn-client1[6359]: OpenVPN 2.6.12 arm-buildroot-linux-gnueabi [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] Nov 28 13:40:45 ovpn-client1[6359]: library versions: OpenSSL 1.1.1w 11 Sep 2023, LZO 2.08 Nov 28 13:40:45 ovpn-client1[6360]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Nov 28 13:40:45 ovpn-client1[6360]: TCP/UDP: Preserving recently used remote address: [AF_INET]217.138.195.29:443 Nov 28 13:40:45 ovpn-client1[6360]: Socket Buffers: R=[524288->524288] S=[524288->524288] Nov 28 13:40:45 ovpn-client1[6360]: UDPv4 link local: (not bound) Nov 28 13:40:45 ovpn-client1[6360]: UDPv4 link remote: [AF_INET]217.138.195.29:443 Nov 28 13:40:45 ovpn-client1[6360]: TLS: Initial packet from [AF_INET]217.138.195.29:443, sid=a9e4ee30 6de459b1 Nov 28 13:40:45 ovpn-client1[6360]: VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org Nov 28 13:40:45 ovpn-client1[6360]: VERIFY KU OK Nov 28 13:40:45 ovpn-client1[6360]: Validating certificate extended key usage Nov 28 13:40:45 ovpn-client1[6360]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Nov 28 13:40:45 ovpn-client1[6360]: VERIFY EKU OK Nov 28 13:40:45 ovpn-client1[6360]: VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Betelgeuse, emailAddress=info@airvpn.org Nov 28 13:40:45 ovpn-client1[6360]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, peer certificate: 4096 bits RSA, signature: RSA-SHA512, peer temporary key: 253 bits X25519 Nov 28 13:40:45 ovpn-client1[6360]: [Betelgeuse] Peer Connection Initiated with [AF_INET]217.138.195.29:443 Nov 28 13:40:45 ovpn-client1[6360]: TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1 Nov 28 13:40:45 ovpn-client1[6360]: TLS: tls_multi_process: initial untrusted session promoted to trusted Nov 28 13:40:46 ovpn-client1[6360]: SENT CONTROL [Betelgeuse]: 'PUSH_REQUEST' (status=1) Nov 28 13:40:46 ovpn-client1[6360]: PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.11.214.1,dhcp-option DNS6 fde6:7a:7d20:7d6::1,tun-ipv6,route-gateway 10.11.214.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:7d20:7d6::1015/64 fde6:7a:7d20:7d6::1,ifconfig 10.11.214.23 255.255.255.0,peer-id 2,cipher CHACHA20-POLY1305,protocol-flags cc-exit tls-ekm dyn-tls-crypt,tun-mtu 1500' Nov 28 13:40:46 ovpn-client1[6360]: OPTIONS IMPORT: --ifconfig/up options modified Nov 28 13:40:46 ovpn-client1[6360]: OPTIONS IMPORT: route options modified Nov 28 13:40:46 ovpn-client1[6360]: OPTIONS IMPORT: route-related options modified Nov 28 13:40:46 ovpn-client1[6360]: OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Nov 28 13:40:46 ovpn-client1[6360]: OPTIONS IMPORT: tun-mtu set to 1500 Nov 28 13:40:46 ovpn-client1[6360]: GDG6: remote_host_ipv6=n/a Nov 28 13:40:46 ovpn-client1[6360]: net_route_v6_best_gw query: dst :: Nov 28 13:40:46 ovpn-client1[6360]: net_route_v6_best_gw result: via :: dev lo Nov 28 13:40:46 ovpn-client1[6360]: TUN/TAP device tun11 opened Nov 28 13:40:46 ovpn-client1[6360]: TUN/TAP TX queue length set to 1000 Nov 28 13:40:46 ovpn-client1[6360]: /usr/sbin/ip link set dev tun11 up mtu 1500 Nov 28 13:40:46 ovpn-client1[6360]: /usr/sbin/ip link set dev tun11 up Nov 28 13:40:46 ovpn-client1[6360]: /usr/sbin/ip addr add dev tun11 10.11.214.23/24 Nov 28 13:40:46 ovpn-client1[6360]: Linux ip addr add failed: external program exited with error status: 2 Nov 28 13:40:46 ovpn-client1[6360]: Exiting due to fatal error When I ssh onto the router and issue that last ip addr command I get this admin@RT-AC86U-44E0:/tmp/home/root# ip addr add dev tun11 10.11.214.23/24 RTNETLINK answers: File exists ip addr show shows 21 entries but only 1 for tun11: 21: tun11: <NO-CARRIER,POINTOPOINT,MULTICAST,NOARP,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/none inet 10.11.214.23/24 scope global tun11 valid_lft forever preferred_lft forever admin@RT-AC86U-44E0:/tmp/home/root# Strangely the pid of the openvpn process keeps ramping up as though it's constantly failing and restarting? admin@RT-AC86U-44E0:/tmp/home/root# ps | grep openvpn 22350 admin 3332 S grep openvpn admin@RT-AC86U-44E0:/tmp/home/root# ps | grep openvpn 22456 admin 3332 S grep openvpn admin@RT-AC86U-44E0:/tmp/home/root# Any ideas? I've not changed anything to cause this, I've just updated to the latest firmware. Rebooted loads of times etc. Cheers!
-
ANSWERED IPs Range for WG server
Tech Jedi Alex replied to larod241's topic in General & Suggestions
Specs, section Assigned IPs: For the entry IPs, use a DNS query: $ dig a in +short de3.all.vpn.airdns.org 141.98.102.245 141.98.102.189 141.98.102.181 185.189.112.21 37.46.199.68 141.98.102.237 37.46.199.52 185.189.112.29 83.143.245.53 37.120.217.245 141.98.102.229 37.46.199.84 185.104.184.45 185.189.112.13 $ dig aaaa in +short de3.all.vpn.airdns.org 2001:ac8:20:98:ba0a:dabc:45a8:c67c 2a00:dd0:aaaa:7:e021:9b15:8027:f809 2001:ac8:36:3:2935:d57f:fc05:83e0 2001:ac8:20:96:226a:3a84:c3d8:dba8 2001:ac8:20:2b:d428:2f9d:4c0a:77b8 2001:ac8:20:225:1b06:18f:a622:b2af 2001:ac8:20:97:dad1:f205:28f1:bff5 2001:ac8:20:2a:818d:602e:cf31:f199 2001:ac8:20:99:fbf6:b62a:86df:b560 2001:ac8:20:2c:8efe:ed7:7e97:6f97 2001:ac8:20:5:623e:50fc:8023:a65 2a00:dd0:aaaa:9:2a94:d040:418f:de4a 2001:ac8:20:9a:13e6:576a:41cb:a5f 2a00:dd0:aaaa:8:486b:fb23:5878:32ea . -
I recently noticed that i can't visit any *.mil websites when I'm using AirVPN with Wireguard client for MacOS. Config file downloaded from Client page looks like this: [Interface] PrivateKey = ... Address = ... DNS = 10.128.0.1 MTU = 1320 [Peer] ... dig command returned with SERVFAIL: ~ > dig @10.128.0.1 www.navy.mil ; <<>> DiG 9.10.6 <<>> @10.128.0.1 www.navy.mil ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 51388 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;www.navy.mil. IN A ;; Query time: 2554 msec ;; SERVER: 10.128.0.1#53(10.128.0.1) ;; WHEN: ;; MSG SIZE rcvd: 41 But it works fine with if i choose Mullvad (also wireguard): ~ > dig www.navy.mil ; <<>> DiG 9.10.6 <<>> www.navy.mil ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17697 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;www.navy.mil. IN A ;; ANSWER SECTION: www.navy.mil. 7138 IN CNAME www.navy.mil.edgekey.net. www.navy.mil.edgekey.net. 300 IN CNAME e16312.dscb.akamaiedge.net. e16312.dscb.akamaiedge.net. 20 IN A 23.15.145.170 ;; Query time: 597 msec ;; SERVER: 100.64.0.7#53(100.64.0.7) ;; WHEN: ;; MSG SIZE rcvd: 132 On a semi-related note: my Opnsense router running Unbound in DNS-over-TLS forwarding mode to upstream DNS servers also got exactly same error: SERVFAIL or straight up timeout with dig command for *.mil domains. Upstream queries go through WAN and not any VPN tunnel. Turning DNSSEC on and off didn't change anything on my opnsense router. If i don't use DNS-over-TLS and just plain forwarding to UDP 53, no issue. I don't know how relevant these two issues are, perhaps AirVPN also use Unbound? Once you find out what's wrong, can you drop some info so i can also fix my Opnsense settings? Thank you!
-
To illustrate a potential privacy risk with port forwarding, consider this hypothetical scenario. Strike 3 Holdings automatically monitors copyright infringement, logging an IP address, timestamp, port, and the port's open status. The IP belongs to an AirVPN server, which would normally halt legal action. However, in this case, Strike 3 Holdings obtains a court order. The order compels AirVPN to identify the user connected to the server at the time of infringement and using the forwarded port in question. In response, AirVPN staff would identify the IP's port pool and query their database for the user account currently forwarding that port. Because AirVPN offers static port forwarding, this query would likely identify the infringer's account. This alone is insufficient for disclosure. The port could have been relinquished after the infringement, and AirVPN keeps no historical port forwarding logs. Users can also change port configurations during a session. A more detailed examination, however, reveals a problem. Port forwarding can only be managed via the AirVPN website, which logs login dates and basic browser information for security purposes. The hypothetical user, Joe Smith, has not logged in since initially configuring his forwarded ports long ago. The timestamp of the infringement is more recent than the last recorded login for the account holding the forwarded port. This creates compelling evidence that the account owner continuously held that port forwarding rule since their last login. AirVPN would then be compelled to provide Joe's username, login history, current ports, origin IPs, and payment transaction IDs. With this information, Strike 3 Holdings can subpoena payment processors and ISPs to uncover Joe Smith's identity.
-
Hello! I recently got AirVPN and have been using it to torrent, it's been working somewhat well until I realized the server I was using had god awful speeds (for reference I have gig speeds and it was giving me 50mbps up/down). So I wanted to change my config to another server, now the routers OpenVPN won't connect at all to the server. I uploaded multiple different configs and all say the same error, I've also tried different OPVN versions and have confirmed that my router uses v2.6. But everytime I try to connect it gives me an error of "ovpn-client1[7647]: sitnl_send: rtnl: generic error (-101): Network is unreachable" Would anyone know whats going on? Thanks! Full log: Oct 16 10:44:35 ovpn-client1[7646]: OpenVPN 2.6.14 arm-buildroot-linux-gnueabi [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] Oct 16 10:44:35 ovpn-client1[7646]: library versions: OpenSSL 1.1.1w 11 Sep 2023, LZO 2.10 Oct 16 10:44:35 ovpn-client1[7647]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Oct 16 10:44:40 ovpn-client1[7647]: TCP/UDP: Preserving recently used remote address: [AF_INET]198.54.129.62:443 Oct 16 10:44:40 ovpn-client1[7647]: Socket Buffers: R=[524288->524288] S=[524288->524288] Oct 16 10:44:40 ovpn-client1[7647]: UDPv4 link local: (not bound) Oct 16 10:44:40 ovpn-client1[7647]: UDPv4 link remote: [AF_INET]198.54.129.62:443 Oct 16 10:44:40 ovpn-client1[7647]: TLS: Initial packet from [AF_INET]198.54.129.62:443, sid=b357b073 5b5c838a Oct 16 10:44:40 ovpn-client1[7647]: VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org Oct 16 10:44:40 ovpn-client1[7647]: VERIFY KU OK Oct 16 10:44:40 ovpn-client1[7647]: Validating certificate extended key usage Oct 16 10:44:40 ovpn-client1[7647]: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication Oct 16 10:44:40 ovpn-client1[7647]: VERIFY EKU OK Oct 16 10:44:40 ovpn-client1[7647]: VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Sarin, emailAddress=info@airvpn.org Oct 16 10:44:41 ovpn-client1[7647]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, peer certificate: 4096 bits RSA, signature: RSA-SHA512, peer temporary key: 253 bits X25519 Oct 16 10:44:41 ovpn-client1[7647]: [Sarin] Peer Connection Initiated with [AF_INET]198.54.129.62:443 Oct 16 10:44:41 ovpn-client1[7647]: TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1 Oct 16 10:44:41 ovpn-client1[7647]: TLS: tls_multi_process: initial untrusted session promoted to trusted Oct 16 10:44:42 ovpn-client1[7647]: SENT CONTROL [Sarin]: 'PUSH_REQUEST' (status=1) Oct 16 10:44:42 ovpn-client1[7647]: PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.17.26.1,dhcp-option DNS6 fde6:7a:7d20:d1a::1,tun-ipv6,route-gateway 10.17.26.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:7d20:d1a::1055/64 fde6:7a:7d20:d1a::1,ifconfig 10.17.26.87 255.255.255.0,peer-id 9,cipher CHACHA20-POLY1305,protocol-flags cc-exit tls-ekm dyn-tls-crypt,tun-mtu 1500' Oct 16 10:44:42 ovpn-client1[7647]: OPTIONS IMPORT: --ifconfig/up options modified Oct 16 10:44:42 ovpn-client1[7647]: OPTIONS IMPORT: route options modified Oct 16 10:44:42 ovpn-client1[7647]: OPTIONS IMPORT: route-related options modified Oct 16 10:44:42 ovpn-client1[7647]: OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Oct 16 10:44:42 ovpn-client1[7647]: OPTIONS IMPORT: tun-mtu set to 1500 Oct 16 10:44:42 ovpn-client1[7647]: GDG6: remote_host_ipv6=n/a Oct 16 10:44:42 ovpn-client1[7647]: net_route_v6_best_gw query: dst :: Oct 16 10:44:42 ovpn-client1[7647]: sitnl_send: rtnl: generic error (-101): Network is unreachable Oct 16 10:44:42 ovpn-client1[7647]: TUN/TAP device tun11 opened Oct 16 10:44:42 ovpn-client1[7647]: TUN/TAP TX queue length set to 1000 Oct 16 10:44:42 ovpn-client1[7647]: /usr/sbin/ip link set dev tun11 up mtu 1500 Oct 16 10:44:42 ovpn-client1[7647]: /usr/sbin/ip link set dev tun11 up Oct 16 10:44:42 ovpn-client1[7647]: /usr/sbin/ip addr add dev tun11 10.17.26.87/24 Oct 16 10:44:42 ovpn-client1[7647]: /usr/sbin/ip link set dev tun11 up mtu 1500 Oct 16 10:44:42 ovpn-client1[7647]: /usr/sbin/ip link set dev tun11 up Oct 16 10:44:42 ovpn-client1[7647]: /usr/sbin/ip -6 addr add fde6:7a:7d20:d1a::1055/64 dev tun11 Oct 16 10:44:42 ovpn-client1[7647]: Linux ip -6 addr add failed: external program exited with error status: 2 Oct 16 10:44:42 ovpn-client1[7647]: Exiting due to fatal error
-
Linux: AirVPN Suite 2.0.0 preview available
colorman replied to Staff's topic in News and Announcement
Hi Staff, I was trying out the latest version. Normally I use wireguard and that always works fine, also closing with Ctrl + C. However, if I use ./goldcrest AirVPN_Belgium_UDP-443-Entry3.ovpn and then close with Ctrl + C, Bluetit stops. Have to restart pc and do ./goldcrest --recover-network. some log files Wachtwoord: localhost:~ # journalctl bluetit.service Failed to add match 'bluetit.service': Invalid argument localhost:~ # journalctl -xeu bluetit.service Jul 05 18:07:20 localhost systemd[1]: Starting AirVPN Bluetit Daemon... ░░ Subject: A start job for unit bluetit.service has begun execution ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit bluetit.service has begun execution. ░░ ░░ The job identifier is 309. Jul 05 18:07:20 localhost bluetit[1879]: Starting Bluetit - AirVPN WireGuard/OpenVPN3 Service 2.0.0 RC 2 - 9 > Jul 05 18:07:20 localhost bluetit[1879]: OpenVPN core 3.12 AirVPN (20250606) linux x86_64 64-bit Jul 05 18:07:20 localhost bluetit[1879]: Copyright (C) 2012- OpenVPN Inc. All rights reserved. Jul 05 18:07:20 localhost bluetit[1879]: SSL Library: OpenSSL 3.1.4 24 Oct 2023 Jul 05 18:07:20 localhost bluetit[1879]: AirVPN WireGuard Client 2.0.0 Linux x86_64 64-bit Jul 05 18:07:20 localhost bluetit[1890]: Bluetit daemon started with PID 1890 Jul 05 18:07:20 localhost bluetit[1890]: Reading run control directives from file /etc/airvpn/bluetit.rc Jul 05 18:07:20 localhost bluetit[1890]: External network is reachable via IPv4 gateway 192.168.178.1 through> Jul 05 18:07:20 localhost bluetit[1890]: Successfully connected to D-Bus Jul 05 18:07:20 localhost systemd[1]: Started AirVPN Bluetit Daemon. ░░ Subject: A start job for unit bluetit.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit bluetit.service has finished successfully. ░░ ░░ The job identifier is 309. Jul 05 18:07:20 localhost bluetit[1890]: IPv6 is available in this system Jul 05 18:07:20 localhost bluetit[1890]: Creating AirVPN Boot server list Jul 05 18:07:20 localhost bluetit[1890]: Added server http://63.33.78.166 Jul 05 18:07:20 localhost bluetit[1890]: Added server http://54.93.175.114 Jul 05 18:07:20 localhost bluetit[1890]: Added server http://82.196.3.205 Jul 05 18:07:20 localhost bluetit[1890]: Added server http://63.33.116.50 Jul 05 18:07:20 localhost bluetit[1890]: Added server http://[2a03:b0c0:0:1010::9b:c001] Jul 05 18:07:20 localhost bluetit[1890]: Added server http://bootme.org Jul 05 18:07:20 localhost bluetit[1890]: Boot server http://bootme.org resolved into IPv6 2a03:b0c0:0:1010::9> Jul 05 18:07:20 localhost bluetit[1890]: AirVPN Boot server list successfully created. Added 6 servers. Jul 05 18:07:20 localhost bluetit[1890]: Default VPN type for AirVPN connections is set to WireGuard Jul 05 18:07:20 localhost bluetit[1890]: Use of user VPN profiles is enabled by Bluetit policy Jul 05 18:07:20 localhost bluetit[1890]: Bluetit successfully initialized and ready Jul 05 18:07:20 localhost bluetit[1890]: Scanning for system DNS addresses Jul 05 18:07:20 localhost bluetit[1890]: Found system IPv4 DNS 84.116.46.20 Jul 05 18:07:20 localhost bluetit[1890]: Found system IPv4 DNS 84.116.46.21 Jul 05 18:07:20 localhost bluetit[1890]: Found 2 system DNS addresses Jul 05 18:07:20 localhost bluetit[1890]: Checking AirVPN servers connectivity Jul 05 18:07:20 localhost bluetit[1890]: AirVPN connectivity attempt 1 in progress Jul 05 18:07:20 localhost bluetit[1890]: Successfully connected to AirVPN server 63.33.78.166 Jul 05 18:07:20 localhost bluetit[1890]: AirVPN servers connectivity successful Jul 05 18:07:20 localhost bluetit[1890]: Requesting network IP and country to AirVPN ipleak.net via secure co> Jul 05 18:07:20 localhost bluetit[1890]: ERROR: Cannot detect system location: Unknown error: Problem with th> Jul 05 18:07:20 localhost bluetit[1890]: AirVPN Manifest updater thread started Jul 05 18:07:20 localhost bluetit[1890]: Default AirVPN Manifest update interval is 15 minutes Jul 05 18:07:20 localhost bluetit[1890]: Updating AirVPN Manifest Jul 05 18:07:20 localhost bluetit[1890]: Trying connection to AirVPN bootstrap server at http://82.196.3.205 Jul 05 18:07:21 localhost bluetit[1890]: AirVPN Manifest successfully retrieved from server Jul 05 18:07:21 localhost bluetit[1890]: AirVPN Manifest update interval is now set to 30 minutes Jul 05 18:07:41 localhost bluetit[1890]: Requested method "version" Jul 05 18:07:41 localhost bluetit[1890]: Requested method "openvpn_info" Jul 05 18:07:42 localhost bluetit[1890]: Requested method "openvpn_copyright" Jul 05 18:07:42 localhost bluetit[1890]: Requested method "ssl_library_version" Jul 05 18:07:42 localhost bluetit[1890]: Requested method "wireguard_info" Jul 05 18:07:42 localhost bluetit[1890]: Requested method "recover_network: Bluetit does not need a network r> Jul 05 18:07:42 localhost bluetit[1890]: Sending event 'event_end_of_session' Jul 05 18:09:44 localhost bluetit[1890]: Requested method "version" Jul 05 18:09:44 localhost bluetit[1890]: Requested method "openvpn_info" Jul 05 18:09:44 localhost bluetit[1890]: Requested method "openvpn_copyright" Jul 05 18:09:44 localhost bluetit[1890]: Requested method "ssl_library_version" Jul 05 18:09:44 localhost bluetit[1890]: Requested method "wireguard_info" Jul 05 18:09:44 localhost bluetit[1890]: Requested method "reset_bluetit_options -> Bluetit options successfu> Jul 05 18:09:44 localhost bluetit[1890]: Requested method "set_options: client-name (client-name) -> Goldcres> Jul 05 18:09:44 localhost bluetit[1890]: Requested method "set_options: client-user (client-user) -> gerrit" Jul 05 18:09:44 localhost bluetit[1890]: Requested method "set_vpn_profile -> OK" Jul 05 18:09:44 localhost bluetit[1890]: Requested method "start_connection" Jul 05 18:09:44 localhost bluetit[1890]: Network filter and lock are using nftables Jul 05 18:09:44 localhost bluetit[1890]: Kernel module nf_tables is already loaded Jul 05 18:09:44 localhost bluetit[1890]: Network filter successfully initialized Jul 05 18:09:44 localhost bluetit[1890]: Private network is allowed to pass the network filter Jul 05 18:09:44 localhost bluetit[1890]: Ping output is allowed to pass the network filter Jul 05 18:09:44 localhost bluetit[1890]: IPv6 NDP is allowed to pass the network filter Jul 05 18:09:44 localhost bluetit[1890]: WireGuard connection successfully started Jul 05 18:09:44 localhost bluetit[1890]: Local interface lo - IPv4 127.0.0.1 IPv6 ::1 Jul 05 18:09:44 localhost bluetit[1890]: Local interface eth0 - IPv4 192.168.178.11 IPv6 2001:1c04:508:a800:b> Jul 05 18:09:44 localhost bluetit[1890]: Default IPv4 gateway via 192.168.178.1 dev eth0 Jul 05 18:09:44 localhost bluetit[1890]: Starting WireGuard synchronous connection Jul 05 18:09:44 localhost bluetit[1890]: Successfully loaded kernel module wireguard Jul 05 18:09:44 localhost bluetit[1890]: WireGuard client successfully created and initialized. Jul 05 18:09:44 localhost bluetit[1890]: Allowing system IPv4 DNS 84.116.46.20 to pass through the network fi> Jul 05 18:09:44 localhost bluetit[1890]: Allowing system IPv4 DNS 84.116.46.21 to pass through the network fi> Jul 05 18:09:45 localhost bluetit[1890]: Ping output is allowed to pass the network filter Jul 05 18:09:45 localhost bluetit[1890]: IPv6 NDP is allowed to pass the network filter Jul 05 18:09:45 localhost bluetit[1890]: Setting up WireGuard network interface tun0 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 0.0.0.0/0 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv6 ::/0 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 0.0.0.0/5 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 8.0.0.0/7 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 11.0.0.0/8 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 12.0.0.0/6 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 16.0.0.0/4 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 32.0.0.0/3 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 64.0.0.0/2 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 128.0.0.0/3 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 160.0.0.0/5 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 168.0.0.0/6 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 172.0.0.0/12 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 172.32.0.0/11 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 172.64.0.0/10 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 172.128.0.0/9 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 173.0.0.0/8 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 174.0.0.0/7 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 176.0.0.0/4 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 192.0.0.0/9 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 192.128.0.0/11 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 192.160.0.0/13 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 192.169.0.0/16 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 192.170.0.0/15 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 192.172.0.0/14 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 192.176.0.0/12 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 192.192.0.0/10 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 193.0.0.0/8 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 194.0.0.0/7 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 196.0.0.0/6 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 200.0.0.0/5 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 208.0.0.0/4 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv4 224.0.0.0/3 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv6 8000::/2 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv6 c000::/3 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv6 e000::/4 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv6 f000::/5 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv6 f800::/6 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv6 fc00::/8 Jul 05 18:09:45 localhost bluetit[1890]: Allowing IPv6 fe00::/7 Jul 05 18:09:45 localhost bluetit[1890]: WireGuard end point set to IPv4 91.207.57.117, port 1637 Jul 05 18:09:45 localhost bluetit[1890]: Successfully created WireGuard device tun0 Jul 05 18:09:45 localhost bluetit[1890]: WireGuard interface tun0 set to IPv4 10.131.115.146/32 Jul 05 18:09:45 localhost bluetit[1890]: WireGuard interface tun0 set to IPv6 fd7d:76ee:e68f:a993:487a:1ccd:1> Jul 05 18:09:45 localhost bluetit[1890]: WireGuard interface tun0 successfully configured Jul 05 18:09:45 localhost bluetit[1890]: MTU WireGuard network interface tun0 set to 1320 Jul 05 18:09:45 localhost bluetit[1890]: WireGuard network interface tun0 successfully initialized and ready Jul 05 18:09:45 localhost bluetit[1890]: Adding IPv4 server 91.207.57.117 to network filter Jul 05 18:09:46 localhost bluetit[1890]: Network filter and lock successfully activated Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 0.0.0.0/0 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv6 ::/0 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 0.0.0.0/5 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 8.0.0.0/7 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 11.0.0.0/8 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 12.0.0.0/6 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 16.0.0.0/4 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 32.0.0.0/3 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 64.0.0.0/2 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 128.0.0.0/3 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 160.0.0.0/5 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 168.0.0.0/6 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 172.0.0.0/12 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 172.32.0.0/11 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 172.64.0.0/10 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 172.128.0.0/9 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 173.0.0.0/8 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 174.0.0.0/7 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 176.0.0.0/4 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 192.0.0.0/9 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 192.128.0.0/11 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 192.160.0.0/13 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 192.169.0.0/16 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 192.170.0.0/15 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 192.172.0.0/14 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 192.176.0.0/12 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 192.192.0.0/10 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 193.0.0.0/8 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 194.0.0.0/7 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 196.0.0.0/6 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 200.0.0.0/5 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 208.0.0.0/4 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 224.0.0.0/3 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv6 8000::/2 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv6 c000::/3 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv6 e000::/4 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv6 f000::/5 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv6 f800::/6 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv6 fc00::/8 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv6 fe00::/7 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 128.0.0.0/1 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv6 8000::/1 dev tun0 Jul 05 18:09:46 localhost bluetit[1890]: Added route IPv4 91.207.57.117/32 via 192.168.178.1 dev eth0 Jul 05 18:09:46 localhost bluetit[1890]: Successfully initialized WireGuard device tun0 Jul 05 18:09:46 localhost bluetit[1890]: Connected to WireGuard server IPv4 91.207.57.117, port 1637 via tun0 Jul 05 18:09:46 localhost bluetit[1890]: VPN Server has pushed DNS IPv4 10.128.0.1 Jul 05 18:09:46 localhost bluetit[1890]: Setting pushed IPv4 DNS server 10.128.0.1 in resolv.conf Jul 05 18:09:46 localhost bluetit[1890]: VPN Server has pushed DNS IPv6 fd7d:76ee:e68f:a993::1 Jul 05 18:09:46 localhost bluetit[1890]: Setting pushed IPv6 DNS server fd7d:76ee:e68f:a993::1 in resolv.conf Jul 05 18:09:46 localhost bluetit[1890]: Server has pushed its own DNS. Rejecting system DNS from network fil> Jul 05 18:09:46 localhost bluetit[1890]: System IPv4 DNS 84.116.46.20 is now rejected by the network filter Jul 05 18:09:46 localhost bluetit[1890]: System IPv4 DNS 84.116.46.21 is now rejected by the network filter Jul 05 18:09:46 localhost bluetit[1890]: WireGuard connection monitor thread started Jul 05 18:09:46 localhost bluetit[1890]: Connected to AirVPN server Castor, Brussels (Belgium) IP address 91.> Jul 05 18:09:46 localhost bluetit[1890]: Pushed DNS: 10.128.0.1 (IPv4) fd7d:76ee:e68f:a993::1 (IPv6) Jul 05 18:09:46 localhost bluetit[1890]: Connection statistics updater thread started Jul 05 18:09:53 localhost bluetit[1890]: Requested method "bluetit_status -> Bluetit is connected to VPN (Wir> Jul 05 18:09:53 localhost bluetit[1890]: Requested method "stop_connection" Jul 05 18:09:53 localhost bluetit[1890]: Stopping WireGuard synchronous connection Jul 05 18:09:53 localhost bluetit[1890]: WireGuard connection monitor thread terminated Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 0.0.0.0/0 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv6 ::/0 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 0.0.0.0/5 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 8.0.0.0/7 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 11.0.0.0/8 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 12.0.0.0/6 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 16.0.0.0/4 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 32.0.0.0/3 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 64.0.0.0/2 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 128.0.0.0/3 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 160.0.0.0/5 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 168.0.0.0/6 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 172.0.0.0/12 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 172.32.0.0/11 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 172.64.0.0/10 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 172.128.0.0/9 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 173.0.0.0/8 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 174.0.0.0/7 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 176.0.0.0/4 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 192.0.0.0/9 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 192.128.0.0/11 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 192.160.0.0/13 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 192.169.0.0/16 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 192.170.0.0/15 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 192.172.0.0/14 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 192.176.0.0/12 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 192.192.0.0/10 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 193.0.0.0/8 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 194.0.0.0/7 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 196.0.0.0/6 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 200.0.0.0/5 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 208.0.0.0/4 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 224.0.0.0/3 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv6 8000::/2 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv6 c000::/3 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv6 e000::/4 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv6 f000::/5 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv6 f800::/6 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv6 fc00::/8 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv6 fe00::/7 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 128.0.0.0/1 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv6 8000::/1 dev tun0 Jul 05 18:09:53 localhost bluetit[1890]: Removed route IPv4 91.207.57.117/32 via 192.168.178.1 dev eth0 Jul 05 18:09:53 localhost bluetit[1890]: Disabling WireGuard network interface tun0 Jul 05 18:09:53 localhost bluetit[1890]: WireGuard network interface tun0 successfully disabled Jul 05 18:09:54 localhost bluetit[1890]: WireGuard successfully disconnected Jul 05 18:09:54 localhost bluetit[1890]: Successfully restored DNS settings Jul 05 18:09:54 localhost bluetit[1890]: Session network filter and lock rollback successful Jul 05 18:09:54 localhost bluetit[1890]: Connection statistics updater thread terminated Jul 05 18:09:54 localhost bluetit[1890]: Sending event 'event_disconnected' Jul 05 18:09:54 localhost bluetit[1890]: Connection time: 00:00:07 Jul 05 18:09:54 localhost bluetit[1890]: Total transferred Input data: 6,30 KB Jul 05 18:09:54 localhost bluetit[1890]: Total transferred Output data: 69,80 KB Jul 05 18:09:54 localhost bluetit[1890]: Max Input rate: 1,09 Kbit/s Jul 05 18:09:54 localhost bluetit[1890]: Max Output rate: 2,32 Kbit/s Jul 05 18:09:54 localhost bluetit[1890]: Session network filter and lock are now disabled Jul 05 18:09:54 localhost bluetit[1890]: Sending event 'event_end_of_session' Jul 05 18:09:54 localhost bluetit[1890]: Sending event 'event_end_of_session' Jul 05 18:09:58 localhost bluetit[1890]: Requested method "version" Jul 05 18:09:58 localhost bluetit[1890]: Requested method "openvpn_info" Jul 05 18:09:58 localhost bluetit[1890]: Requested method "openvpn_copyright" Jul 05 18:09:58 localhost bluetit[1890]: Requested method "ssl_library_version" Jul 05 18:09:58 localhost bluetit[1890]: Requested method "wireguard_info" Jul 05 18:09:58 localhost bluetit[1890]: Requested method "reset_bluetit_options -> Bluetit options successfu> Jul 05 18:09:58 localhost bluetit[1890]: Requested method "set_options: client-name (client-name) -> Goldcres> Jul 05 18:09:58 localhost bluetit[1890]: Requested method "set_options: client-user (client-user) -> gerrit" Jul 05 18:09:58 localhost bluetit[1890]: Requested method "set_vpn_profile -> OK" Jul 05 18:09:58 localhost bluetit[1890]: Requested method "start_connection" Jul 05 18:09:58 localhost bluetit[1890]: Network filter and lock are using nftables Jul 05 18:09:58 localhost bluetit[1890]: Kernel module nf_tables is already loaded Jul 05 18:09:58 localhost bluetit[1890]: Network filter successfully initialized Jul 05 18:09:58 localhost bluetit[1890]: Private network is allowed to pass the network filter Jul 05 18:09:58 localhost bluetit[1890]: Ping output is allowed to pass the network filter Jul 05 18:09:58 localhost bluetit[1890]: IPv6 NDP is allowed to pass the network filter Jul 05 18:09:58 localhost bluetit[1890]: WireGuard connection successfully started Jul 05 18:09:58 localhost bluetit[1890]: Local interface lo - IPv4 127.0.0.1 IPv6 ::1 Jul 05 18:09:58 localhost bluetit[1890]: Local interface eth0 - IPv4 192.168.178.11 IPv6 2001:1c04:508:a800:b> Jul 05 18:09:58 localhost bluetit[1890]: Default IPv4 gateway via 192.168.178.1 dev eth0 Jul 05 18:09:58 localhost bluetit[1890]: Starting WireGuard synchronous connection Jul 05 18:09:58 localhost bluetit[1890]: Kernel module wireguard is already loaded Jul 05 18:09:58 localhost bluetit[1890]: WireGuard client successfully created and initialized. Jul 05 18:09:58 localhost bluetit[1890]: Allowing system IPv4 DNS 84.116.46.20 to pass through the network fi> Jul 05 18:09:58 localhost bluetit[1890]: Allowing system IPv4 DNS 84.116.46.21 to pass through the network fi> Jul 05 18:09:59 localhost bluetit[1890]: Ping output is allowed to pass the network filter Jul 05 18:09:59 localhost bluetit[1890]: IPv6 NDP is allowed to pass the network filter Jul 05 18:09:59 localhost bluetit[1890]: Setting up WireGuard network interface tun0 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 0.0.0.0/0 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv6 ::/0 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 0.0.0.0/5 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 8.0.0.0/7 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 11.0.0.0/8 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 12.0.0.0/6 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 16.0.0.0/4 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 32.0.0.0/3 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 64.0.0.0/2 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 128.0.0.0/3 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 160.0.0.0/5 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 168.0.0.0/6 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 172.0.0.0/12 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 172.32.0.0/11 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 172.64.0.0/10 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 172.128.0.0/9 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 173.0.0.0/8 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 174.0.0.0/7 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 176.0.0.0/4 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 192.0.0.0/9 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 192.128.0.0/11 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 192.160.0.0/13 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 192.169.0.0/16 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 192.170.0.0/15 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 192.172.0.0/14 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 192.176.0.0/12 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 192.192.0.0/10 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 193.0.0.0/8 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 194.0.0.0/7 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 196.0.0.0/6 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 200.0.0.0/5 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 208.0.0.0/4 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv4 224.0.0.0/3 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv6 8000::/2 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv6 c000::/3 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv6 e000::/4 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv6 f000::/5 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv6 f800::/6 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv6 fc00::/8 Jul 05 18:09:59 localhost bluetit[1890]: Allowing IPv6 fe00::/7 Jul 05 18:09:59 localhost bluetit[1890]: WireGuard end point set to IPv4 91.207.57.117, port 1637 Jul 05 18:09:59 localhost bluetit[1890]: Successfully created WireGuard device tun0 Jul 05 18:09:59 localhost bluetit[1890]: WireGuard interface tun0 set to IPv4 10.131.115.146/32 Jul 05 18:09:59 localhost bluetit[1890]: WireGuard interface tun0 set to IPv6 fd7d:76ee:e68f:a993:487a:1ccd:1> Jul 05 18:09:59 localhost bluetit[1890]: WireGuard interface tun0 successfully configured Jul 05 18:09:59 localhost bluetit[1890]: MTU WireGuard network interface tun0 set to 1320 Jul 05 18:09:59 localhost bluetit[1890]: WireGuard network interface tun0 successfully initialized and ready Jul 05 18:09:59 localhost bluetit[1890]: Adding IPv4 server 91.207.57.117 to network filter Jul 05 18:10:00 localhost bluetit[1890]: Network filter and lock successfully activated Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 0.0.0.0/0 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv6 ::/0 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 0.0.0.0/5 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 8.0.0.0/7 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 11.0.0.0/8 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 12.0.0.0/6 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 16.0.0.0/4 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 32.0.0.0/3 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 64.0.0.0/2 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 128.0.0.0/3 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 160.0.0.0/5 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 168.0.0.0/6 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 172.0.0.0/12 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 172.32.0.0/11 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 172.64.0.0/10 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 172.128.0.0/9 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 173.0.0.0/8 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 174.0.0.0/7 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 176.0.0.0/4 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 192.0.0.0/9 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 192.128.0.0/11 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 192.160.0.0/13 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 192.169.0.0/16 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 192.170.0.0/15 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 192.172.0.0/14 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 192.176.0.0/12 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 192.192.0.0/10 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 193.0.0.0/8 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 194.0.0.0/7 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 196.0.0.0/6 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 200.0.0.0/5 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 208.0.0.0/4 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 224.0.0.0/3 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv6 8000::/2 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv6 c000::/3 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv6 e000::/4 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv6 f000::/5 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv6 f800::/6 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv6 fc00::/8 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv6 fe00::/7 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 128.0.0.0/1 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv6 8000::/1 dev tun0 Jul 05 18:10:00 localhost bluetit[1890]: Added route IPv4 91.207.57.117/32 via 192.168.178.1 dev eth0 Jul 05 18:10:00 localhost bluetit[1890]: Successfully initialized WireGuard device tun0 Jul 05 18:10:00 localhost bluetit[1890]: Connected to WireGuard server IPv4 91.207.57.117, port 1637 via tun0 Jul 05 18:10:00 localhost bluetit[1890]: VPN Server has pushed DNS IPv4 10.128.0.1 Jul 05 18:10:00 localhost bluetit[1890]: Setting pushed IPv4 DNS server 10.128.0.1 in resolv.conf Jul 05 18:10:00 localhost bluetit[1890]: VPN Server has pushed DNS IPv6 fd7d:76ee:e68f:a993::1 Jul 05 18:10:00 localhost bluetit[1890]: Setting pushed IPv6 DNS server fd7d:76ee:e68f:a993::1 in resolv.conf Jul 05 18:10:00 localhost bluetit[1890]: Server has pushed its own DNS. Rejecting system DNS from network fil> Jul 05 18:10:00 localhost bluetit[1890]: System IPv4 DNS 84.116.46.20 is now rejected by the network filter Jul 05 18:10:00 localhost bluetit[1890]: System IPv4 DNS 84.116.46.21 is now rejected by the network filter Jul 05 18:10:00 localhost bluetit[1890]: WireGuard connection monitor thread started Jul 05 18:10:00 localhost bluetit[1890]: Connected to AirVPN server Castor, Brussels (Belgium) IP address 91.> Jul 05 18:10:00 localhost bluetit[1890]: Pushed DNS: 10.128.0.1 (IPv4) fd7d:76ee:e68f:a993::1 (IPv6) Jul 05 18:10:00 localhost bluetit[1890]: Connection statistics updater thread started Jul 05 18:10:02 localhost bluetit[1890]: Requested method "bluetit_status -> Bluetit is connected to VPN (Wir> Jul 05 18:10:02 localhost bluetit[1890]: Requested method "stop_connection" Jul 05 18:10:02 localhost bluetit[1890]: Stopping WireGuard synchronous connection Jul 05 18:10:02 localhost bluetit[1890]: WireGuard connection monitor thread terminated Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 0.0.0.0/0 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv6 ::/0 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 0.0.0.0/5 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 8.0.0.0/7 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 11.0.0.0/8 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 12.0.0.0/6 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 16.0.0.0/4 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 32.0.0.0/3 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 64.0.0.0/2 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 128.0.0.0/3 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 160.0.0.0/5 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 168.0.0.0/6 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 172.0.0.0/12 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 172.32.0.0/11 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 172.64.0.0/10 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 172.128.0.0/9 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 173.0.0.0/8 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 174.0.0.0/7 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 176.0.0.0/4 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 192.0.0.0/9 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 192.128.0.0/11 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 192.160.0.0/13 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 192.169.0.0/16 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 192.170.0.0/15 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 192.172.0.0/14 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 192.176.0.0/12 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 192.192.0.0/10 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 193.0.0.0/8 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 194.0.0.0/7 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 196.0.0.0/6 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 200.0.0.0/5 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 208.0.0.0/4 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 224.0.0.0/3 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv6 8000::/2 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv6 c000::/3 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv6 e000::/4 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv6 f000::/5 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv6 f800::/6 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv6 fc00::/8 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv6 fe00::/7 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 128.0.0.0/1 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv6 8000::/1 dev tun0 Jul 05 18:10:02 localhost bluetit[1890]: Removed route IPv4 91.207.57.117/32 via 192.168.178.1 dev eth0 Jul 05 18:10:02 localhost bluetit[1890]: Disabling WireGuard network interface tun0 Jul 05 18:10:02 localhost bluetit[1890]: WireGuard network interface tun0 successfully disabled Jul 05 18:10:02 localhost bluetit[1890]: WireGuard successfully disconnected Jul 05 18:10:02 localhost bluetit[1890]: Successfully restored DNS settings Jul 05 18:10:03 localhost bluetit[1890]: Session network filter and lock rollback successful Jul 05 18:10:03 localhost bluetit[1890]: Sending event 'event_disconnected' Jul 05 18:10:03 localhost bluetit[1890]: Connection time: 00:00:02 Jul 05 18:10:03 localhost bluetit[1890]: Total transferred Input data: 6,30 KB Jul 05 18:10:03 localhost bluetit[1890]: Total transferred Output data: 69,80 KB Jul 05 18:10:03 localhost bluetit[1890]: Max Input rate: 1,09 Kbit/s Jul 05 18:10:03 localhost bluetit[1890]: Max Output rate: 2,32 Kbit/s Jul 05 18:10:03 localhost bluetit[1890]: Session network filter and lock are now disabled Jul 05 18:10:03 localhost bluetit[1890]: Sending event 'event_end_of_session' Jul 05 18:10:03 localhost bluetit[1890]: Sending event 'event_end_of_session' Jul 05 18:18:13 localhost bluetit[1890]: Requested method "version" Jul 05 18:18:13 localhost bluetit[1890]: Requested method "openvpn_info" Jul 05 18:18:13 localhost bluetit[1890]: Requested method "openvpn_copyright" Jul 05 18:18:13 localhost bluetit[1890]: Requested method "ssl_library_version" Jul 05 18:18:13 localhost bluetit[1890]: Requested method "wireguard_info" Jul 05 18:18:13 localhost bluetit[1890]: Requested method "reset_bluetit_options -> Bluetit options successfu> Jul 05 18:18:13 localhost bluetit[1890]: Requested method "set_options: client-name (client-name) -> Goldcres> Jul 05 18:18:13 localhost bluetit[1890]: Requested method "set_options: client-user (client-user) -> gerrit" Jul 05 18:18:13 localhost bluetit[1890]: Requested method "set_vpn_profile -> OK" Jul 05 18:18:13 localhost bluetit[1890]: Requested method "start_connection" Jul 05 18:18:13 localhost bluetit[1890]: Network filter and lock are using nftables Jul 05 18:18:13 localhost bluetit[1890]: Kernel module nf_tables is already loaded Jul 05 18:18:13 localhost bluetit[1890]: Network filter successfully initialized Jul 05 18:18:13 localhost bluetit[1890]: Private network is allowed to pass the network filter Jul 05 18:18:13 localhost bluetit[1890]: Ping output is allowed to pass the network filter Jul 05 18:18:13 localhost bluetit[1890]: IPv6 NDP is allowed to pass the network filter Jul 05 18:18:13 localhost bluetit[1890]: OpenVPN connection successfully started Jul 05 18:18:13 localhost bluetit[1890]: Local interface lo - IPv4 127.0.0.1 IPv6 ::1 Jul 05 18:18:13 localhost bluetit[1890]: Local interface eth0 - IPv4 192.168.178.11 IPv6 2001:1c04:508:a800:b> Jul 05 18:18:13 localhost bluetit[1890]: Default IPv4 gateway via 192.168.178.1 dev eth0 Jul 05 18:18:13 localhost bluetit[1890]: Starting OpenVPN synchronous connection Jul 05 18:18:13 localhost bluetit[1890]: OpenVPN3 client successfully created and initialized. Jul 05 18:18:13 localhost bluetit[1890]: TUN persistence is enabled. Jul 05 18:18:13 localhost bluetit[1890]: Allowing system IPv4 DNS 84.116.46.20 to pass through the network fi> Jul 05 18:18:13 localhost bluetit[1890]: Allowing system IPv4 DNS 84.116.46.21 to pass through the network fi> Jul 05 18:18:16 localhost bluetit[1890]: Resolved remote OpenVPN server be3.vpn.airdns.org into IPv4 91.207.5> Jul 05 18:18:16 localhost bluetit[1890]: Successfully set OpenVPN3 client configuration Jul 05 18:18:16 localhost bluetit[1890]: Ping output is allowed to pass the network filter Jul 05 18:18:16 localhost bluetit[1890]: IPv6 NDP is allowed to pass the network filter Jul 05 18:18:16 localhost bluetit[1890]: Starting OpenVPN3 connection thread Jul 05 18:18:16 localhost bluetit[1890]: Connection statistics updater thread started Jul 05 18:18:16 localhost bluetit[1890]: OpenVPN core 3.12 AirVPN (20250606) linux x86_64 64-bit Jul 05 18:18:16 localhost bluetit[1890]: Frame=512/2112/512 mssfix-ctrl=1250 Jul 05 18:18:16 localhost bluetit[1890]: NOTE: This configuration contains options that were not used: Jul 05 18:18:16 localhost bluetit[1890]: Unsupported option (ignored) Jul 05 18:18:16 localhost bluetit[1890]: 0 [resolv-retry] [infinite] Jul 05 18:18:16 localhost bluetit[1890]: 1 [persist-key] Jul 05 18:18:16 localhost bluetit[1890]: 2 [persist-tun] Jul 05 18:18:16 localhost bluetit[1890]: 3 [explicit-exit-notify] [5] Jul 05 18:18:16 localhost bluetit[1890]: 4 [data-ciphers-fallback] [AES-256-CBC] Jul 05 18:18:16 localhost bluetit[1890]: EVENT: RESOLVE Jul 05 18:18:16 localhost bluetit[1890]: Setting up network filter and lock Jul 05 18:18:16 localhost bluetit[1890]: Adding IPv4 server 91.207.57.117 to network filter Jul 05 18:18:16 localhost bluetit[1890]: Network filter and lock successfully activated Jul 05 18:18:16 localhost bluetit[1890]: Contacting 91.207.57.117:443 via UDP Jul 05 18:18:16 localhost bluetit[1890]: EVENT: WAIT Jul 05 18:18:16 localhost bluetit[1890]: Connecting to [91.207.57.117]:443 (91.207.57.117) via UDP Jul 05 18:18:16 localhost bluetit[1890]: EVENT: CONNECTING Jul 05 18:18:16 localhost bluetit[1890]: Tunnel Options:V4,dev-type tun,link-mtu 1586,tun-mtu 1500,proto UDPv> Jul 05 18:18:16 localhost bluetit[1890]: Sending Peer Info: IV_VER=3.12 AirVPN (20250606) IV_PLAT=linux IV_TCPNL=1 IV_PROTO=8094 IV_MTU=1600 IV_CIPHERS=AES-256-GCM:AES-256-CBC:AES-192-GCM:AES-192-CBC:AES-128-G> IV_LZO_STUB=1 IV_COMP_STUB=1 IV_COMP_STUBv2=1 IV_SSL=OpenSSL 3.1.4 24 Oct 2023 UV_IPV6=yes IV_GUI_VER=Bluetit - AirVPN WireGuard/OpenVPN3 Service 2.0.0 RC 2 IV_BS64DL=1 Jul 05 18:18:17 localhost bluetit[1890]: TLS Handshake: peer certificate: CN=Castor, 4096 bit RSA, cipher: TL> Jul 05 18:18:17 localhost bluetit[1890]: Session is ACTIVE Jul 05 18:18:17 localhost bluetit[1890]: EVENT: GET_CONFIG Jul 05 18:18:17 localhost bluetit[1890]: Sending PUSH_REQUEST to server... Jul 05 18:18:17 localhost bluetit[1890]: OPTIONS: 0 [comp-lzo] [no] 1 [redirect-gateway] [ipv6] [def1] [bypass-dhcp] 2 [dhcp-option] [DNS] [10.12.230.1] 3 [dhcp-option] [DNS6] [fde6:7a:7d20:8e6::1] 4 [tun-ipv6] 5 [route-gateway] [10.12.230.1] 6 [topology] [subnet] 7 [ping] [10] 8 [ping-restart] [60] 9 [ifconfig-ipv6] [fde6:7a:7d20:8e6::10c6/64] [fde6:7a:7d20:8e6::1] 10 [ifconfig] [10.12.230.200] [255.255.255.0] 11 [peer-id] [3] 12 [cipher] [AES-256-GCM] Jul 05 18:18:17 localhost bluetit[1890]: PROTOCOL OPTIONS: key-derivation: OpenVPN PRF compress: LZO_STUB control channel: tls-crypt enabled data channel: cipher AES-256-GCM, peer-id 3 Jul 05 18:18:17 localhost bluetit[1890]: EVENT: ASSIGN_IP Jul 05 18:18:17 localhost bluetit[1890]: VPN Server has pushed IPv4 DNS server 10.12.230.1 Jul 05 18:18:17 localhost bluetit[1890]: Setting pushed IPv4 DNS server 10.12.230.1 in resolv.conf Jul 05 18:18:17 localhost bluetit[1890]: VPN Server has pushed IPv6 DNS server fde6:7a:7d20:8e6::1 Jul 05 18:18:17 localhost bluetit[1890]: Setting pushed IPv6 DNS server fde6:7a:7d20:8e6::1 in resolv.conf Jul 05 18:18:17 localhost bluetit[1890]: net_route_best_gw query IPv4: 91.207.57.117/32 Jul 05 18:18:17 localhost bluetit[1890]: sitnl_route_best_gw result: via 192.168.178.1 dev eth0 Jul 05 18:18:17 localhost bluetit[1890]: net_iface_mtu_set: mtu 1500 for tun0 Jul 05 18:18:17 localhost bluetit[1890]: net_iface_up: set tun0 up Jul 05 18:18:17 localhost bluetit[1890]: net_addr_add: 10.12.230.200/24 brd 10.12.230.255 dev tun0 Jul 05 18:18:17 localhost bluetit[1890]: net_addr_add: fde6:7a:7d20:8e6::10c6/64 dev tun0 Jul 05 18:18:17 localhost bluetit[1890]: net_route_add: 91.207.57.117/32 via 192.168.178.1 dev eth0 table 0 m> Jul 05 18:18:17 localhost bluetit[1890]: net_route_add: 0.0.0.0/1 via 10.12.230.1 dev tun0 table 0 metric 0 Jul 05 18:18:17 localhost bluetit[1890]: net_route_add: 128.0.0.0/1 via 10.12.230.1 dev tun0 table 0 metric 0 Jul 05 18:18:17 localhost bluetit[1890]: net_route_add: ::/1 via fde6:7a:7d20:8e6::1 dev tun0 table 0 metric 0 Jul 05 18:18:17 localhost bluetit[1890]: net_route_add: 8000::/1 via fde6:7a:7d20:8e6::1 dev tun0 table 0 met> Jul 05 18:18:17 localhost bluetit[1890]: TunPersist: saving tun context: Session Name: 91.207.57.117 Layer: OSI_LAYER_3 Remote Address: 91.207.57.117 Tunnel Addresses: 10.12.230.200/24 -> 10.12.230.1 fde6:7a:7d20:8e6::10c6/64 -> fde6:7a:7d20:8e6::1 [IPv6] Reroute Gateway: IPv4=1 IPv6=1 flags=[ ENABLE REROUTE_GW DEF1 BYPASS> Block IPv4: no Block IPv6: no Block local DNS: no Add Routes: Exclude Routes: DNS Servers: Priority: 0 Addresses: 10.12.230.1 fde6:7a:7d20:8e6::1 Values from dhcp-options: true Jul 05 18:18:17 localhost bluetit[1890]: Connected via tun Jul 05 18:18:17 localhost bluetit[1890]: LZO-ASYM init swap=0 asym=1 Jul 05 18:18:17 localhost bluetit[1890]: Comp-stub init swap=0 Jul 05 18:18:17 localhost bluetit[1890]: EVENT: CONNECTED 91.207.57.117:443 (91.207.57.117) via /UDP on tun/1> Jul 05 18:18:17 localhost bluetit[1890]: Server has pushed its own DNS. Rejecting system DNS from network fil> Jul 05 18:18:17 localhost bluetit[1890]: System IPv4 DNS 84.116.46.20 is now rejected by the network filter Jul 05 18:18:17 localhost bluetit[1890]: System IPv4 DNS 84.116.46.21 is now rejected by the network filter Jul 05 18:18:17 localhost bluetit[1890]: Connected to AirVPN server Castor, Brussels (Belgium) IP address 91.> Jul 05 18:18:17 localhost bluetit[1890]: Pushed DNS: 10.12.230.1 (IPv4) fde6:7a:7d20:8e6::1 (IPv6) Jul 05 18:18:47 localhost bluetit[1890]: Requested method "bluetit_status -> Bluetit is connected to VPN (Ope> Jul 05 18:18:47 localhost bluetit[1890]: Requested method "stop_connection" Jul 05 18:18:47 localhost bluetit[1890]: Stopping OpenVPN synchronous connection Jul 05 18:18:47 localhost bluetit[1890]: Connection statistics updater thread terminated Jul 05 18:18:47 localhost systemd[1]: bluetit.service: Main process exited, code=dumped, status=11/SEGV ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ An ExecStart= process belonging to unit bluetit.service has exited. ░░ ░░ The process' exit code is 'dumped' and its exit status is 11. Jul 05 18:18:47 localhost systemd[1]: bluetit.service: Failed with result 'core-dump'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ The unit bluetit.service has entered the 'failed' state with result 'core-dump'. Jul 05 18:18:47 localhost systemd[1]: bluetit.service: Consumed 5.589s CPU time. ░░ Subject: Resources consumed by unit runtime ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ The unit bluetit.service completed and consumed the indicated resources. Jul 05 18:21:42 localhost systemd[1]: Starting AirVPN Bluetit Daemon... ░░ Subject: A start job for unit bluetit.service has begun execution ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit bluetit.service has begun execution. ░░ ░░ The job identifier is 3689. Jul 05 18:21:42 localhost bluetit[11565]: Starting Bluetit - AirVPN WireGuard/OpenVPN3 Service 2.0.0 RC 2 - 9> Jul 05 18:21:42 localhost bluetit[11565]: OpenVPN core 3.12 AirVPN (20250606) linux x86_64 64-bit Jul 05 18:21:42 localhost bluetit[11565]: Copyright (C) 2012- OpenVPN Inc. All rights reserved. Jul 05 18:21:42 localhost bluetit[11565]: SSL Library: OpenSSL 3.1.4 24 Oct 2023 Jul 05 18:21:42 localhost bluetit[11565]: AirVPN WireGuard Client 2.0.0 Linux x86_64 64-bit Jul 05 18:21:42 localhost systemd[1]: bluetit.service: Can't open PID file /etc/airvpn/bluetit.lock (yet?) af> Jul 05 18:21:42 localhost systemd[1]: bluetit.service: Supervising process 11576 which is not our child. We'l> Jul 05 18:21:42 localhost bluetit[11576]: Bluetit daemon started with PID 11576 Jul 05 18:21:42 localhost bluetit[11576]: Reading run control directives from file /etc/airvpn/bluetit.rc Jul 05 18:21:42 localhost bluetit[11576]: External network is reachable via IPv4 gateway 192.168.178.1 throug> Jul 05 18:21:42 localhost bluetit[11576]: Successfully connected to D-Bus Jul 05 18:21:42 localhost systemd[1]: Started AirVPN Bluetit Daemon. ░░ Subject: A start job for unit bluetit.service has finished successfully ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit bluetit.service has finished successfully. ░░ ░░ The job identifier is 3689. Jul 05 18:21:42 localhost bluetit[11576]: IPv6 is available in this system Jul 05 18:21:42 localhost bluetit[11576]: Creating AirVPN Boot server list Jul 05 18:21:42 localhost bluetit[11576]: Added server http://63.33.78.166 Jul 05 18:21:42 localhost bluetit[11576]: Added server http://54.93.175.114 Jul 05 18:21:42 localhost bluetit[11576]: Added server http://82.196.3.205 Jul 05 18:21:42 localhost bluetit[11576]: Added server http://63.33.116.50 Jul 05 18:21:42 localhost bluetit[11576]: Added server http://[2a03:b0c0:0:1010::9b:c001] Jul 05 18:21:42 localhost bluetit[11576]: Added server http://bootme.org Jul 05 18:22:07 localhost bluetit[11576]: Boot server http://bootme.org cannot be resolved Jul 05 18:22:07 localhost bluetit[11576]: AirVPN Boot server list successfully created. Added 6 servers. Jul 05 18:22:07 localhost bluetit[11576]: Default VPN type for AirVPN connections is set to WireGuard Jul 05 18:22:07 localhost bluetit[11576]: Use of user VPN profiles is enabled by Bluetit policy Jul 05 18:22:07 localhost bluetit[11576]: Bluetit successfully initialized and ready Jul 05 18:22:07 localhost bluetit[11576]: Scanning for system DNS addresses Jul 05 18:22:07 localhost bluetit[11576]: Found system IPv4 DNS 10.12.230.1 Jul 05 18:22:07 localhost bluetit[11576]: Found 1 system DNS address Jul 05 18:22:07 localhost bluetit[11576]: Bluetit did not exit gracefully on its last run or has been killed. Jul 05 18:22:07 localhost bluetit[11576]: Run recover network procedure by using Bluetit client option --reco> Jul 05 18:22:07 localhost bluetit[11576]: ERROR: Connection to AirVPN's ipleak.net cancelled. It seems Blueti> Your system may not be working properly and your network connection> Jul 05 18:22:07 localhost bluetit[11576]: AirVPN Manifest updater thread started Jul 05 18:22:07 localhost bluetit[11576]: Default AirVPN Manifest update interval is 15 minutes Jul 05 18:22:07 localhost bluetit[11576]: AirVPN Manifest update suspended: System needs network recovery Jul 05 18:22:07 localhost bluetit[11576]: Trying to load the local instance of AirVPN Manifest Jul 05 18:22:07 localhost bluetit[11576]: AirVPN Manifest successfully retrieved from local instance Jul 05 18:22:22 localhost bluetit[11576]: Requested method "version" Jul 05 18:22:22 localhost bluetit[11576]: Requested method "openvpn_info" Jul 05 18:22:23 localhost bluetit[11576]: Requested method "openvpn_copyright" Jul 05 18:22:23 localhost bluetit[11576]: Requested method "ssl_library_version" Jul 05 18:22:23 localhost bluetit[11576]: Requested method "wireguard_info" Jul 05 18:22:23 localhost bluetit[11576]: Requested method "reset_bluetit_options -> Bluetit options successf> Jul 05 18:22:23 localhost bluetit[11576]: Requested method "set_options: client-name (client-name) -> Goldcre> Jul 05 18:22:23 localhost bluetit[11576]: Requested method "set_options: client-user (client-user) -> gerrit" Jul 05 18:22:23 localhost bluetit[11576]: Requested method "set_vpn_profile -> ERROR: Cannot set VPN profile.> Your system may not be working properly and your network connection> " Jul 05 18:22:35 localhost bluetit[11576]: Requested method "version" Jul 05 18:22:35 localhost bluetit[11576]: Requested method "openvpn_info" Jul 05 18:22:35 localhost bluetit[11576]: Requested method "openvpn_copyright" Jul 05 18:22:35 localhost bluetit[11576]: Requested method "ssl_library_version" Jul 05 18:22:35 localhost bluetit[11576]: Requested method "wireguard_info" Jul 05 18:22:35 localhost bluetit[11576]: Successfully restored DNS settings Jul 05 18:22:35 localhost bluetit[11576]: Scanning for system DNS addresses Jul 05 18:22:35 localhost bluetit[11576]: Found system IPv4 DNS 84.116.46.20 Jul 05 18:22:35 localhost bluetit[11576]: Found system IPv4 DNS 84.116.46.21 Jul 05 18:22:35 localhost bluetit[11576]: Found 2 system DNS addresses Jul 05 18:22:35 localhost bluetit[11576]: Network filter successfully restored Jul 05 18:22:35 localhost bluetit[11576]: Updating AirVPN Manifest Jul 05 18:22:35 localhost bluetit[11576]: Requested method "recover_network -> Successfully restored DNS and > Jul 05 18:22:35 localhost bluetit[11576]: Sending event 'event_end_of_session' Jul 05 18:22:35 localhost bluetit[11576]: Trying connection to AirVPN bootstrap server at http://63.33.78.166 Jul 05 18:22:36 localhost bluetit[11576]: Boot server http://bootme.org resolved into IPv6 2a03:b0c0:0:1010::> Jul 05 18:22:36 localhost bluetit[11576]: AirVPN Manifest successfully retrieved from server Jul 05 18:22:36 localhost bluetit[11576]: AirVPN Manifest update interval is now set to 30 minutes lines 657-685/685 (END) Goldcrest - AirVPN Bluetit Client 2.0.0 RC 2 - 9 June 2025 2025-07-05 18:18:13 Reading run control directives from file /home/gerrit/.config/goldcrest.rc 2025-07-05 18:18:13 Bluetit - AirVPN WireGuard/OpenVPN3 Service 2.0.0 RC 2 - 9 June 2025 2025-07-05 18:18:13 OpenVPN core 3.12 AirVPN (20250606) linux x86_64 64-bit 2025-07-05 18:18:13 Copyright (C) 2012- OpenVPN Inc. All rights reserved. 2025-07-05 18:18:13 OpenSSL 3.1.4 24 Oct 2023 2025-07-05 18:18:13 AirVPN WireGuard Client 2.0.0 Linux x86_64 64-bit 2025-07-05 18:18:13 Bluetit options successfully reset 2025-07-05 18:18:13 Requesting VPN connection to Bluetit 2025-07-05 18:18:13 Network filter and lock are using nftables 2025-07-05 18:18:13 Kernel module nf_tables is already loaded 2025-07-05 18:18:13 Network filter successfully initialized 2025-07-05 18:18:13 Private network is allowed to pass the network filter 2025-07-05 18:18:13 Ping output is allowed to pass the network filter 2025-07-05 18:18:13 IPv6 NDP is allowed to pass the network filter 2025-07-05 18:18:13 Local interface lo - IPv4 127.0.0.1 IPv6 ::1 2025-07-05 18:18:13 Local interface eth0 - IPv4 192.168.178.11 IPv6 2001:1c04:508:a800:b260:b657:ae5d:6d7e IPv6 2001:1c04:508:a800:aaa1:59ff:fe2f:523e IPv6 fe80::aaa1:59ff:fe2f:523e 2025-07-05 18:18:13 Default IPv4 gateway via 192.168.178.1 dev eth0 2025-07-05 18:18:13 Starting OpenVPN synchronous connection 2025-07-05 18:18:13 TUN persistence is enabled. 2025-07-05 18:18:13 Allowing system IPv4 DNS 84.116.46.20 to pass through the network filter 2025-07-05 18:18:13 Allowing system IPv4 DNS 84.116.46.21 to pass through the network filter 2025-07-05 18:18:16 Resolved remote OpenVPN server be3.vpn.airdns.org into IPv4 91.207.57.117 2025-07-05 18:18:16 Ping output is allowed to pass the network filter 2025-07-05 18:18:16 OpenVPN core 3.12 AirVPN (20250606) linux x86_64 64-bit 2025-07-05 18:18:16 Frame=512/2112/512 mssfix-ctrl=1250 2025-07-05 18:18:16 NOTE: This configuration contains options that were not used: 2025-07-05 18:18:16 Unsupported option (ignored) 2025-07-05 18:18:16 0 [resolv-retry] [infinite] 2025-07-05 18:18:16 1 [persist-key] 2025-07-05 18:18:16 2 [persist-tun] 2025-07-05 18:18:16 3 [explicit-exit-notify] [5] 2025-07-05 18:18:16 4 [data-ciphers-fallback] [AES-256-CBC] 2025-07-05 18:18:16 EVENT: RESOLVE 2025-07-05 18:18:16 Setting up network filter and lock 2025-07-05 18:18:16 Adding IPv4 server 91.207.57.117 to network filter 2025-07-05 18:18:16 Network filter and lock successfully activated 2025-07-05 18:18:16 Contacting 91.207.57.117:443 via UDP 2025-07-05 18:18:16 EVENT: WAIT 2025-07-05 18:18:16 Connecting to [91.207.57.117]:443 (91.207.57.117) via UDP 2025-07-05 18:18:16 EVENT: CONNECTING 2025-07-05 18:18:16 Tunnel Options:V4,dev-type tun,link-mtu 1586,tun-mtu 1500,proto UDPv4,comp-lzo,cipher BF-CBC,auth SHA512,keysize 128,key-method 2,tls-client 2025-07-05 18:18:16 Sending Peer Info: IV_VER=3.12 AirVPN (20250606) IV_PLAT=linux IV_TCPNL=1 IV_PROTO=8094 IV_MTU=1600 IV_CIPHERS=AES-256-GCM:AES-256-CBC:AES-192-GCM:AES-192-CBC:AES-128-GCM:AES-128-CBC:BF-CBC IV_LZO_STUB=1 IV_COMP_STUB=1 IV_COMP_STUBv2=1 IV_SSL=OpenSSL 3.1.4 24 Oct 2023 UV_IPV6=yes IV_GUI_VER=Bluetit - AirVPN WireGuard/OpenVPN3 Service 2.0.0 RC 2 IV_BS64DL=1 2025-07-05 18:18:17 TLS Handshake: peer certificate: CN=Castor, 4096 bit RSA, cipher: TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 Kx=any Au=any Enc=CHACHA20/POLY1305(256) Mac=AEAD, key-agreement: x25519 2025-07-05 18:18:17 Session is ACTIVE 2025-07-05 18:18:17 EVENT: GET_CONFIG 2025-07-05 18:18:17 Sending PUSH_REQUEST to server... 2025-07-05 18:18:17 OPTIONS: 0 [comp-lzo] [no] 1 [redirect-gateway] [ipv6] [def1] [bypass-dhcp] 2 [dhcp-option] [DNS] [10.12.230.1] 3 [dhcp-option] [DNS6] [fde6:7a:7d20:8e6::1] 4 [tun-ipv6] 5 [route-gateway] [10.12.230.1] 6 [topology] [subnet] 7 [ping] [10] 8 [ping-restart] [60] 9 [ifconfig-ipv6] [fde6:7a:7d20:8e6::10c6/64] [fde6:7a:7d20:8e6::1] 10 [ifconfig] [10.12.230.200] [255.255.255.0] 11 [peer-id] [3] 12 [cipher] [AES-256-GCM] 2025-07-05 18:18:17 PROTOCOL OPTIONS: key-derivation: OpenVPN PRF compress: LZO_STUB control channel: tls-crypt enabled data channel: cipher AES-256-GCM, peer-id 3 2025-07-05 18:18:17 EVENT: ASSIGN_IP 2025-07-05 18:18:17 VPN Server has pushed IPv4 DNS server 10.12.230.1 2025-07-05 18:18:17 Setting pushed IPv4 DNS server 10.12.230.1 in resolv.conf 2025-07-05 18:18:17 VPN Server has pushed IPv6 DNS server fde6:7a:7d20:8e6::1 2025-07-05 18:18:17 Setting pushed IPv6 DNS server fde6:7a:7d20:8e6::1 in resolv.conf 2025-07-05 18:18:17 net_route_best_gw query IPv4: 91.207.57.117/32 2025-07-05 18:18:17 sitnl_route_best_gw result: via 192.168.178.1 dev eth0 2025-07-05 18:18:17 net_iface_mtu_set: mtu 1500 for tun0 2025-07-05 18:18:17 net_iface_up: set tun0 up 2025-07-05 18:18:17 net_addr_add: 10.12.230.200/24 brd 10.12.230.255 dev tun0 2025-07-05 18:18:17 net_addr_add: fde6:7a:7d20:8e6::10c6/64 dev tun0 2025-07-05 18:18:17 net_route_add: 91.207.57.117/32 via 192.168.178.1 dev eth0 table 0 metric 0 2025-07-05 18:18:17 net_route_add: 0.0.0.0/1 via 10.12.230.1 dev tun0 table 0 metric 0 2025-07-05 18:18:17 net_route_add: 128.0.0.0/1 via 10.12.230.1 dev tun0 table 0 metric 0 2025-07-05 18:18:17 net_route_add: ::/1 via fde6:7a:7d20:8e6::1 dev tun0 table 0 metric 0 2025-07-05 18:18:17 net_route_add: 8000::/1 via fde6:7a:7d20:8e6::1 dev tun0 table 0 metric 0 2025-07-05 18:18:17 TunPersist: saving tun context: Session Name: 91.207.57.117 Layer: OSI_LAYER_3 Remote Address: 91.207.57.117 Tunnel Addresses: 10.12.230.200/24 -> 10.12.230.1 fde6:7a:7d20:8e6::10c6/64 -> fde6:7a:7d20:8e6::1 [IPv6] Reroute Gateway: IPv4=1 IPv6=1 flags=[ ENABLE REROUTE_GW DEF1 BYPASS_DHCP IPv4 IPv6 ] Block IPv4: no Block IPv6: no Block local DNS: no Add Routes: Exclude Routes: DNS Servers: Priority: 0 Addresses: 10.12.230.1 fde6:7a:7d20:8e6::1 Values from dhcp-options: true 2025-07-05 18:18:17 Connected via tun 2025-07-05 18:18:17 LZO-ASYM init swap=0 asym=1 2025-07-05 18:18:17 Comp-stub init swap=0 2025-07-05 18:18:17 EVENT: CONNECTED 91.207.57.117:443 (91.207.57.117) via /UDP on tun/10.12.230.200/fde6:7a:7d20:8e6::10c6 gw=[10.12.230.1/fde6:7a:7d20:8e6::1] mtu=(default) 2025-07-05 18:18:17 Server has pushed its own DNS. Rejecting system DNS from network filter. 2025-07-05 18:18:17 System IPv4 DNS 84.116.46.20 is now rejected by the network filter 2025-07-05 18:18:17 System IPv4 DNS 84.116.46.21 is now rejected by the network filter 2025-07-05 18:18:17 Connected to AirVPN server Castor, Brussels (Belgium) IP address 91.207.57.117 - VPN Type OpenVPN - Port 443 - Protocol UDP - Cipher AES-256-GCM 2025-07-05 18:18:17 Pushed DNS: 10.12.230.1 (IPv4) fde6:7a:7d20:8e6::1 (IPv6) ^C2025-07-05 18:18:47 Caught Onderbroken signal. Terminating. 2025-07-05 18:18:47 Requesting VPN connection termination to Bluetit 2025-07-05 18:18:47 ERROR: D-Bus service org.airvpn.server is not available. Please check whether Bluetit service (daemon) is running. gerrit@localhost:/usr/local/bin> ./goldcrest AirVPN_Belgium_UDP-443-Entry3.ovpn Goldcrest - AirVPN Bluetit Client 2.0.0 RC 2 - 9 June 2025 2025-07-05 18:19:00 Reading run control directives from file /home/gerrit/.config/goldcrest.rc 2025-07-05 18:19:00 ERROR: D-Bus service org.airvpn.server is not available. Please check whether Bluetit service (daemon) is running. gerrit@localhost:/usr/local/bin> ./goldcrest --recover-network Goldcrest - AirVPN Bluetit Client 2.0.0 RC 2 - 9 June 2025 2025-07-05 18:19:48 Reading run control directives from file /home/gerrit/.config/goldcrest.rc 2025-07-05 18:19:48 ERROR: D-Bus service org.airvpn.server is not available. Please check whether Bluetit service (daemon) is running. gerrit@localhost:/usr/local/bin> -
Arion behaving very weirdly!
Tech Jedi Alex replied to confused_user's topic in Troubleshooting and Problems
$ ip-api 89.238.150.43 { "country" : "United Kingdom", "regionName" : "England", "city" : "London", "zip" : "", "lat" : 51.5073, "lon" : -0.1277, "timezone" : "Europe/London", "isp" : "M247 Europe SRL", "org" : "AirVPN.org exit server (Arion)", "as" : "AS9009 M247 Europe SRL", "mobile" : false, "proxy" : true, "hosting" : true, "query" : "89.238.150.43" } Nah, simple geolocation DB error. It could've been an M247 IP address located in Romania (M247 itself is a Romanian company, even) but was since moved to UK, and the info wasn't updated in the DB. I'm struggling with understanding the issue. Maybe it's the unfamiliarity with DataImpulse. Can you elaborate? -
Hi to all, today I found a strange behavior during usage of Firefox, connected via Piautos. When I send the search query " Telefonbuch" I get lots of results in russian language and the IP locator of Firefox showed me "Chimki" as my current location. When I switch to a german server and send the same search query, the correct IP location (Frankfurt) was displayed. After deinstallation and reinstallation of firefox I had the same issue! Defender showed no malware on my PC. This looks very strange to me. Please check this immediatly. Best regards
-
The AirVPN Status API endpoint lists all servers and their entry IP addresses. It's a public endpoint emitting results as JSON, XML, plain text or PHP code. Easily scriptable. Also, querying earthX.all.vpn.airdns.org returns all Xth entry IP addresses (X = 1-4). For exit addresses, it gets a bit bad. You can query servername_exit.airservers.org to get the exit IPv4 of that server, but you won't get the IPv6 exit address this way.
-
ANSWERED WireGuard with Linux - Terminal: Help...
reversevpn replied to Nasheayahu's topic in Troubleshooting and Problems
Did you install systemd-resolved yet? If not, do so and try again. If you already have, then just erase the DNS= line from the America.conf file, and manually change /etc/resolv.conf to 10.128.0.1 after the America interface has been raised if you wish to use airvpn's DNS. Alternatively, if you have your own DNS server like dnsmasq and want it to query airvpn's DNS, edit /etc/dnsmasq.conf and add a server=10.128.0.1 directive to it. -
https://survey-consulting.com/ : no DNS and no access DNS issue $ dig survey-consulting.com ; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> survey-consulting.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 56474 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;survey-consulting.com. IN A ;; Query time: 3231 msec ;; SERVER: 10.30.50.1#53(10.30.50.1) (UDP) ;; WHEN: Mon Dec 18 11:09:39 CET 2023 ;; MSG SIZE rcvd: 50 $ dig survey-consulting.com @80.67.169.12 ; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> survey-consulting.com @80.67.169.12 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20821 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;survey-consulting.com. IN A ;; ANSWER SECTION: survey-consulting.com. 86400 IN A 37.61.203.152 ;; Query time: 44 msec ;; SERVER: 80.67.169.12#53(80.67.169.12) (UDP) ;; WHEN: Mon Dec 18 11:09:30 CET 2023 ;; MSG SIZE rcvd: 66 adding 37.61.203.152 survey-consulting.com 37.61.203.152 www.survey-consulting.com in /etc/hosts $ ping survey-consulting.com PING survey-consulting.com (37.61.203.152) 56(84) bytes of data. ^C --- survey-consulting.com ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3063ms :~$ wget survey-consulting.com --2023-12-18 11:11:16-- http://survey-consulting.com/ Résolution de survey-consulting.com (survey-consulting.com)… 37.61.203.152 Connexion à survey-consulting.com (survey-consulting.com)|37.61.203.152|:80… Test link : https://airvpn.org/routes/?q=https%3A%2F%2Fsurvey-consulting.com%2F
-
Deactivate VPN, using https://www.fdn.fr/actions/dns/ and it's OK. But today : seems OK too . have issue with https://survey-consulting.com/ too $ dig survey-consulting.com ; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> survey-consulting.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 56474 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;survey-consulting.com. IN A ;; Query time: 3231 msec ;; SERVER: 10.30.50.1#53(10.30.50.1) (UDP) ;; WHEN: Mon Dec 18 11:09:39 CET 2023 ;; MSG SIZE rcvd: 50 $ dig survey-consulting.com @80.67.169.12 ; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> survey-consulting.com @80.67.169.12 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20821 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;survey-consulting.com. IN A ;; ANSWER SECTION: survey-consulting.com. 86400 IN A 37.61.203.152 ;; Query time: 44 msec ;; SERVER: 80.67.169.12#53(80.67.169.12) (UDP) ;; WHEN: Mon Dec 18 11:09:30 CET 2023 ;; MSG SIZE rcvd: 66 (but here : website disable access too)
-
Website fr.mappy.com show n as unknow. Doing a ping and a dif with AirVPN : :~$ ping fr.mappy.com ping: fr.mappy.com: Nom ou service inconnu :~$ dig fr.mappy.com ; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> fr.mappy.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 22802 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;fr.mappy.com. IN A ;; Query time: 3755 msec ;; SERVER: 10.15.178.1#53(10.15.178.1) (UDP) ;; WHEN: Thu Dec 14 11:37:40 CET 2023 ;; MSG SIZE rcvd: 41 Without VPN :~$ ping fr.mappy.com PING www.mappy.com (193.203.32.57) 56(84) bytes of data. ^C --- www.mappy.com ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2030ms :~$ dig fr.mappy.com ; <<>> DiG 9.18.19-1~deb12u1-Debian <<>> fr.mappy.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2855 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1472 ;; QUESTION SECTION: ;fr.mappy.com. IN A ;; ANSWER SECTION: fr.mappy.com. 1664 IN CNAME www.mappy.com. www.mappy.com. 1093 IN A 193.203.32.57 ;; Query time: 4 msec ;; SERVER: 192.168.1.254#53(192.168.1.254) (UDP) ;; WHEN: Thu Dec 14 11:37:57 CET 2023 ;; MSG SIZE rcvd: 75 can yoiu update your DNS please ? Else : https://airvpn.org/routes/?q=https%3A%2F%2Ffr.mappy.com
-
ANSWERED airvpn.org broken DNSSEC trust chain
Staff replied to copykitty's topic in Troubleshooting and Problems
Hello! It's all pre-defined by GoDaddy and nothing can be configured on our side, unfortunately. We will query GoDaddy and warn them about the issue. We own and control authoritative DNS for almost all of our domain names but not for airvpn.org. to add redundancy. Kind regards
