Linux: AirVPN Suite 2.0.0 preview available

Staff

1 hour ago, colorman said:

./install.sh: line 385: setcap: command not found

Hello!

setcap sets file capabilities and requires libcap. Please install libcap and libcap-progs packages, uninstall and re-install the Suite, test again and report back at your convenience.

Kind regards

colorman

I missed package libcap-progs

But still error;

localhost:/usr/local/bin> ./goldcrest AirVPN_Belgium_UDP-1637-Entry3.conf
Goldcrest - AirVPN Bluetit Client 2.0.0 beta 4 - 14 February 2025

2025-02-15 11:49:25 Reading run control directives from file /home/gerrit/.config/goldcrest.rc
2025-02-15 11:49:25 Bluetit - AirVPN WireGuard/OpenVPN3 Service 2.0.0 beta 4 - 14 February 2025
2025-02-15 11:49:25 OpenVPN core 3.11 AirVPN (20250206) linux x86_64 64-bit
2025-02-15 11:49:25 Copyright (C) 2012- OpenVPN Inc. All rights reserved.
2025-02-15 11:49:25 OpenSSL 3.1.4 24 Oct 2023
2025-02-15 11:49:25 AirVPN WireGuard Client 2.0.0 Linux x86_64 64-bit
2025-02-15 11:49:25 Bluetit options successfully reset
2025-02-15 11:49:25 Requesting VPN connection to Bluetit
2025-02-15 11:49:25 Network filter and lock are using nftables
2025-02-15 11:49:25 Kernel module nf_tables is already loaded
2025-02-15 11:49:25 Network filter successfully initialized
2025-02-15 11:49:25 Private network is allowed to pass the network filter
2025-02-15 11:49:25 ERROR: Cannot start WireGuard connection. Client name and user name (system login name) not pro
vided.
2025-02-15 11:49:25 Bluetit session terminated

Staff

2 hours ago, colorman said:

But still error;

Hello!

2 hours ago, colorman said:

2025-02-15 11:49:25 ERROR: Cannot start WireGuard connection. Client name and user name (system login name) not provided.

We managed to reproduce the bug by trying to launch Goldcrest by both airvpn (or users in the airvpn group) and root. We will address the problem in the next beta version. In the meantime (so you can continue testing) please do not use a configuration file for WireGuard connections. Run Hummingbird directly when you want to establish a WireGuard connection through a configuration file and run Goldcrest for AirVPN integration.

Thank you for your tests!

Kind regards

colorman

1 minute ago, Staff said:

Hello!

We managed to reproduce the bug by trying to launch Goldcrest by both airvpn (or users in the airvpn group) and root. We will address the problem in the next beta version. In the meantime (so you can continue testing) please do not use a configuration file for WireGuard connections. Run Hummingbird directly when you want to establish a connection through a configuration file and run Goldcrest for AirVPN integration.

Thank you for your tests!

Kind regards

Thanks..
Use Eddie now

jeffiscow

Hey Y'all!

First I'd like to say this tool seems awesome that for the handwork and support.

I've been having a problem after I tried opening a port for p2p on the Airvpn site and binding it to my bittorrent client bluetit detected 2 dns and shutdown and locked and was getting the "lock file --recover-network" message. I was able to fix that but now was getting a “D-Bus serviceorg.airvpn.server is not available” message. After trying everything I could find on the forums and the only thing that has fixed it was reinstalling, I figured I'd check if the Arch had a package in the AUR.

There are a few things I tried airvpn-suite-beta-bin 2.0.0-3 and this is what happened:

