ANSWERED Can only connect to internet if Eddie is running

[bricksandmortar 7]

Hi, up until a few days ago, I was able to connect to the internet whether Eddie was connected or not. Now there seems to be no connectivity if I exit out of eddie. Unfortunately this is sometimes necessary because there are some sites that just will not work with VPN's. I have been using Airvpn for years without issue but this has become a bind. As far as I am aware, nothing has changed.

I am running Linux Mint 21.2 (Victoria) on a Lenovo laptop with an AMD Ryzen 5 5500U processor.

Here are the logs:- (I think I've done it right)

Eddie System/Environment Report - 25/09/2023 - 15:28 UTC

Eddie version: 2.23.1
Eddie OS build: linux_x64
Eddie architecture: x64
OS type: Linux
OS name: Linux Mint
OS version: 21.2 (Victoria)
OS architecture: x64
Mono /.Net Framework: 6.8.0.105 (Debian 6.8.0.105+dfsg-3.2 Wed Jun 30 05:34:49 UTC 2021); Framework: v4.0.30319
OpenVPN: 2.5.5 - OpenSSL 3.0.2 15 Mar 2022, LZO 2.10 (/usr/sbin/openvpn)
Hummingbird: Not available
WireGuard: 1.0.0
SSH: OpenSSH_8.9p1 Ubuntu-3ubuntu0.3, OpenSSL 3.0.2 15 Mar 2022 (/usr/bin/ssh)
SSL: 5.63 (/usr/bin/stunnel4)
Profile path: /home/primary/.config/eddie/default.profile
Data path: /home/primary/.config/eddie
Application path: /usr/lib/eddie-ui
Executable path: /usr/lib/eddie-ui/eddie-ui.exe
Command line arguments: (2 args) path.resources="/usr/share/eddie-ui" path.exec="/usr/bin/eddie-ui"
Network Lock Active: Yes, Linux nftables
Connected to VPN: Yes, Alshain
OS support IPv4: Yes
OS support IPv6: No
Detected DNS: 10.7.211.1
Test DNS IPv4: Ok
Test DNS IPv6: Failed
Test Ping IPv4: 102 ms
Test Ping IPv6: Failed
Test HTTP IPv4: Ok
Test HTTP IPv6: Error: Fetch url error:Couldn't connect to server
Test HTTPS: Ok
----------------------------
Important options not at defaults:

login: (omissis)
password: (omissis)
remember: True
servers.allowlist: 11afb4b44daab27cd43a86befc30c037b85f33b4508b5bc384e62fc6047324fd,20dc8ad0bdcd308532e267288a96f544097973189da6b23cf9343aed601d6b09,3b928e0251c5b18e89553ba51f2469ebf302df622b5025cfa40e304197b0628d,15d62d4848bf83a53a3802a3fd0703551a45aabac6735b54be63d6f6b45f901b,e98659a8610a1ab160d6aaf546ac583fbaed82cd520c13ec9db8a50846f4b0db,8a087281a360f0ee5d7b10b2fbdb176120c58e04ec599fa2fd594bc11681b75f,600bb65180381071c7d4e7e6f472233b6d0caeaabddf5ca2690a978fb59111dc,4d8372743530ac3f7b095f63b52f1240f1195595c4aa76ef63d01a77aafa7fb5,19663fc5a83c65aa1aaf1b5efe615714e7e4fbc8b0e5bd5793f0602a64019a43,0f75ed38c6976eb0d2c81c7efc9d38ea7ce93ca48b9dedfe853d07bd97153b21,af26f9891683e6935d3aa5a08f21e8e6957c0137f714399135f57e85ca8d1f16,177a1d3e9f639f05ddf2959ed07c96193505a2b5753fc0cb267a03226a3d9630,0cfd7ac924659206202eda92548908d15db32774d3c1099679cab967262f4f20,2698d7ee1f83d78c67af410733c99441222e229b57ed096a9e7c91e264c9986a,06a8a7f2450258e2994b65a711bba91e3a486b26856d34c4ea2332ff57cda768
mode.type: openvpn
mode.protocol: TCP
mode.alt: 2
proxy.mode: none
netlock: True
netlock.allow_dns: True
network.entry.iplayer: ipv4-only
network.ipv6.mode: block
network.ipv4.autoswitch: True
advanced.expert: True
ui.skip.provider.manifest.failed: True
ui.skip.promotional: True

----------------------------
Logs:

. 2023.09.25 16:08:48 - Eddie version: 2.23.1 / linux_x64, System: Linux, Name: Linux Mint, Version: 21.2 (Victoria), Mono/.Net: 6.8.0.105 (Debian 6.8.0.105+dfsg-3.2 Wed Jun 30 05:34:49 UTC 2021); Framework: v4.0.30319
. 2023.09.25 16:08:48 - Command line arguments (2): path.resources="/usr/share/eddie-ui" path.exec="/usr/bin/eddie-ui"
. 2023.09.25 16:08:48 - Collect network information
. 2023.09.25 16:08:49 - Reading options from /home/primary/.config/eddie/default.profile
. 2023.09.25 16:08:50 - OpenVPN - Version: 2.5.5 - OpenSSL 3.0.2 15 Mar 2022, LZO 2.10 (/usr/sbin/openvpn)
. 2023.09.25 16:08:50 - SSH - Version: OpenSSH_8.9p1 Ubuntu-3ubuntu0.3, OpenSSL 3.0.2 15 Mar 2022 (/usr/bin/ssh)
. 2023.09.25 16:08:50 - SSL - Version: 5.63 (/usr/bin/stunnel4)
. 2023.09.25 16:08:50 - systemd-resolved restarted
I 2023.09.25 16:08:51 - Ready
. 2023.09.25 16:08:52 - Collect information about AirVPN completed
! 2023.09.25 16:09:20 - Activation of Network Lock - Linux nftables
I 2023.09.25 16:09:32 - Session starting.
I 2023.09.25 16:09:33 - Checking authorization ...
. 2023.09.25 16:09:33 - IPv6 disabled on network adapter (default)
. 2023.09.25 16:09:33 - IPv6 disabled on network adapter (enp1s0)
. 2023.09.25 16:09:33 - IPv6 disabled on network adapter (wlp2s0)
! 2023.09.25 16:09:33 - Connecting to Alshain (United Kingdom of Great Britain and Northern Ireland, London)
. 2023.09.25 16:09:33 - Routes, add 217.151.98.165/32 for interface "wlp2s0".
. 2023.09.25 16:09:33 - Routes, add 217.151.98.165/32 for interface "wlp2s0", already exists.
. 2023.09.25 16:09:33 - OpenVPN > OpenVPN 2.5.5 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 14 2022
. 2023.09.25 16:09:33 - OpenVPN > library versions: OpenSSL 3.0.2 15 Mar 2022, LZO 2.10
. 2023.09.25 16:09:33 - OpenVPN > Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
. 2023.09.25 16:09:33 - OpenVPN > Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
. 2023.09.25 16:09:33 - OpenVPN > Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
. 2023.09.25 16:09:33 - OpenVPN > Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
. 2023.09.25 16:09:33 - OpenVPN > TCP/UDP: Preserving recently used remote address: [AF_INET]217.151.98.165:443
. 2023.09.25 16:09:33 - OpenVPN > Socket Buffers: R=[131072->131072] S=[16384->16384]
. 2023.09.25 16:09:33 - OpenVPN > Attempting to establish TCP connection with [AF_INET]217.151.98.165:443 [nonblock]
. 2023.09.25 16:09:33 - OpenVPN > TCP connection established with [AF_INET]217.151.98.165:443
. 2023.09.25 16:09:33 - OpenVPN > TCP_CLIENT link local: (not bound)
. 2023.09.25 16:09:33 - OpenVPN > TCP_CLIENT link remote: [AF_INET]217.151.98.165:443
. 2023.09.25 16:09:33 - OpenVPN > TLS: Initial packet from [AF_INET]217.151.98.165:443, sid=dd3afdfd cfce3e6e
. 2023.09.25 16:09:34 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
. 2023.09.25 16:09:34 - OpenVPN > VERIFY KU OK
. 2023.09.25 16:09:34 - OpenVPN > Validating certificate extended key usage
. 2023.09.25 16:09:34 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
. 2023.09.25 16:09:34 - OpenVPN > VERIFY EKU OK
. 2023.09.25 16:09:34 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Alshain, emailAddress=info@airvpn.org
. 2023.09.25 16:09:34 - OpenVPN > Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, peer certificate: 4096 bit RSA, signature: RSA-SHA512
. 2023.09.25 16:09:34 - OpenVPN > [Alshain] Peer Connection Initiated with [AF_INET]217.151.98.165:443
. 2023.09.25 16:09:34 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.7.211.1,dhcp-option DNS6 fde6:7a:7d20:3d3::1,tun-ipv6,route-gateway 10.7.211.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:7d20:3d3::102f/64 fde6:7a:7d20:3d3::1,ifconfig 10.7.211.49 255.255.255.0,peer-id 0,cipher AES-256-GCM'
. 2023.09.25 16:09:34 - OpenVPN > Pushed option removed by filter: 'redirect-gateway ipv6 def1 bypass-dhcp'
. 2023.09.25 16:09:34 - OpenVPN > Pushed option removed by filter: 'dhcp-option DNS 10.7.211.1'
. 2023.09.25 16:09:34 - OpenVPN > Pushed option removed by filter: 'dhcp-option DNS6 fde6:7a:7d20:3d3::1'
. 2023.09.25 16:09:34 - OpenVPN > Pushed option removed by filter: 'tun-ipv6'
. 2023.09.25 16:09:34 - OpenVPN > Pushed option removed by filter: 'ifconfig-ipv6 fde6:7a:7d20:3d3::102f/64 fde6:7a:7d20:3d3::1'
. 2023.09.25 16:09:34 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified
. 2023.09.25 16:09:34 - OpenVPN > OPTIONS IMPORT: compression parms modified
. 2023.09.25 16:09:34 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified
. 2023.09.25 16:09:34 - OpenVPN > OPTIONS IMPORT: route-related options modified
. 2023.09.25 16:09:34 - OpenVPN > OPTIONS IMPORT: peer-id set
. 2023.09.25 16:09:34 - OpenVPN > OPTIONS IMPORT: adjusting link_mtu to 1627
. 2023.09.25 16:09:34 - OpenVPN > OPTIONS IMPORT: data channel crypto options modified
. 2023.09.25 16:09:34 - OpenVPN > Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
. 2023.09.25 16:09:34 - OpenVPN > Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
. 2023.09.25 16:09:34 - OpenVPN > TUN/TAP device tun0 opened
. 2023.09.25 16:09:34 - OpenVPN > net_iface_mtu_set: mtu 1500 for tun0
. 2023.09.25 16:09:34 - OpenVPN > net_iface_up: set tun0 up
. 2023.09.25 16:09:34 - OpenVPN > net_addr_v4_add: 10.7.211.49/24 dev tun0
. 2023.09.25 16:09:34 - OpenVPN > Initialization Sequence Completed
. 2023.09.25 16:09:34 - DNS of the interface 'wlp2s0' switched to VPN DNS - via systemd-resolved
. 2023.09.25 16:09:34 - DNS of the interface 'tun0' switched to VPN DNS - via systemd-resolved
. 2023.09.25 16:09:34 - DNS of the system switched to VPN DNS - via /etc/resolv.conf)
. 2023.09.25 16:09:34 - Routes, add 0.0.0.0/1 for interface "tun0".
. 2023.09.25 16:09:35 - Routes, add 128.0.0.0/1 for interface "tun0".
. 2023.09.25 16:09:35 - Routes, add 217.151.98.163/32 for interface "tun0".
. 2023.09.25 16:09:35 - Routes, skipped for 2001:ac8:31:3:2926:7fe8:9d5e:812a : IPv6 blocked.
. 2023.09.25 16:09:35 - Flushing DNS
. 2023.09.25 16:09:35 - Flush DNS - systemd-resolved flush-caches
I 2023.09.25 16:09:35 - Checking route IPv4
I 2023.09.25 16:09:36 - Checking DNS
! 2023.09.25 16:09:37 - Connected.
. 2023.09.25 16:09:41 - DNS of the interface 'tun0' switched to VPN DNS - via systemd-resolved
. 2023.09.25 16:09:51 - DNS of the interface 'tun0' switched to VPN DNS - via systemd-resolved
. 2023.09.25 16:10:01 - DNS of the interface 'tun0' switched to VPN DNS - via systemd-resolved

