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

Decide on max elapsed time when not able to reach management or signal whether #77

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

Originally created by @braginini on GitHub (Nov 3, 2021).

Right now Management and Signal connections are retried in case there are some issues.
E.g. Signal or Management server is not available.

While the connection to Management and Signal is crucial for receiving system updates and negotiating new connections, peer-to-peer connections to other peers can still be open and fully functioning.

Retrying lasts for 30 min and afterward, the error is propagated higher, canceling the whole client operation (including healthy peer-to-peer connections) and starting the retry mechanism on the whole client app.

While Signal and Management won't be unavailable for so long (30 min+) do we want to give it a little bit more time for the clients to retry before canceling the whole operation?

E.g. 6,12,24 hours?

Originally created by @braginini on GitHub (Nov 3, 2021). Right now Management and Signal connections are retried in case there are some issues. E.g. Signal or Management server is not available. While the connection to Management and Signal is crucial for receiving system updates and negotiating new connections, peer-to-peer connections to other peers can still be open and fully functioning. Retrying lasts for 30 min and afterward, the error is propagated higher, canceling the whole client operation (including healthy peer-to-peer connections) and starting the retry mechanism on the whole client app. While Signal and Management won't be unavailable for so long (30 min+) do we want to give it a little bit more time for the clients to retry before canceling the whole operation? E.g. 6,12,24 hours?
saavagebueno added the client label 2025-11-20 05:05:51 -05:00
saavagebueno commented 2025-11-20 05:05:52 -05:00
Author
Owner
Copy Link

@braginini commented on GitHub (Nov 4, 2021):

Additionally, when the network is unavailable on a machine, peers are constantly keeping retrying the connection to each other and fail on signaling.
Think of a mechanism to prevent such unnecessary retries.

@braginini commented on GitHub (Nov 4, 2021): Additionally, when the network is unavailable on a machine, peers are constantly keeping retrying the connection to each other and fail on signaling. Think of a mechanism to prevent such unnecessary retries.
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
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#77
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?