myusername@ArchLaptop % yain airvpn-suite-beta-bin                                                                                                                                                                  ~
AUR Explicit (1): airvpn-suite-beta-bin-2.0.0-3
:: (1/1) Downloaded PKGBUILD: airvpn-suite-beta-bin
  1 airvpn-suite-beta-bin                    (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> a
:: Deleting (1/1): /home/jeffiscow/.cache/yay/airvpn-suite-beta-bin
HEAD is now at b19ea8b pkgver++; arch=armv7h; license=GPL-3.0-only
  1 airvpn-suite-beta-bin                    (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> a

:: Proceed with install? [Y/n] y
==> Making package: airvpn-suite-beta-bin 2.0.0-3 (Sat 08 Mar 2025 11:18:48 AM EST)
==> Retrieving sources...
  -> Downloading AirVPN-Suite-x86_64-2.0.0-beta-1.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 3877k  100 3877k    0     0  3234k      0  0:00:01  0:00:01 --:--:-- 3236k
  -> Found airvpn-suite.sysusers
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha512sums...
    AirVPN-Suite-x86_64-2.0.0-beta-1.tar.gz ... Passed
    airvpn-suite.sysusers ... Passed
:: (1/1) Parsing SRCINFO: airvpn-suite-beta-bin
==> Making package: airvpn-suite-beta-bin 2.0.0-3 (Sat 08 Mar 2025 11:18:52 AM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found AirVPN-Suite-x86_64-2.0.0-beta-1.tar.gz
  -> Found airvpn-suite.sysusers
==> Validating source files with sha512sums...
    AirVPN-Suite-x86_64-2.0.0-beta-1.tar.gz ... Passed
    airvpn-suite.sysusers ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting AirVPN-Suite-x86_64-2.0.0-beta-1.tar.gz with bsdtar
==> Sources are ready.
==> Making package: airvpn-suite-beta-bin 2.0.0-3 (Sat 08 Mar 2025 11:18:56 AM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Entering fakeroot environment...
==> Starting package()...
install: invalid group 'airvpn'
==> ERROR: A failure occurred in package().
    Aborting...
 -> error making: airvpn-suite-beta-bin-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
airvpn-suite-beta-bin - exit status 4

Is this saying I need to create the “airvpn” group before I install the package, and if so, any idea what permissions and setting that group would need?

inxi print out for ya if that helps.

Thanks in advance!

inxi.txt

OpenSourcerer

I see my lapse in thinking there. In package(), the cuckoo binary is copied with airvpn as its group, but this group is only created in pacman's post-transaction hooks, after a package is installed. Since it's not able to create the package in the first place, airvpn-suite-beta-bin 2.0.0-3 is upgradeable (since the airvpn group would exist already) , but uninstallable from scratch.
I don't know that "yain" program you use (yay fork?), but if there is an option to edit the PKGBUILD before installing, comment out line 34, otherwise edit the PKGBUILD and build using makepkg:

34   # install -Dm4755 -g airvpn bin/cuckoo "$pkgdir/usr/bin/cuckoo"

makepkg -sCcri

After installing, set mode of cuckoo to 4755 and change group to airvpn:

# chmod 4755 /usr/bin/cuckoo
# chgrp airvpn /usr/bin/cuckoo

Be advised that the package is unmaintained. I abandoned maintainership of all Suite packages two months ago.

jeffiscow

@OpenSourcerer
I'm in the process of learning about Linux, security and how to best use of VPNs, so I apologize for not including everything I tried first before coming to the forum to ask for help. I didn't want to write a novel. My thought process on using the package from the AUR was It would save time and energy when installing and reinstalling. Also, “yain” is just an alias I set for “sudo yay -S”.

I didn't realize at the time the package was unmaintained, but know that I know I'll go back and try setting up Suite the suggested way. If I run into the "--recover-network" not working again I'll post the bluetit log and whatever is recommended and advised.

colorman

@Staff
Is there any development on the next Beta version?
It's very quiet.
Thanks in advance

Staff

14 hours ago, colorman said:

@Staff
Is there any development on the next Beta version?
It's very quiet.
Thanks in advance

Hello!

Yes, there has been intensive work behind the scenes to fix some tricky bugs and improve the implementation of specific parts (special thanks to beta testers behind the scenes). The next beta version, or perhaps the first Release Candidate, is scheduled for the very first days of April.

Kind regards

Staff

Hello!

We're very glad to inform you that AirVPN Suite 2.0.0 beta 5 for Linux is now available. The original post link is updated to show the new download URLs. This is an extensive bug fix version addressing all the issues reported ever since beta 4 was released and with the addition of new Network Lock related options offering more flexibility. Now you can accept or deny incoming, outgoing or both ICMP-echo packets, and independently you can permit or forbid IPv6 NDP, which is based on ICMPv6. The new options supported by Bluetit and Hummingbird are:

allowping [on | off | input | output], default: output
allowipv6ndp [on | off], default: on

The Goldcrest and Hummingbird corresponding options are:
--allow-ping
--allow-ipv6ndp

with the very same possible values and default settings. EDIT: BUG/error: the Hummingbird default value of allow-ping is "on" - please take note! It will be fixed in the next version.

Please check the changelogs for each application included in the packages to see all the changes in detail.

Kind regards and datalove
AirVPN Staff

colorman

with openSUSE 15.6 it seems ok now.
also with goldcrest.
good work. 😀

Staff

Hello!

We're very glad to inform you that AirVPN Suite 2.0.0 Release Candidate 1 for Linux is now available. The original post link is updated to show the new download URLs. The important differences from beta 5 are:

a bug causing a crash when nft error messages exceeded a definite size has been fully addressed
Bluetit features additional pause and re-connection attempts aimed at facilitating re-connection at system resume after suspension and other situations
Hummingbirtd --allow-ping default value is now "output"

Special note for firewalld users

Please read here, it's very important: https://airvpn.org/forums/topic/70164-linux-network-lock-and-firewalld/

Please note that from now on compatibility with Debian 10 and its derivatives, that reached end of long term support and end of life on June 2024, is lost even for the legacy version, mainly because the Suite is now C++20 compliant. The legacy version remains suitable for Debian 11 and its derivatives.

Kind regards

183aTr78f9o

@Staff
Are NixOS packages planned at some point, after the stable version is released? Just curious.

Staff

14 hours ago, 183aTr78f9o said:

@Staff
Are NixOS packages planned at some point, after the stable version is released? Just curious.

Hello!

The Suite distribution concept avoids any specific package manager for their excessive proliferation. Most of these package managers are incompatible with each other. We count nowadays 18 package managers on 800+ different distributions. Development team is committed to offering exclusively tarballs and an installation script written in sh to ensure compatibility with a wide range of distributions.

Kind regards

Staff

Hello!

We're very glad to inform you that AirVPN Suite 2.0.0 Release Candidate 2 for Linux is now available. The original post is updated to show the new download URLs. The important improvements over RC 1 are:

Cuckoo's design flaw has been fixed. Now cuckoo can be run when no graphic environment is installed
added check and warning to clearly inform the user when firewalld is configured to be the exclusive owner of its tables / chains / rules
in case VPN is busy in a pending process (such as reconnecting) stop_connection command is not performed by Bluetit, thus avoiding potential problems
a few changes to greatly improve network management during sessions based on WireGuard
libxml2 is now statically linked. This pondered decision was driven by various problems caused by a few Linux distributions inconsistencies with established practices and standards
linked against the new OpenVPN3-AirVPN 3.12 library

Special note for firewalld users

Please read here, it's very important: https://airvpn.org/forums/topic/70164-linux-network-lock-and-firewalld/

Please note that compatibility with Debian 10 and its derivatives, that reached end of long term support and end of life on June 2024, is lost even for the legacy version, mainly because the Suite is now C++20 compliant. The legacy version remains suitable for Debian 11 and its derivatives.

Kind regards

jeffiscow

Awesome! Going to give it another go with this release, will report back. Any public repos to post issues to? It seems like the GitLab reop hasnt been updated in bit.

On 6/10/2025 at 8:41 AM, Staff said:

Special note for firewalld users
Please read here, it's very important: https://airvpn.org/forums/topic/70164-linux-network-lock-and-firewalld/

Thanks for this, I'm a firewalld fan would have been trying to mess with this to fix it forever!

Pwbkkee

Bluetit 2.0.0 RC 2 does not exit cleanly. Either it fails with SIGSEGV when Goldcrest is terminated or it fails with SIGABRT when systemd sends it a SIGTERM.

Here is the log showing Bluetit's SIGABRT failure:

Jun 25 01:03:00 systemd[962]: Stopping goldcrest@Delphinus.service - Goldcrest...
Jun 25 01:03:00 bluetit[1288]: Requested method "bluetit_status -> Bluetit is connected to VPN (OpenVPN)"
Jun 25 01:03:00 bluetit[1288]: Requested method "stop_connection"
Jun 25 01:03:00 bluetit[1288]: Stopping OpenVPN synchronous connection
Jun 25 01:03:00 bluetit[1288]: Connection statistics updater thread terminated
Jun 25 01:03:00 bluetit[1288]: OpenVPN3 connection thread terminated
Jun 25 01:03:00 systemd-networkd[646]: tun0: Link DOWN
Jun 25 01:03:00 systemd-networkd[646]: tun0: Lost carrier
Jun 25 01:03:00 bluetit[1288]: Sending event 'event_disconnected'
Jun 25 01:03:00 bluetit[1288]: Connection time: 04:00:56
Jun 25 01:03:00 bluetit[1288]: Total transferred Input data: 39.03 MB
Jun 25 01:03:00 bluetit[1288]: Total transferred Output data: 2.67 MB
Jun 25 01:03:00 bluetit[1288]: Max Input rate: 542.04 Kbit/s
Jun 25 01:03:00 bluetit[1288]: Max Output rate: 55.31 Kbit/s
Jun 25 01:03:00 bluetit[1288]: Logging out AirVPN user Pwbkkee
Jun 25 01:03:00 bluetit[1288]: Sending event 'event_end_of_session'
Jun 25 01:03:00 bluetit[1288]: Sending event 'event_end_of_session'
Jun 25 01:03:00 dbus-daemon[642]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.39" (uid=1000 pid=1298 comm="/usr/local/bin/goldcrest --air-connect --air-serve") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.37" (uid=0 pid=1288 comm="/usr/local/bin/bluetit")
Jun 25 01:03:00 systemd[962]: Stopped goldcrest@Delphinus.service - Goldcrest.
Jun 25 01:03:00 systemd[962]: goldcrest@Delphinus.service: Consumed 6.388s CPU time.
Jun 25 01:04:00 sudo[3244]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/systemctl stop bluetit.service
Jun 25 01:04:00 sudo[3244]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Jun 25 01:04:00 bluetit[1288]: Received Terminated signal. Terminating Bluetit.
Jun 25 01:04:00 systemd[1]: Stopping bluetit.service - AirVPN Bluetit Daemon...
Jun 25 01:04:00 bluetit[1288]: AirVPN Manifest updater thread terminated
Jun 25 01:04:00 bluetit[1288]: Sending event 'event_end_of_session'
Jun 25 01:04:00 systemd[1]: bluetit.service: Main process exited, code=dumped, status=6/ABRT
Jun 25 01:04:00 systemd[1]: bluetit.service: Failed with result 'core-dump'.
Jun 25 01:04:00 systemd[1]: Stopped bluetit.service - AirVPN Bluetit Daemon.
Jun 25 01:04:00 systemd[1]: bluetit.service: Consumed 8.632s CPU time.

Here is my bluetit.service file:

[Unit]
Description=AirVPN Bluetit Daemon
[Service]
CapabilityBoundingSet=CAP_NET_ADMIN
ConfigurationDirectory=airvpn
DeviceAllow=/dev/net/tun rw
DevicePolicy=closed
ExecStart=/usr/local/bin/bluetit
KillMode=mixed
LockPersonality=true
MemoryDenyWriteExecute=true
Nice=-10
NoNewPrivileges=true
PrivateIPC=true
PrivateMounts=true
PrivateTmp=true
ProtectControlGroups=true
ProtectHome=true
ProtectHostname=true
ProtectKernelLogs=true
ProtectKernelModules=true
ProtectKernelTunables=true
ProtectProc=invisible
ProtectSystem=strict
RemoveIPC=true
RestrictAddressFamilies=AF_ALG AF_INET AF_INET6 AF_NETLINK AF_UNIX
RestrictNamespaces=true
RestrictRealtime=true
RestrictSUIDSGID=true
SystemCallArchitectures=native
SystemCallErrorNumber=EPERM
SystemCallFilter=@system-service
Type=forking
WorkingDirectory=/etc/airvpn

Here is my goldcrest@.service file:

[Unit]
Description=Goldcrest
[Service]
DevicePolicy=closed
ExecStart=/usr/local/bin/goldcrest --air-connect --air-server %i
LockPersonality=true
MemoryDenyWriteExecute=true
NoNewPrivileges=true
RestrictAddressFamilies=AF_UNIX
RestrictNamespaces=true
RestrictNetworkInterfaces=lo
RestrictRealtime=true
RestrictSUIDSGID=true
Slice=background.slice
StandardError=null
StandardOutput=null
SystemCallArchitectures=native
SystemCallErrorNumber=EPERM
SystemCallFilter=@system-service

My system is running Debian 12 "bookworm" with linux 6.1.140-1 and systemd 254.26~bpo12+1.

Staff

@Pwbkkee

Hello and thank you for your tests!

Please post at your convenience the complete Bluetit log to let us investigate.

Suite components are designed after a client-daemon architecture, where Bluetit is a real daemon (not a generic service, a real daemon) and Goldcrest is a client. Your setup is odd and poses a few problems, since you turn a client into a service and you try to have a service-service arch.

What is it that you can't do with current architecture that forces you into this sort of aberration? For example, in your case if you want Bluetit to connect by itself you don't need an auxiliary service, you can do it through the run control directives in bluetit.rc file and you would have a connection as soon as Bluetit comes up, instead of being forced to wait for yet another service to come up.

Kind regards

Pwbkkee

The log snippet that I posted is the full log concerning the SIGABRT failure. The rest of Bluetit's log shows nothing abnormal. Only 2.0.0 RC2 has this issue; all previous versions of Bluetit exited cleanly.

My setup allows me to run both Bluetit and Goldcrest in sandboxed environments. It also allows me to run Goldcrest in the background without using screen. I start and stop both Bluetit and Goldcrest manually, and my goldcrest@.service file allows me to specify which server I want to connect to. I can't do that with Bluetit's automatic connection feature.

Staff

9 hours ago, Pwbkkee said:

Only 2.0.0 RC2 has this issue; all previous versions of Bluetit exited cleanly.

Thank you, under investigation.

Quote

it also allows me to run Goldcrest in the background without using screen

screen or any other multiplexer is unnecessary thanks to the async mode (option --async). We will keep you posted.

Kind regards

Staff

@Pwbkkee

Hello!

After extensive debugging we noticed that Bluetit does not crash, but WireGuard does. Please note that in your setup the following option on the bluetit.service file you created:

ProtectKernelModules=true

prevents Bluetit from loading firewall and WireGuard kernel modules, which are needed respectively for Network Lock and WireGuard proper functioning. The following one:

RestrictNamespaces=true

prevents traffic splitting.

The absence of ConfigurationDirectoryMode= with ConfigurationDirectory=airvpn implies a change of permission in /etc/airvpn (by default 660) with subsequent security problems that must be seriously considered, otherwise the unit can not work in general.

Running Goldcrest as a service must also be carefully considered and whenever possible Goldcrest should work as it was designed for, i.e. as a client, with the asynchronous mode in your case. Goldcrest keeps all the standard streams (stdin, stdout and stderr, including TTY access) open, whereas Bluetit does not, as it is a real daemon, not a systemd service, which is only a pale daemon surrogate if you want to be kind, or a fake if you want to call a spade a spade. Therefore running Goldcrest with root privileges by systemd is another security flaw that must be pondered.

Other directives could introduce additional problems, but we haven't investigated deeply all of them, we just want to point you toward the main problems and explain the issue you experience.

The whole setup introduces instability, causes WireGuard and OpenVPN3-AirVPN library to crash, lowers security and prevents important Bluetit features including Network Lock, so proceed only if you know exactly what you're doing and always consider the instability that you cause especially on WireGuard and OpenVPN library.

Kind regards

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>

Linux: AirVPN Suite 2.0.0 preview available

Recommended Posts

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

NOT AN AIRVPN TEAM MEMBER. USE TICKETS FOR PROFESSIONAL SUPPORT.

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Join the conversation