----------------------------
Network Info:

{
    "routes": [
        {
            "destination": "0.0.0.0\/1",
            "interface": "tun0",
            "scope": "link"
        },
        {
            "destination": "0.0.0.0\/0",
            "gateway": "192.168.1.1",
            "interface": "wlp2s0",
            "metric": "20600",
            "proto": "dhcp"
        },
        {
            "destination": "10.7.211.0\/24",
            "interface": "tun0",
            "proto": "kernel",
            "scope": "link",
            "src": "10.7.211.49"
        },
        {
            "destination": "128.0.0.0\/1",
            "interface": "tun0",
            "scope": "link"
        },
        {
            "destination": "169.254.0.0\/16",
            "interface": "wlp2s0",
            "metric": "1000",
            "scope": "link"
        },
        {
            "destination": "192.168.1.0\/24",
            "interface": "wlp2s0",
            "metric": "600",
            "proto": "kernel",
            "scope": "link",
            "src": "192.168.1.238"
        },
        {
            "destination": "217.151.98.163\/32",
            "interface": "tun0",
            "scope": "link"
        },
        {
            "destination": "217.151.98.165\/32",
            "gateway": "192.168.1.1",
            "interface": "wlp2s0"
        },
        {
            "destination": "::1\/128",
            "interface": "lo",
            "metric": "256",
            "pref": "medium",
            "proto": "kernel"
        }
    ],
    "ipv4-default-gateway": "192.168.1.1",
    "ipv4-default-interface": "wlp2s0",
    "interfaces": [
        {
            "friendly": "lo",
            "id": "lo",
            "name": "lo",
            "description": "lo",
            "type": "Loopback",
            "status": "Unknown",
            "bytes_received": "256866733",
            "bytes_sent": "256866733",
            "support_ipv4": true,
            "support_ipv6": false,
            "ips": [
                "127.0.0.1",
                "::1"
            ],
            "bind": true
        },
        {
            "friendly": "enp1s0",
            "id": "enp1s0",
            "name": "enp1s0",
            "description": "enp1s0",
            "type": "Ethernet",
            "status": "Down",
            "bytes_received": "0",
            "bytes_sent": "0",
            "support_ipv4": true,
            "support_ipv6": false,
            "ips": [],
            "bind": false
        },
        {
            "friendly": "wlp2s0",
            "id": "wlp2s0",
            "name": "wlp2s0",
            "description": "wlp2s0",
            "type": "Wireless80211",
            "status": "Up",
            "bytes_received": "6429567021",
            "bytes_sent": "361297675",
            "support_ipv4": true,
            "support_ipv6": false,
            "ips": [
                "192.168.1.238"
            ],
            "bind": true
        },
        {
            "friendly": "tun0",
            "id": "tun0",
            "name": "tun0",
            "description": "tun0",
            "type": "0",
            "status": "Unknown",
            "bytes_received": "7291415",
            "bytes_sent": "622137",
            "support_ipv4": true,
            "support_ipv6": false,
            "ips": [
                "10.7.211.49"
            ],
            "bind": true
        }
    ]
}
----------------------------
ip addr show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 88:a4:c2:8b:96:54 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:45:e2:bc:f0:33 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.238/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp2s0
       valid_lft 84973sec preferred_lft 84973sec
