[GH-ISSUE #528] DNS/Routing Problem in Linux Client on openSUSE Tumbleweed #161

Closed
opened 2026-10-13 20:14:01 +00:00 by bsakaguchi · 7 comments
Owner

Originally created by @JackGin on GitHub (Jan 22, 2024).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/528

Hi guys,

I would like to extend my gratitude for your exceptional work in developing the Amnezia VPN project.

I am reaching out to report a potential bug I've encountered with the Linux client, specifically when operated on openSUSE Tumbleweed. Although the client successfully establishes a connection to the server, it appears to be facing a DNS/routing issue.

More precisely, while I am able to ping any IP address successfully, DNS resolution seems to be failing as I cannot access websites through a web browser. This issue persists regardless of whether Amnezia DNS is enabled or disabled.

I have tested this with two different versions of the client (4.1.0 and 4.2.0), and have experimented with both Amnezia WG and OpenVPN over Cloak protocols. Interestingly, the client functions without any such DNS issues on Android and Windows platforms when connecting to the same server.

I understand the complexities involved in maintaining cross-platform compatibility and appreciate any efforts you can make to investigate and resolve this issue. Your support in this matter would be greatly appreciated.

The logs say:
2024-01-22 17:10:02 debug Amnezia "DaemonLocalServer" "New connection received"
2024-01-22 17:10:02 debug Amnezia "DaemonLocalServerConnection" "Connection created"
2024-01-22 17:10:02 debug Amnezia "DaemonLocalServerConnection" "Read Data"
2024-01-22 17:10:02 debug Amnezia "DaemonLocalServerConnection" "Command received: status"
2024-01-22 17:10:02 debug Amnezia "Daemon" "Status request"
2024-01-22 17:10:02 debug Amnezia "DaemonLocalServerConnection" "Command received: activate"
2024-01-22 17:10:02 debug Amnezia "Daemon" "Activating interface"
2024-01-22 17:10:02 debug Amnezia "WireguardUtilsLinux" "Created wireguard interface amn0"
2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "LinuxRouteMonitor created."
2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding exclusion route for 153.92.126.74/32"
2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Gateway 10.0.0.1 for interface enp2s0"
2024-01-22 17:10:02 debug Amnezia "WireguardUtilsLinux" "Configuring peer 26/jz74o49mD0r4PBrw4MD8pVijp6k2/X5HsPS87mWI= via 153.92.126.74"
2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding exclusion route for 153.92.126.74/32"
2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Gateway 10.0.0.1 for interface enp2s0"
2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding exclusion route for /999999"
2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Invalid destination prefix"
2024-01-22 17:10:02 debug Amnezia "DnsUtilsLinux" "Adding DNS resolver 172.29.172.254 via amn0"
2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding route to 0.0.0.0/1"
2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding route to 128.0.0.0/1"
2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding route to ::/1"
2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding route to 8000::/1"
2024-01-22 17:10:02 debug Amnezia "Daemon" "Connection status: 1"
2024-01-22 17:10:02 debug Amnezia "DnsUtilsLinux" "Error received from the DBus service"
2024-01-22 17:10:02 debug Amnezia "DnsUtilsLinux" "Error received from the DBus service"
2024-01-22 17:10:02 debug Amnezia "DnsUtilsLinux" "Error retrieving the DNS domains from the DBus service"
2024-01-22 17:10:02 debug Amnezia "Daemon" "Checking for handshake..."
2024-01-22 17:10:02 debug Amnezia "Daemon" "awaiting 26/jz74o49mD0r4PBrw4MD8pVijp6k2/X5HsPS87mWI="
2024-01-22 17:10:02 debug Flush dns completed
2024-01-22 17:10:02 critical Critical, trying to add invalid route: 172.29.172.254
2024-01-22 17:10:02 critical Critical, trying to add invalid route: 1.0.0.1

Originally created by @JackGin on GitHub (Jan 22, 2024). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/528 Hi guys, I would like to extend my gratitude for your exceptional work in developing the Amnezia VPN project. I am reaching out to report a potential bug I've encountered with the Linux client, specifically when operated on openSUSE Tumbleweed. Although the client successfully establishes a connection to the server, it appears to be facing a DNS/routing issue. More precisely, while I am able to ping any IP address successfully, DNS resolution seems to be failing as I cannot access websites through a web browser. This issue persists regardless of whether Amnezia DNS is enabled or disabled. I have tested this with two different versions of the client (4.1.0 and 4.2.0), and have experimented with both Amnezia WG and OpenVPN over Cloak protocols. Interestingly, the client functions without any such DNS issues on Android and Windows platforms when connecting to the same server. I understand the complexities involved in maintaining cross-platform compatibility and appreciate any efforts you can make to investigate and resolve this issue. Your support in this matter would be greatly appreciated. The logs say: 2024-01-22 17:10:02 debug Amnezia "DaemonLocalServer" "New connection received" 2024-01-22 17:10:02 debug Amnezia "DaemonLocalServerConnection" "Connection created" 2024-01-22 17:10:02 debug Amnezia "DaemonLocalServerConnection" "Read Data" 2024-01-22 17:10:02 debug Amnezia "DaemonLocalServerConnection" "Command received: status" 2024-01-22 17:10:02 debug Amnezia "Daemon" "Status request" 2024-01-22 17:10:02 debug Amnezia "DaemonLocalServerConnection" "Command received: activate" 2024-01-22 17:10:02 debug Amnezia "Daemon" "Activating interface" 2024-01-22 17:10:02 debug Amnezia "WireguardUtilsLinux" "Created wireguard interface amn0" 2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "LinuxRouteMonitor created." 2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding exclusion route for 153.92.126.74/32" 2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Gateway 10.0.0.1 for interface enp2s0" 2024-01-22 17:10:02 debug Amnezia "WireguardUtilsLinux" "Configuring peer 26/jz74o49mD0r4PBrw4MD8pVijp6k2/X5HsPS87mWI= via 153.92.126.74" 2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding exclusion route for 153.92.126.74/32" 2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Gateway 10.0.0.1 for interface enp2s0" 2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding exclusion route for /999999" 2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Invalid destination prefix" 2024-01-22 17:10:02 debug Amnezia "DnsUtilsLinux" "Adding DNS resolver 172.29.172.254 via amn0" 2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding route to 0.0.0.0/1" 2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding route to 128.0.0.0/1" 2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding route to ::/1" 2024-01-22 17:10:02 debug Amnezia "LinuxRouteMonitor" "Adding route to 8000::/1" 2024-01-22 17:10:02 debug Amnezia "Daemon" "Connection status: 1" 2024-01-22 17:10:02 debug Amnezia "DnsUtilsLinux" "Error received from the DBus service" 2024-01-22 17:10:02 debug Amnezia "DnsUtilsLinux" "Error received from the DBus service" 2024-01-22 17:10:02 debug Amnezia "DnsUtilsLinux" "Error retrieving the DNS domains from the DBus service" 2024-01-22 17:10:02 debug Amnezia "Daemon" "Checking for handshake..." 2024-01-22 17:10:02 debug Amnezia "Daemon" "awaiting 26/jz74o49mD0r4PBrw4MD8pVijp6k2/X5HsPS87mWI=" 2024-01-22 17:10:02 debug Flush dns completed 2024-01-22 17:10:02 critical Critical, trying to add invalid route: 172.29.172.254 2024-01-22 17:10:02 critical Critical, trying to add invalid route: 1.0.0.1
Author
Owner

@JackGin commented on GitHub (Jan 24, 2024):

Turns out to be an issue with resolv.conf. Thanks once again. Closing.

<!-- gh-comment-id:1907409729 --> @JackGin commented on GitHub (Jan 24, 2024): Turns out to be an issue with resolv.conf. Thanks once again. Closing.
Author
Owner

@KDBal commented on GitHub (Apr 13, 2024):

Turns out to be an issue with resolv.conf. Thanks once again. Closing.

Could you, please, tell, how did you fix this issue? I have the same problem.

<!-- gh-comment-id:2053727048 --> @KDBal commented on GitHub (Apr 13, 2024): > Turns out to be an issue with resolv.conf. Thanks once again. Closing. Could you, please, tell, how did you fix this issue? I have the same problem.
Author
Owner

@SputerSnoot commented on GitHub (May 2, 2024):

Turns out to be an issue with resolv.conf. Thanks once again. Closing.

Could you, please, tell, how did you fix this issue? I have the same problem.

Assuming you're using NetworkManager:

  • Disable Automatic DNS Configuration: Add the following lines to /etc/NetworkManager/NetworkManager.conf:
[main]
dns=none

This prevents NetworkManager from automatically managing DNS configurations.

  • Replace everything in /etc/resolv.conf with this:
nameserver 1.1.1.1
nameserver 1.0.0.1

Now you should be able to browse the web.

Amnezia works poorly with NetworkManager, try other network manager like systemd-networkd or another alternatives https://wiki.archlinux.org/title/Network_configuration#Network_managers

<!-- gh-comment-id:2090616824 --> @SputerSnoot commented on GitHub (May 2, 2024): > > Turns out to be an issue with resolv.conf. Thanks once again. Closing. > > Could you, please, tell, how did you fix this issue? I have the same problem. Assuming you're using NetworkManager: - Disable Automatic DNS Configuration: Add the following lines to /etc/NetworkManager/NetworkManager.conf: ``` [main] dns=none ``` This prevents NetworkManager from automatically managing DNS configurations. - Replace everything in /etc/resolv.conf with this: ``` nameserver 1.1.1.1 nameserver 1.0.0.1 ``` Now you should be able to browse the web. Amnezia works poorly with NetworkManager, try other network manager like systemd-networkd or another alternatives https://wiki.archlinux.org/title/Network_configuration#Network_managers
Author
Owner

@IvanyaK commented on GitHub (Dec 7, 2024):

Turns out to be an issue with resolv.conf. Thanks once again. Closing.

Could you, please, tell, how did you fix this issue? I have the same problem.

Assuming you're using NetworkManager:

* Disable Automatic DNS Configuration: Add the following lines to /etc/NetworkManager/NetworkManager.conf:
[main]
dns=none

This prevents NetworkManager from automatically managing DNS configurations.

* Replace everything in /etc/resolv.conf with this:
nameserver 1.1.1.1
nameserver 1.0.0.1

Now you should be able to browse the web.

Amnezia works poorly with NetworkManager, try other network manager like systemd-networkd or another alternatives https://wiki.archlinux.org/title/Network_configuration#Network_managers

I had the same problem on opensuse tumbleweed, thanks for the solution

<!-- gh-comment-id:2525272497 --> @IvanyaK commented on GitHub (Dec 7, 2024): > > > Turns out to be an issue with resolv.conf. Thanks once again. Closing. > > > > > > Could you, please, tell, how did you fix this issue? I have the same problem. > > Assuming you're using NetworkManager: > > * Disable Automatic DNS Configuration: Add the following lines to /etc/NetworkManager/NetworkManager.conf: > > > ``` > [main] > dns=none > ``` > > This prevents NetworkManager from automatically managing DNS configurations. > > * Replace everything in /etc/resolv.conf with this: > > > ``` > nameserver 1.1.1.1 > nameserver 1.0.0.1 > ``` > > Now you should be able to browse the web. > > Amnezia works poorly with NetworkManager, try other network manager like systemd-networkd or another alternatives https://wiki.archlinux.org/title/Network_configuration#Network_managers I had the same problem on opensuse tumbleweed, thanks for the solution
Author
Owner

@Flashwalker commented on GitHub (Jul 3, 2025):

Turns out to be an issue with resolv.conf. Thanks once again. Closing.

Could you, please, tell, how did you fix this issue? I have the same problem.

Assuming you're using NetworkManager:

  • Disable Automatic DNS Configuration: Add the following lines to /etc/NetworkManager/NetworkManager.conf:
[main]
dns=none

This prevents NetworkManager from automatically managing DNS configurations.

  • Replace everything in /etc/resolv.conf with this:
nameserver 1.1.1.1
nameserver 1.0.0.1

Now you should be able to browse the web.

Amnezia works poorly with NetworkManager, try other network manager like systemd-networkd or another alternatives https://wiki.archlinux.org/title/Network_configuration#Network_managers

This is really the improper solution.
/etc/resolv.conf should not be edited manually. This file will be overwritten by systemd or NetworkManager

<!-- gh-comment-id:3033007882 --> @Flashwalker commented on GitHub (Jul 3, 2025): > > > Turns out to be an issue with resolv.conf. Thanks once again. Closing. > > > > > > Could you, please, tell, how did you fix this issue? I have the same problem. > > Assuming you're using NetworkManager: > > * Disable Automatic DNS Configuration: Add the following lines to /etc/NetworkManager/NetworkManager.conf: > > ``` > [main] > dns=none > ``` > > This prevents NetworkManager from automatically managing DNS configurations. > > * Replace everything in /etc/resolv.conf with this: > > ``` > nameserver 1.1.1.1 > nameserver 1.0.0.1 > ``` > > Now you should be able to browse the web. > > Amnezia works poorly with NetworkManager, try other network manager like systemd-networkd or another alternatives https://wiki.archlinux.org/title/Network_configuration#Network_managers This is really the improper solution. /etc/resolv.conf should not be edited manually. This file will be overwritten by systemd or NetworkManager
Author
Owner

@Pentatonix0 commented on GitHub (Nov 6, 2025):

I'm facing a similar problem. The following helped me:

Before editing /etc/resolv.conf, disable systemd-resolved

sudo systemctl stop systemd-resolved
sudo systemctl disable systemd-resolved
<!-- gh-comment-id:3496068192 --> @Pentatonix0 commented on GitHub (Nov 6, 2025): I'm facing a similar problem. The following helped me: Before editing `/etc/resolv.conf`, disable systemd-resolved ``` sudo systemctl stop systemd-resolved sudo systemctl disable systemd-resolved ```
Author
Owner

@yablokozolotov commented on GitHub (Dec 7, 2025):

I'm facing a similar problem. The following helped me:

Before editing /etc/resolv.conf, disable systemd-resolved

sudo systemctl stop systemd-resolved
sudo systemctl disable systemd-resolved

user@localhost:~> sudo systemctl stop systemd-resolved' 'Failed to stop systemd-resolved.service: Unit systemd-resolved.service not loaded.' 'user@localhost:~> sudo systemctl disable systemd-resolved' 'Failed to disable unit: Unit systemd-resolved.service does not exis

<!-- gh-comment-id:3622971650 --> @yablokozolotov commented on GitHub (Dec 7, 2025): > I'm facing a similar problem. The following helped me: > > Before editing `/etc/resolv.conf`, disable systemd-resolved > > ``` > sudo systemctl stop systemd-resolved > sudo systemctl disable systemd-resolved > ``` `user@localhost:~> sudo systemctl stop systemd-resolved' 'Failed to stop systemd-resolved.service: Unit systemd-resolved.service not loaded.' 'user@localhost:~> sudo systemctl disable systemd-resolved' 'Failed to disable unit: Unit systemd-resolved.service does not exis`
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
amnezia-vpn/amnezia-client#161
No description provided.