Jump to content
Not connected, Your IP: 18.97.14.89
AirVPN

All Activity

This stream auto-updates     

  1. Past hour
  2. victorbr1398 victorbr1398 joined the community ...
  3. chovija chovija joined the community ...
  4. Igorccg Igorccg joined the community ...
  5. Igorvzi Igorvzi joined the community ...
  6. RafaelSam RafaelSam joined the community ...
  7. jingtao825 jingtao825 joined the community ...
  8. Miguelluh Miguelluh joined the community ...
  9. FreakyDeaky123 FreakyDeaky123 joined the community ...
  10. treyzer treyzer joined the community ...
  11. Today
  12. Pacific Auto Zone Pacific Auto Zone joined the community ...
  13. Yesterday
  14. AdamPro rendering AdamPro rendering changed their profile photo ...
  15. Y-Not Natural Y-Not Natural changed their profile photo ...
  16. Botanical Remedies LLC Botanical Remedies LLC changed their profile photo ...
  17. OpenSourcerer started following eddie - there is no available or enabled network lock mode, Reddit blocked on all AirVPN servers, AirVPN Not display and and 3 others ...
  18. OpenSourcerer
    Probably a change on Reddit's side. The route checker simply connects to the website like any browser behind a VPN server would and displays the HTTP code received from the target webserver. If it's a 403 it's definitely restricted on Reddit's side.
  19. OpenSourcerer
    Right-clicking on the tray icon > Show doesn't work?
  20. OpenSourcerer
    Please post the exact error. Also try rebooting (not shutdown+startup) the machine first.
  21. OpenSourcerer
    uTP never changed. Though, there are some tests here and there that say mixed mode (TCP + uTP) can be faster, one just needs to wait a few minutes for uTP to ramp up. I generally still recommend TCP only, though, the difference is marginal. Still UDP, so uTP will behave similarly. Then maybe in your case mixed mode is indeed better. It's not like having this enabled will somehow cause your OS to uninstall. Or manipulate the weather around you and spawn an EF5 tornado on the spot. As written, I usually recommend TCP only because in most cases it just avoids headaches.
  22. OpenSourcerer
    Besides, I can simply forget updating it and everyone will lose their minds. Real risk to a business.
  23. OpenSourcerer
    What instructions, and what kind of errors? What's the error here? Please try a connection with Eddie and provide a system report. .
  24. Dessine-moi un faire-part Dessine-moi un faire-part changed their profile photo ...
  25. arduoushare started following Reddit blocked on all AirVPN servers ...
  26. arduoushare
    Even when logged into reddit.com, i now get a "You've been blocked by network security" message. Furthermore, the route checking tool shows that reddit.com is inaccessible from all AirVPN servers (HTTP 403). i don't know if the 403 is because the route checking tool can't be logged into Reddit while checking, or if something has changed recently.
  27. Illegalemoiaussi
    The AirVPN application does not display, nothing happens, it stays in the background. When I try to open it, I get the error message "An instance of eddie is already running," but reinstalling and uninstalling doesn't fix the issue. Even going through the task manager to close it and restart doesn't work. AirVPN stays hidden and I can't do anything with it. Best regards.
  28. Hawaiian Tour Co Hawaiian Tour Co changed their profile photo ...
  29. Jasmine Florist Jasmine Florist changed their profile photo ...
  30. Bartz Law Group Bartz Law Group changed their profile photo ...
  31. Aims Aesthetics Aims Aesthetics changed their profile photo ...
  32. Jasonpen started following Torrents - Should we still avoid μTP? ...
  33. Repairfully Repairfully changed their profile photo ...
  34. Russell_94
    I have installed the latest version of Eddie, but this keeps failing with an error about elevated rights failing. Am I doing anything wrong?
  35. yoyall
    Hi Everyone! Over the years there's been advice to avoid μTP in torrent clients like qBittorrent and use TCP exclusively (when using a VPN). And I have followed this advice. But now I wanted to check in again to see if that is still the case - Is it still recommended to avoid μTP? I'm asking for two reasons - 1) when this advice first came out I think we only really had OpenVPN. Now the default is Wireguard. Does that change anything? And also 2) I recently had a couple of torrents I was trying to download and they were stalled and dead. But when I enabled μTP with TCP, they sprang to life and downloaded lickety-split. So, just wanted to see if anything had changed - or whether my experience was just an anecdotal one-off. Cheers!
  36. @Yang
    Thank you for your guidance.
  37.    @Yang reacted to a post in a topic: Could you please add support for the AmneziaWG protocol in future versions of Eddie? ...
  38. Last week
  39.    MrNull reacted to a post in a topic: Abandoned Warrant Canary. What is going on with Perfect Privacy? ...
  40. MrNull
    Former Perfect Privacy customer here. I stopped using the service around November of last year after half their servers went down while they acted completely in-transparent about it. Verbiage like "Which problems are you talking about?! We're as fantastic and safe as ever." have become the norm despite endless problems: 50% of the advertised servers are never working, defunct IKVE2 profiles, an unfinished client that feels like a stuck beta, barely any support, etc.pp. The only person keeping the service seem like a still maintained project is the mod " PP Christian ". I honestly have no idea what is going on over there but I started to dig a bit deeper. A friend of mine is part of the Chaos Computer Club. I asked him about his opinion because I knew he had been using the service in the past and he responded that they most likely ran into some trouble with the German authorities last year which resulted in some data centers handing them a notice and canceling the server subscriptions. At the same time, it seems like the team of Perfect Privacy has disbanded and the service is now entirely run by the company's director D., his wife and maybe a few others. I think it's not entirely far-fetched to assume that the account PP Christian is actually run by D.. There are lot of conspiracies floating around the forums. PP being taken over by the police as a honey pot, or the team having sold the service and therefore can't update the warrant canary but honestly, I think the other assumptions are far more realistic. They have lost their primary partners and are less staff which results in less customers, less money and less options to change that -- a vicious cycle that will lead to he service's downfall. Regarding the warrant canary, I think people are putting way too much weight into it. In the end it's just a notification that guarantees that the service is still acting independently, it's never a guarantee against state level players like law enforcement and people shouldn't be so naive to believe that.
  41. Puontyxx
    I am getting the above error when running Eddie for the first time after signing up to AirVPN after a recommendation I am using PopOS I installed via terminal following the instructions but got terminal errors when trying to login I then downloaded and installed the ubuntu image and Eddie loads fine. However after logging in and trying to connect to a server I get this issue: there is now available or enabled network lock mode I have read about network lock and googled the error. The most relevant cases I could find was about an old WindowsXP user and a guy who said he didn't have 'iptables' installed as part of linux. However, I have tried running without 'network lock' enabled in the settings. I have restarted the app and tried to connect to a server again, and it just fails to connect to any server after attempting a connection. I gave up after trying to connect to 20 different random servers. Please help. Thank you
  42.    Abdulah222 reacted to a post in a topic: No latencies ...
  43.    Infradragon reacted to a post in a topic: AUR eddie-ui-git 2.24.5 package - mscorlib.dll error ...
  44. OpenSourcerer
    No. Instead, remove the aur repo from your mirrorlist, remove all packages from it and rebuild them live from AUR. Cachy's aur repo is a horror made manifest, I'm hearing nothing but bad things about it.
  45.    Infradragon reacted to a post in a topic: [LINUX] Network Lock and firewalld ...
  46. Infradragon
    i'm having the exact same issue with both the eddie-ui and eddie-ui-git packages from the AUR edit: figured it out, the packge from the cachyos repos is causing the issue, i'll report this upstream
  47. AirGuest233
    Well, it's the worst ISP in China.They shape everything.I suggest you should switch to other ISP such as China Telecom , China Unicom or China Mobile.You may find some cheap plans on the RedNote.But BE CAREFUL. If you switch your ISP to I mentioned above, you could try these servers. China Telecom: NL , DE , US SJC , US LAX China Unicom: nearly all european servers (except IE , NO , SE) (I recommend NL , DE) , US servers in the west coast. China Mobile: JP , SG servers I recommend using OpenVPN (IP Entry 3 & UDP & Port 443),since WireGuard is too easy to be identified (run a Wireshark and you know what I mean). If you have IPv6 connection,you should use them first (unless it's too slow for you).The GFW is less aggressive on IPv6 compared to IPv4
  48. EVN Europe Ltd. EVN Europe Ltd. changed their profile photo ...
  49. @Yang
    I'm using China Broadcasting Network, and ever since I started using AirVPN, I've mainly used it for P2P sharing. After all, I first came across AirVPN through an ad on an eMule website, so I've always wanted to improve speed and connection duration. Unfortunately, due to advanced traffic shaping technologies, my connection has become slower and slower, eventually getting reset. At first, I had speeds of over 150 Mbps, but they gradually dropped to 8 Mbps, and after about 10 hours, the connection finally disconnected. I think my network environment poses a significant challenge for both VPNs and P2P networks. In the future, I may no longer use AirVPN for P2P sharing, and instead just use it for browsing. The basic circumvention service that AirVPN provides still works quite well for that purpose.
  50.    @Yang reacted to a post in a topic: Could you please add support for the AmneziaWG protocol in future versions of Eddie? ...
  51. @Yang
    Your explanation was very clear, thank you. Although I'm not a professional programmer, I can understand it.
  52. @Yang
    你的解释很清楚，谢谢。虽然我不是专业的程序员，但我能理解。
  53. colorman
    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>
  54. AirGuest233
    I am also in China and I can confirm that OpenVPN (IP Entry 3 & UDP & Port 443) works perfectly in China with great speed (over 200Mbps on some DE servers).BTW could you tell me which ISP you are using?And which server you are connected to?
  55. OpenSourcerer
    I wouldn't say that, seeing as the project seemingly recommends using its own Linux kernel module, so only specialized projects may pull this out-of-tree module and compile it into their kernels. On a standard router, maybe even if you flash it with specialized ROMs like OpenWrt, you may find Wireguard, but not AmneziaWG. It also seems to need its own forks of standard Wireguard tools which you probably won't find in some distribution families. Maybe Debian at some point, later Ubuntu, and maybe maybe Fedora. On Arch, it might surface on the AUR (or probably is), and on SuSE on the OBS. Red Hat will never adopt it, and if Enterprise is not really interested, you get into a situation where single developers, or a single group of devs, are maintaining something used commercially again. It is not sustainable; you'll never know if it'll still be there in 5 years, or if internal disputes won't force the project to be forked and developed under a different name. But standard Wireguard is developed by well-known researchers, right in the kernel, and garnered enough commercial interest that some consumer networking companies implemented it as a feature. Wireguard is sustainable. AmneziaWG is not. It will never replace standard Wireguard. Besides, the aim of Wireguard is not privacy. And most people around the forums (by topics created in the forums, at least) use the VPN not for the privacy aspect but because they want to torrent. What they're looking for is performance. You don't need AmneziaWG for that. What I'm concerned about is the relationship Wireguard <> AmneziaWG. AmneziaWG would have the obligation to behave in a way a standard Wireguard behaves if server and client differ. I don't know how Wireguard will react if those fixed parameters talked about in the docs are altered. Maybe it's not even a problem, since AmneziaWG clients can connect here normally. At least according to some threads it doesn't seem to be a problem. Dunno. But, no, a replacement is highly unlikely, both generally and specifically on AirVPN.
  56. @Yang
    In your situation, you can only use Tor. It routes your traffic through global nodes, which are impossible to block entirely. Use obfuscated bridges like Tor's webtunnel, and run AirVPN over Tor—but keep in mind, it's very slow.
  57. Phanuel
    I'm also wondering if something like that could be possible. It doesn't have to be Amnezia, it could be something of your own. SSH isn't working for me anymore, while SSL works fine, though both of the protocols are nowhere to be considered fast, they are just too slow to be used. I currently use Amnezia, because it's the quickest possible protocol that actually works. While it would be great if it was added, I've recently confronted a problem that I don't think could be solved. I think my provider started to block all the IPs from a certain server provider that AirVPN uses, and I'm afraid it may block the rest of them as well. It doesn't connect me anymore to the servers of that provider, no matter if I use SSL or AmneziaWG protocols. If anyone has solutions to this problem, I would appreciate any help.
  58. ryan7654
    This is not a universal fix unfortunately. It seems it is broken for aarch64 (ARM64) in general, I am using an ARM64 Fedora Linux VM on an Apple Silicon Mac. I'm sure there is an equivalent workaround for Fedora, but I just switched back to a Debian 12 VM instead (same workaround as Pi OS applied). ryan@fedoraVM:~$ uname -a Linux fedoraVM 6.15.3-200.fc42.aarch64 #1 SMP PREEMPT_DYNAMIC Thu Jun 19 15:27:43 UTC 2025 aarch64 GNU/Linux ryan@fedoraVM:~$ cat /etc/os-release NAME="Fedora Linux" VERSION="42 (KDE Plasma Desktop Edition)" RELEASE_TYPE=stable ID=fedora VERSION_ID=42 VERSION_CODENAME="" PLATFORM_ID="platform:f42" PRETTY_NAME="Fedora Linux 42 (KDE Plasma Desktop Edition)" ANSI_COLOR="0;38;2;60;110;180" LOGO=fedora-logo-icon CPE_NAME="cpe:/o:fedoraproject:fedora:42" DEFAULT_HOSTNAME="fedora" HOME_URL="https://fedoraproject.org/" DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f42/system-administrators-guide/" SUPPORT_URL="https://ask.fedoraproject.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Fedora" REDHAT_BUGZILLA_PRODUCT_VERSION=42 REDHAT_SUPPORT_PRODUCT="Fedora" REDHAT_SUPPORT_PRODUCT_VERSION=42 SUPPORT_END=2026-05-13 VARIANT="KDE Plasma Desktop Edition" VARIANT_ID=kde ryan@fedoraVM:~$ eddie-ui Error loading shared library: /tmp/mono-bundle-3uGRr0/libgdiplus.so.0 libtiff.so.5: cannot open shared object file: No such file or directory ryan@fedoraVM:~$
  1. Load more activity
×
×
  • Create New...