[GH-ISSUE #3245] Pings disappear from some peers to others after one week #6670

Open
opened 2026-08-05 01:09:32 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @netandreus on GitHub (Jan 28, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3245

Originally assigned to: @pappz on GitHub.

Describe the problem

I have 2 peers:

  • "node-3" with netbird address 100.81.65.41
  • "node-2" with netbird address 100.81.94.114
    supporting HA-routes to multiple vlans.

Also I have:

  • "uk-node-1" with netboird address 100.81.73.30 and
  • ELK VM with HeartBeat and NetBird client installed with address 100.81.167.156.

My problem is that after a week these nodes (node-2 and node-3) losing connection to ELK node, and ELK node losing connection to node-2 and node-3, I can't ping them by netbird IP addresses. But in the same time I can ping other peers from ELK peer and ping other than ELK peers from node-2 and node-3.

To Reproduce

Steps to reproduce the behavior:

  1. Run two peers in HA mode.
  2. Run third peer on other location
  3. Wait for at least one week
  4. Peers connection lost

Expected behavior

Stable connection between peers.

Are you using NetBird Cloud?

No, I use self-hosted netbird.

NetBird version

0.36.3

NetBird status -dA output:

When I go by ssh to node-3 I see this:

 elk-huk-internal.netbird.selfhosted:
  NetBird IP: 100.81.167.156
  Public key: P0Xd+rb5EjqfaFXIL/KuQ0yGKHT4qTa99Mz4ABrshRA=
  Status: Connected
  -- detail --
  Connection type: Relayed
  ICE candidate (Local/Remote): -/-
  ICE candidate endpoints (Local/Remote): -/-
  Relay server address: rels://gateway.xxx.com:443
  Last connection update: 1 day, 7 hours ago <<<<<<<<<<<<<<<<<
  Last WireGuard handshake: 1 day, 7 hours ago <<<<<<<<<<<<<<<<<
  Transfer status (received/sent) 110.7 MiB/838.7 MiB
  Quantum resistance: false
  Routes: -
  Networks: -
  Latency: 129.747422ms

And same from node-2:

 elk-huk-internal.netbird.selfhosted:
  NetBird IP: 100.81.167.156
  Public key: P0Xd+rb5EjqfaFXIL/KuQ0yGKHT4qTa99Mz4ABrshRA=
  Status: Connected
  -- detail --
  Connection type: Relayed
  ICE candidate (Local/Remote): -/-
  ICE candidate endpoints (Local/Remote): -/-
  Relay server address: rels://gateway.xxx.com:443
  Last connection update: 1 day, 7 hours ago <<<<<<<<<<<<<<<<<
  Last WireGuard handshake: 1 day, 7 hours ago <<<<<<<<<<<<<<<<<
  Transfer status (received/sent) 579.3 KiB/6.3 MiB
  Quantum resistance: false
  Routes: -
  Networks: -
  Latency: 130.665153ms

Workaround

After I run:

netbird down
netbird up

WireGuard connection re-established.

Related issues

Can you please fix this?

Originally created by @netandreus on GitHub (Jan 28, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3245 Originally assigned to: @pappz on GitHub. **Describe the problem** I have 2 peers: - "node-3" with netbird address 100.81.65.41 - "node-2" with netbird address 100.81.94.114 supporting HA-routes to multiple vlans. Also I have: - "uk-node-1" with netboird address 100.81.73.30 and - ELK VM with HeartBeat and NetBird client installed with address 100.81.167.156. My problem is that after a week these nodes (node-2 and node-3) losing connection to ELK node, and ELK node losing connection to node-2 and node-3, I can't ping them by netbird IP addresses. But in the same time I can ping other peers from ELK peer and ping other than ELK peers from node-2 and node-3. **To Reproduce** Steps to reproduce the behavior: 1. Run two peers in HA mode. 2. Run third peer on other location 3. Wait for at least one week 4. Peers connection lost **Expected behavior** Stable connection between peers. **Are you using NetBird Cloud?** No, I use self-hosted netbird. **NetBird version** 0.36.3 **NetBird status -dA output:** When I go by ssh to node-3 I see this: ``` elk-huk-internal.netbird.selfhosted: NetBird IP: 100.81.167.156 Public key: P0Xd+rb5EjqfaFXIL/KuQ0yGKHT4qTa99Mz4ABrshRA= Status: Connected -- detail -- Connection type: Relayed ICE candidate (Local/Remote): -/- ICE candidate endpoints (Local/Remote): -/- Relay server address: rels://gateway.xxx.com:443 Last connection update: 1 day, 7 hours ago <<<<<<<<<<<<<<<<< Last WireGuard handshake: 1 day, 7 hours ago <<<<<<<<<<<<<<<<< Transfer status (received/sent) 110.7 MiB/838.7 MiB Quantum resistance: false Routes: - Networks: - Latency: 129.747422ms ``` And same from node-2: ``` elk-huk-internal.netbird.selfhosted: NetBird IP: 100.81.167.156 Public key: P0Xd+rb5EjqfaFXIL/KuQ0yGKHT4qTa99Mz4ABrshRA= Status: Connected -- detail -- Connection type: Relayed ICE candidate (Local/Remote): -/- ICE candidate endpoints (Local/Remote): -/- Relay server address: rels://gateway.xxx.com:443 Last connection update: 1 day, 7 hours ago <<<<<<<<<<<<<<<<< Last WireGuard handshake: 1 day, 7 hours ago <<<<<<<<<<<<<<<<< Transfer status (received/sent) 579.3 KiB/6.3 MiB Quantum resistance: false Routes: - Networks: - Latency: 130.665153ms ``` **Workaround** After I run: ``` netbird down netbird up ``` WireGuard connection re-established. **Related issues** - [Peer link is being dropped](https://github.com/netbirdio/netbird/issues/3121#top) Can you please fix this?
saavagebueno added the clientrelay labels 2026-08-05 01:09:32 -04:00
Sign in to join this conversation.
No Label client relay
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#6670