13: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none
    inet 10.7.211.49/24 scope global tun0
       valid_lft forever preferred_lft forever
----------------------------
ip link show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 88:a4:c2:8b:96:54 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 00:45:e2:bc:f0:33 brd ff:ff:ff:ff:ff:ff
13: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 500
    link/none

From the research I've done it seems it's a DNS issue but the fixes/workarounds I've found have been windows based.

Any ideas? I'm stumped.
 

[OpenSourcerer 1361]

36 minutes ago, bricksandmortar said:

. 2023.09.25 16:09:34 - DNS of the system switched to VPN DNS - via /etc/resolv.conf)

If you disconnect, what's the content of this file?

[bricksandmortar 7]

Thanks for the reply, contents of /etc/resolv.conf
 

Quote

# Generated by Eddie v2.21.8 - https://eddie.website - 15 September 2023 21:40:17 UTC

nameserver 10.14.82.1

 

[OpenSourcerer 1361]

So, it's not reset to what it was before. I think systemd-resolved is to blame here. That file is not a regular file but a symlink in your case. Though I only faintly remember the solution. I will do some searching.

[bricksandmortar 7]

# Generated by Eddie v2.21.8 - https://eddie.website - 15 September 2023 21:40:17 UTC

nameserver 10.14.82.1Many thanks, not sure if this helps but...

