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

Random network disruptions on 0.33.0 #1457

New Issue
Closed
opened 2025-11-20 05:30:57 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:30:57 -05:00
Owner
Copy Link

Originally created by @christian-schlichtherle on GitHub (Nov 25, 2024).

After upgrading from version 0.32.0 to 0.33.0, we see random network disruptions although netbird status is reporting no disconnects. This issue happens several times per hour even if the nodes sit on the same LAN. Eventually, we've downgraded to 0.32.0.

To reproduce: Install a larger bunch of Linux nodes on the same LAN, put some serious workload on them and watch random network errors without being reported by netbird status. In our case, we run Longhorn on the nodes and everytime this happens almost all of the volumes degrade, causing huge network activity in order to rebuild new volume replicas on other nodes.

Originally created by @christian-schlichtherle on GitHub (Nov 25, 2024). After upgrading from version 0.32.0 to 0.33.0, we see random network disruptions although `netbird status` is reporting no disconnects. This issue happens several times per hour even if the nodes sit on the same LAN. Eventually, we've downgraded to 0.32.0. To reproduce: Install a larger bunch of Linux nodes on the same LAN, put some serious workload on them and watch random network errors without being reported by `netbird status`. In our case, we run Longhorn on the nodes and everytime this happens almost all of the volumes degrade, causing huge network activity in order to rebuild new volume replicas on other nodes.
saavagebueno added the clientwaiting-feedbacktriage-needed labels 2025-11-20 05:30:57 -05:00
saavagebueno commented 2025-11-20 05:30:57 -05:00
Author
Owner
Copy Link

@mgarces commented on GitHub (Nov 26, 2024):

Hi, can you please clarify if this is on self-hosted or cloud?
Also, would it be possible to run some tests with 0.33.0 and collect logs with debug mode activated? [1] It would be helpful to understand the status of your nodes.

[1] https://docs.netbird.io/how-to/troubleshooting-client

@mgarces commented on GitHub (Nov 26, 2024): Hi, can you please clarify if this is on self-hosted or cloud? Also, would it be possible to run some tests with `0.33.0` and collect logs with debug mode activated? [[1](https://docs.netbird.io/how-to/troubleshooting-client)] It would be helpful to understand the status of your nodes. [1] https://docs.netbird.io/how-to/troubleshooting-client
saavagebueno commented 2025-11-20 05:30:58 -05:00
Author
Owner
Copy Link

@christian-schlichtherle commented on GitHub (Dec 3, 2024):

This was the cloud service.

I'm sorry to tell you that the recent issues with regressions in Netbird and incompatibilities with Flannel have caused us to reengineer out network design: We have now settled on Netmaker for the overlay network and Cilium for the CNI plugin.

In all fairness, Netbird isn't to blame entirely for our struggles: It seems more like a compatibility issue with Flannel that caused frequent outages of the clusters every few hours. Nevertheless, there were definitely regressions in Netbird too, I've created tickets before. As the situation became unbearable, I had to look for a change. I hope you can solve the regression issues because this is a really impressive project.

@christian-schlichtherle commented on GitHub (Dec 3, 2024): This was the cloud service. I'm sorry to tell you that the recent issues with regressions in Netbird and incompatibilities with Flannel have caused us to reengineer out network design: We have now settled on Netmaker for the overlay network and Cilium for the CNI plugin. In all fairness, Netbird isn't to blame entirely for our struggles: It seems more like a compatibility issue with Flannel that caused frequent outages of the clusters every few hours. Nevertheless, there were definitely regressions in Netbird too, I've created tickets before. As the situation became unbearable, I had to look for a change. I hope you can solve the regression issues because this is a really impressive project.
saavagebueno commented 2025-11-20 05:30:58 -05:00
Author
Owner
Copy Link

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

Hello @christian-schlichtherle,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

@nazarewk commented on GitHub (Apr 28, 2025): Hello @christian-schlichtherle, We're currently reviewing our open issues and would like to verify if this problem still exists in the [latest NetBird version](https://github.com/netbirdio/netbird/releases). Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within **2 weeks**, but feel free to reopen it with updated information. Thanks for your contribution to improving the project!
saavagebueno commented 2025-11-20 05:30:58 -05:00
Author
Owner
Copy Link

@christian-schlichtherle commented on GitHub (Apr 28, 2025):

As stated above, we have abandoned Netbird for Netmaker.

@christian-schlichtherle commented on GitHub (Apr 28, 2025): As stated above, we have abandoned Netbird for Netmaker.
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 client triage-needed waiting-feedback
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#1457
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?