SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-18 14:11:56 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Different behaviour of netbird client in centos 8 stream and centos 9 stream peers #615

New Issue
Closed
opened 2025-11-20 05:14:45 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 05:14:45 -05:00
Owner
Copy Link

Originally created by @devopskupryk on GitHub (Feb 8, 2024).

Describe the problem

I have installed netbird client on two hosts:
gateway-yc - centos 8 stream
gateway-replica-yc - centos 9 stream

@gateway-yc ~]$ netbird status

Daemon version: 0.25.4
CLI version: 0.25.4
Management: Connected
Signal: Connected
FQDN: gateway-yc.vpn.hidden.tech
NetBird IP: 100.77.154.30/16
Interface type: Userspace
Peers count: 33/43 Connected

@gateway-replica-yc ~]$ netbird status

Daemon version: 0.25.6
CLI version: 0.25.6
Management: Connected
Signal: Connected
Relays: 2/2 Available
FQDN: gateway-replica-yc.vpn.hidden.tech
NetBird IP: 100.77.122.227/16
Interface type: Kernel
Peers count: 33/43 Connected

Netbird client adds different netbird nameservers in the /etc/resolv.conf of these hosts
@gateway-yc ~]$ cat /etc/resolv.conf

# Generated by NetBird
# If needed you can restore the original file by copying back /etc/resolv.conf.original.netbird

search vpn.hidden.tech ru-central1.internal auto.internal
nameserver **100.77.255.254**
nameserver 172.26.60.2
nameserver 1.1.1.1
nameserver 8.8.8.8

@gateway-replica-yc ~]$ cat /etc/resolv.conf

# Generated by NetBird
# If needed you can restore the original file by copying back /etc/resolv.conf.original.netbird

search vpn.hidden.tech ru-central1.internal auto.internal
nameserver **100.77.122.227**
nameserver 172.26.64.2
nameserver 1.1.1.1
nameserver 8.8.8.8

I don't know whose ip 100.77.255.254 is.
100.77.122.227 - this is an ip of the gateway-replica-yc peer.
Looks like netbird client starts some local resolver on the gateway-replica-yc:
gateway-replica-yc ~]$ sudo ss -ntupl | grep 53
udp UNCONN 0 0 100.77.122.227:53 0.0.0.0:* users:(("netbird",pid=739,fd=22))

This two hosts are in the local network and they are used as failover routers between local network and netbird vpn network.
I want to specify netbird nameserver on the other hosts in my local network for asking netbird peers by fqdns.
If I specify (on some host in local network) nameserver 100.77.255.254 and route to this ip via gateway-yc then dns resolution works on this host.
If I specify (on some host in local network) nameserver 100.77.255.254 and route to this ip via gateway-replica-yc then dns resolution doesn't work on this hosts. gateway-replica-yc doesn't resolve netbird peers fqdns via 100.77.255.254 too.

I have some questions:

  1. Why gateway-replica-yc doesn't get the same nameserver 100.77.255.254 (like gateway-yc) but start local resolver instead?
  2. Why is there no access to the 100.77.255.254 from gateway-replica-yc?
  3. Is it possible to configure netbird client on gateway-replica-yc like on gateway-yc to get nameserver 100.77.255.254 with access to?
  4. Is it possible to configure netbird client on gateway-yc like on gateway-replica-yc to start local resolver?
  5. Is it possible to configure local netbird resolver to get dns requests (and to provide response to them) from local network?

To Reproduce
Just netbird up

Expected behavior
Both hosts (gateway-yc and gateway-replica-yc) get the same dns configuration - nameserver 100.77.255.254 in /etc/resolv.conf

Are you using NetBird Cloud?

I use self-host NetBird's control plane.