There are two files /etc/resolve.conf.eddie which is a symlink and /etc/resolve.conf.eddievpn which contain...

resolve.conf.eddie (while eddie running and connected)

 

# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0 trust-ad
search lan

resolve.conf.eddievpn (while eddie running and connected)

[OpenSourcerer 1361]

Huh? What are the contents of that directory, then?

$ ls -la /etc/airvpn/

.

[bricksandmortar 7]

Sorry mate, not trying to be an asshole but I'm not sure what you mean.

The response to the command $ ls -la /etc/airvpn/ is...

ls: cannot access '/etc/airvpn/': No such file or directory

There's no airvpn directory within /etc

[OpenSourcerer 1361]

Oooh, right. T'was me mate, /etc/airvpn is used by the AirVPN suite, not by Eddie
Sorry, I meant this ls.

$ ls -la /etc/resolv*

And while you're at it, maybe their contents, too.

$ for file in /etc/resolv*; do echo -e "\n$file:\n--------------------\n"; cat $file; done

The reason I'm asking is that I don't understand what resolv.* files are there now. It's starting to look like Eddie is botching them accidentally, but I want to confirm this.

[bricksandmortar 7]

Reponse to $ ls -la /etc/resolv* 

-rw-r--r-- 1 root root 300 Sep 26 20:17 /etc/resolv.conf
lrwxrwxrwx 1 root root  39 Apr 25 23:34 /etc/resolv.conf.eddie -> ../run/systemd/resolve/stub-resolv.conf
-rw-r--r-- 1 root root 109 Sep 15 22:40 /etc/resolv.conf.eddievpn


