[GH-ISSUE #1787] Linux peer cannot connect to other peers, for no apparent reason #3194

Open
opened 2026-08-05 00:51:08 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @acarstoiu on GitHub (Apr 2, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1787

Describe the problem

I'm using the free cloud plan of Netbird since before there were any paid plans and the serice was in its early days. Never had any connection problems with the other peers, in spite of the fact that there's no package for my distribution, Gentoo.
But after upgrading from 0.25.3 to 0.26.7 my peer is unable to connect to other peers. Initially the service complained in its log file about being unable to instantiate an "eBPF proxy" using the kernel or some user space replacement. I've read this article and configured my kernel according to the needs, which made the log file look like this (log level set to trace):

2024-04-01T19:32:45+03:00 INFO client/cmd/service_controller.go:24: starting Netbird service
2024-04-01T19:32:45+03:00 TRAC client/server/server.go:184: running client connection
2024-04-01T19:32:45+03:00 INFO client/cmd/service_controller.go:64: started daemon server: /var/run/netbird.sock
2024-04-01T19:32:45+03:00 INFO client/internal/connect.go:96: starting NetBird client version 0.26.7
2024-04-01T19:32:45+03:00 DEBG client/internal/connect.go:157: connecting to the Management service api.netbird.io:443
2024-04-01T19:32:46+03:00 DEBG client/internal/connect.go:165: connected to the Management service api.netbird.io:443
2024-04-01T19:32:47+03:00 DEBG signal/client/grpc.go:92: connected to Signal Service: signal.netbird.io:443
2024-04-01T19:32:47+03:00 DEBG client/internal/wgproxy/proxy_ebpf.go:37: instantiate ebpf proxy
2024-04-01T19:32:47+03:00 DEBG client/internal/ebpf/ebpf/wg_proxy_linux.go:11: load ebpf WG proxy
2024-04-01T19:32:47+03:00 INFO client/internal/wgproxy/proxy_ebpf.go:80: local wg proxy listening on: 3128

No sign of any malfunction, as you can see. Any ideas

To Reproduce

Simply start the netbird service and notice that the local peer is not connected, both according to the GUI app and to the admin page at https://app.netbird.io/peers (which shows another peer as being online).

Expected behavior

To get connected to other peers.

Are you using NetBird Cloud?

Yes..

NetBird version

See below.

NetBird status -d output (redacted):

# netbird status -d
Peers detail:
Daemon version: 0.26.7
CLI version: 0.26.7
Management: Connected to https://api.netbird.io:443
Signal: Connected to https://signal.netbird.io:443
Relays:
Nameservers:
FQDN: {xxxx}.netbird.cloud
NetBird IP: 100.67.{xx}.{xx}/16
Interface type: Kernel
Quantum resistance: false
Routes: -
Peers count: 0/0 Connected
Originally created by @acarstoiu on GitHub (Apr 2, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1787 **Describe the problem** I'm using the free **cloud** plan of Netbird since before there were any paid plans and the serice was in its early days. Never had any connection problems with the other peers, in spite of the fact that there's no package for my distribution, [Gentoo](https://www.gentoo.org/). But after upgrading from _0.25.3_ to _0.26.7_ my peer is unable to connect to other peers. Initially the service complained in its log file about being unable to instantiate an "eBPF proxy" using the kernel or some user space replacement. I've read [this article](https://netbird.io/knowledge-hub/using-xdp-ebpf-to-share-default-dns-port-between-resolvers) and configured my kernel according to the needs, which made the log file look like this (log level set to `trace`): ``` 2024-04-01T19:32:45+03:00 INFO client/cmd/service_controller.go:24: starting Netbird service 2024-04-01T19:32:45+03:00 TRAC client/server/server.go:184: running client connection 2024-04-01T19:32:45+03:00 INFO client/cmd/service_controller.go:64: started daemon server: /var/run/netbird.sock 2024-04-01T19:32:45+03:00 INFO client/internal/connect.go:96: starting NetBird client version 0.26.7 2024-04-01T19:32:45+03:00 DEBG client/internal/connect.go:157: connecting to the Management service api.netbird.io:443 2024-04-01T19:32:46+03:00 DEBG client/internal/connect.go:165: connected to the Management service api.netbird.io:443 2024-04-01T19:32:47+03:00 DEBG signal/client/grpc.go:92: connected to Signal Service: signal.netbird.io:443 2024-04-01T19:32:47+03:00 DEBG client/internal/wgproxy/proxy_ebpf.go:37: instantiate ebpf proxy 2024-04-01T19:32:47+03:00 DEBG client/internal/ebpf/ebpf/wg_proxy_linux.go:11: load ebpf WG proxy 2024-04-01T19:32:47+03:00 INFO client/internal/wgproxy/proxy_ebpf.go:80: local wg proxy listening on: 3128 ``` No sign of any malfunction, as you can see. Any ideas ❓ **To Reproduce** Simply start the _netbird_ service and notice that the local peer is **not** connected, both according to the GUI app and to the admin page at https://app.netbird.io/peers (which shows another peer as being online). **Expected behavior** To get connected to other peers. **Are you using NetBird Cloud?** Yes.. **NetBird version** See below. **NetBird status -d output (redacted):** ``` # netbird status -d Peers detail: Daemon version: 0.26.7 CLI version: 0.26.7 Management: Connected to https://api.netbird.io:443 Signal: Connected to https://signal.netbird.io:443 Relays: Nameservers: FQDN: {xxxx}.netbird.cloud NetBird IP: 100.67.{xx}.{xx}/16 Interface type: Kernel Quantum resistance: false Routes: - Peers count: 0/0 Connected ```
saavagebueno added the clientcloud labels 2026-08-05 00:51:08 -04:00
Sign in to join this conversation.
No Label client cloud
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#3194