Open eriverosr opened 6 months ago
jumski
commented
4 months ago I think i suffer from the same bug. I believe there is some kind of problem with managing /etc/resolv.conf when other process is also managing it (NetworkManager in my case).
This also manifests in the log output pasted by @eriverosr - in the first, correct one, you can grep for resolve.conf but the second log does not have entries about watching/managing this file.
The bug is extremely annoying :-(
jumski
commented
4 months ago This problem resolved itself on my end. I'm not sure if this was caused by recent update or my doings, but this is roughly what i did (maybe will be useful for someone):
stopped and uninstalled netbird service
set dns=none in NetworkManager.conf
set a simple resolv.conf with a single line
nameserver 1.1.1.1installed and started netbird service
i touched /etc/resolv.conf.original.netbird because i saw in logs lines about not being able to find/open this file -> not sure if it was necessary
netbird up --dns-resolver-address="" to reset the resolver
after those steps my /etc/resolv.conf looks like this:
# Generated by NetBird
# If needed you can restore the original file by copying back /etc/resolv.conf.original.netbird
options timeout:4 attempts:1
search netbird.cloud
nameserver 100.116.181.170
nameserver 1.1.1.1
Describe the problem
Since 0.25.6, if there is a NetBird peer in Linux with Network Manager and an internal nameserver configured (using internal-routed IPs), the routes assigned to the peer disappear after initial connection.
To Reproduce
Steps to reproduce the behavior:
watch -n 0.5 ip routeExpected behavior
Routes shouldn't be deleted if the peer has assigned an internal nameserver.
The problem does not occur if no nameserver or a public nameserver (Google/Cloudflare/Quad9/etc) is assigned to the Linux host.
The problem does not occur at all with version 0.25.5.
The problem does not occur with the Windows or macOS Client (I just have tested it with Arch Linux. I haven't got the opportunity to test it with Ubuntu)
Are you using NetBird Cloud?
No. I'm using the self-hosted version.
NetBird version
Client: 0.25.6, installed in an Arch Linux machine with NetworkManager (version 0.25.5 doesn't have this problem).
Screenshots
Nameserver:
Relevant Routes:
ACLs:
Peer:
Additional context
Logs during the client connection with NetBird Client v0.25.5 (everything works)
Logs during the client connection with NetBird Client v0.25.6 (routes dissapear)
dbus-monitorwhile connecting with both versions, and in the case of the client version 0.25.6 I received areApplyNetworkManager message that I didn´t saw with client version 0.25.5. That's why I think it could be related to NetworkManager.ip route add), everything works.