Reponse to $ for file in /etc/resolv*; do echo -e "\nfile:\n--------------------\n"; cat $file; done

file:
--------------------

#
# Created by Eddie. Do not edit.
#
# Your resolv.conf file is temporarily backed up in /etc/resolv.conf.eddievpn
# To restore your resolv.conf file you need to log in as root
# and execute the below command from the shell:
#
# mv /etc/resolv.conf.eddievpn /etc/resolv.conf
#
nameserver 10.5.51.1



file:
--------------------

# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.53
options edns0 trust-ad
search lan

file:
--------------------

# Generated by Eddie v2.21.8 - https://eddie.website - 15 September 2023 21:40:17 UTC

nameserver 10.14.82.1

Hope this helps.
 

[OpenSourcerer 1361]

You forgot a $ in the echo… No matter, it's still readable.

So, okay, what I see is that both the flat-file /etc/resolv.conf and its backup are filled with AirDNS servers, so it doesn't matter whether VPN is on or off, you will not get DNS back using Eddie.
Meanwhile, the resolv.conf.eddie containing the stub resolver (and ultimately the file that will make DNS work again) is from… April.

The fix is thus, after ensuring Eddie is shut down, to remove the current resolv.conf and backup, then renaming the .eddie backup to resolv.conf.

$ rm /etc/resolv{.conf,.conf.eddievpn} && mv /etc/resolv.conf.eddie /etc/resolv.conf

.

[Staff 9765]

Hello!

Some context for the readers as well: Eddie 2.23.1 added full support with proper DNS management for every systemd-resolved working mode. Any older version will misbehave whenever systemd-resolved is running (various working modes are not supported).
AirVPN Suite added full support with proper DNS management for every systemd-resolved working mode in 2022 (1.2.0 or higher version).

Kind regards
 

[bricksandmortar 7]

Thank you opensourcerer, the fix worked, I needed superuser privileges but now all is well. Your time and patience is much appreciated.