[GH-ISSUE #3841] Routing peer broken from 0.40.0 onwards #7562

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

Originally created by @drewhemm on GitHub (May 19, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3841

Describe the problem

Using any version higher than 0.40.0 for a routing peer prevents access to any networks routed via that peer. The software version for 'client' peers is not a factor. I am running 0.44.0 on the client peer.

Networks are completely inaccessible by all protocols.

To Reproduce

Steps to reproduce the behavior:

  1. Create a routing peer with Netbird 0.39.2
  2. Connect via a client peer
  3. Start a ping from the client to an IP routed via the routing peer
  4. Upgrade the routing peer to 0.40.0 (or any newer version)
  5. Ping will start to time out
  6. Downgrade the routing peer to 0.39.2 (or any earlier version)
  7. Ping will resume

Expected behavior

Network connectivity should not be broken, as there are no breaking changes announced in 0.40.0

Are you using NetBird Cloud?

No, I am using self-hosted Netbird.

NetBird version

As described above, 0.39.2 is okay, 0.40.0 and newer are broken.

Is any other VPN software installed?

Yes, but not active during testing. Wireguard client. Draytek Smart VPN.

Debug output

I will attach the output of netbird status -dA and netbird debug for 1m -AS shortly.

Additional context

Have you tried these troubleshooting steps?

  • Checked for newer NetBird versions
  • Searched for similar issues on GitHub (including closed ones)
  • Restarted the NetBird client
  • Disabled other VPN software
  • Checked firewall settings
Originally created by @drewhemm on GitHub (May 19, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3841 **Describe the problem** Using any version higher than 0.40.0 for a routing peer prevents access to any networks routed via that peer. The software version for 'client' peers is not a factor. I am running 0.44.0 on the client peer. Networks are completely inaccessible by all protocols. **To Reproduce** Steps to reproduce the behavior: 1. Create a routing peer with Netbird 0.39.2 2. Connect via a client peer 3. Start a ping from the client to an IP routed via the routing peer 4. Upgrade the routing peer to 0.40.0 (or any newer version) 5. Ping will start to time out 6. Downgrade the routing peer to 0.39.2 (or any earlier version) 7. Ping will resume **Expected behavior** Network connectivity should not be broken, as there are no breaking changes announced in [0.40.0](https://github.com/netbirdio/netbird/releases/tag/v0.40.0) **Are you using NetBird Cloud?** No, I am using self-hosted Netbird. **NetBird version** As described above, [0.39.2](https://github.com/netbirdio/netbird/releases/tag/v0.39.2) is okay, [0.40.0](https://github.com/netbirdio/netbird/releases/tag/v0.40.0) and newer are broken. **Is any other VPN software installed?** Yes, but not active during testing. Wireguard client. Draytek Smart VPN. **Debug output** I will attach the output of `netbird status -dA` and `netbird debug for 1m -AS` shortly. **Additional context** **Have you tried these troubleshooting steps?** - [x] Checked for newer NetBird versions - [x] Searched for similar issues on GitHub (including closed ones) - [x] Restarted the NetBird client - [x] Disabled other VPN software - [x] Checked firewall settings
saavagebueno added the triage-needed label 2026-08-05 01:13:31 -04:00
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#7562