Originally created by @devopskupryk on GitHub (Feb 8, 2024). **Describe the problem** I have installed netbird client on two hosts: gateway-yc - centos 8 stream gateway-replica-yc - centos 9 stream @gateway-yc ~]$ netbird status ``` Daemon version: 0.25.4 CLI version: 0.25.4 Management: Connected Signal: Connected FQDN: gateway-yc.vpn.hidden.tech NetBird IP: 100.77.154.30/16 Interface type: Userspace Peers count: 33/43 Connected ``` @gateway-replica-yc ~]$ netbird status ``` Daemon version: 0.25.6 CLI version: 0.25.6 Management: Connected Signal: Connected Relays: 2/2 Available FQDN: gateway-replica-yc.vpn.hidden.tech NetBird IP: 100.77.122.227/16 Interface type: Kernel Peers count: 33/43 Connected ``` Netbird client adds different netbird nameservers in the /etc/resolv.conf of these hosts @gateway-yc ~]$ cat /etc/resolv.conf ``` # Generated by NetBird # If needed you can restore the original file by copying back /etc/resolv.conf.original.netbird search vpn.hidden.tech ru-central1.internal auto.internal nameserver **100.77.255.254** nameserver 172.26.60.2 nameserver 1.1.1.1 nameserver 8.8.8.8 ``` @gateway-replica-yc ~]$ cat /etc/resolv.conf ``` # Generated by NetBird # If needed you can restore the original file by copying back /etc/resolv.conf.original.netbird search vpn.hidden.tech ru-central1.internal auto.internal nameserver **100.77.122.227** nameserver 172.26.64.2 nameserver 1.1.1.1 nameserver 8.8.8.8 ``` I don't know whose ip 100.77.255.254 is. 100.77.122.227 - this is an ip of the gateway-replica-yc peer. Looks like netbird client starts some local resolver on the gateway-replica-yc: gateway-replica-yc ~]$ sudo ss -ntupl | grep 53 `udp UNCONN 0 0 100.77.122.227:53 0.0.0.0:* users:(("netbird",pid=739,fd=22)) ` This two hosts are in the local network and they are used as failover routers between local network and netbird vpn network. I want to specify netbird nameserver on the other hosts in my local network for asking netbird peers by fqdns. If I specify (on some host in local network) nameserver 100.77.255.254 and route to this ip via gateway-yc then dns resolution works on this host. If I specify (on some host in local network) nameserver 100.77.255.254 and route to this ip via gateway-replica-yc then dns resolution doesn't work on this hosts. gateway-replica-yc doesn't resolve netbird peers fqdns via 100.77.255.254 too. I have some questions: 1. Why gateway-replica-yc doesn't get the same nameserver 100.77.255.254 (like gateway-yc) but start local resolver instead? 3. Why is there no access to the 100.77.255.254 from gateway-replica-yc? 4. Is it possible to configure netbird client on gateway-replica-yc like on gateway-yc to get nameserver 100.77.255.254 with access to? 5. Is it possible to configure netbird client on gateway-yc like on gateway-replica-yc to start local resolver? 6. Is it possible to configure local netbird resolver to get dns requests (and to provide response to them) from local network? **To Reproduce** Just netbird up **Expected behavior** Both hosts (gateway-yc and gateway-replica-yc) get the same dns configuration - nameserver 100.77.255.254 in /etc/resolv.conf **Are you using NetBird Cloud?** I use self-host NetBird's control plane.
saavagebueno added the question label 2025-11-20 05:14:45 -05:00
saavagebueno commented 2025-11-20 05:14:46 -05:00
Author
Owner
Copy Link

@nazarewk commented on GitHub (Apr 18, 2025):

  • 100.XXX.255.254 is a kind of reserved/unused address for the network used by default on all systems except Linux, I was not aware Linux ever used this
  • linux spins up a DNS forwarder on the IP address assigned to the wt0 (or whatever is a NetBird interface)

feel free to comment/reopen if it doesn't resolve your questions

@nazarewk commented on GitHub (Apr 18, 2025): - `100.XXX.255.254` is a kind of reserved/unused address for the network used by default on all systems except Linux, I was not aware Linux ever used this - linux spins up a DNS forwarder on the IP address assigned to the `wt0` (or whatever is a NetBird interface) feel free to comment/reopen if it doesn't resolve your questions
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#615
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?