SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-01 03:33:13 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

[PR #771] Add grpc keep alive for management service #2868

New Issue
Open
opened 2025-11-20 08:04:14 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 08:04:14 -05:00
Owner
Copy Link

Original Pull Request: https://github.com/netbirdio/netbird/pull/771

State: closed
Merged: No

Describe your changes

Application level keep alive PoC for gRPC.

The concept is that mgmt server send the keep alive messages
periodically.
Because the current setup does not support the both way communication
the server inject keep alive (empty) messages in the Sync stream. So
the keep alive procedure will start after the Sync call happens.

The application level keep alive will be applied only on that case when the
server is behind reveres proxy. The server check it with the proper
HTTP headers to ensure to necessary this feature or not.

Because in the client has a bug what can cause exception I involved
the version information into the gRPC function calls and the server
send keep alive messages only if it is supported by the client.

Example nginx config:

server {
  listen *:80 http2;

  server_name signal.localhost;

  location / {
    grpc_set_header x-netbird-peer '$remote_addr:$remote_port';
    grpc_pass grpc://0.0.0.0:82;
  }
}

Issue ticket number and link

Checklist

  • Is it a bug fix
  • Is a typo/documentation fix
  • Is a feature enhancement
  • It is a refactor
  • Created tests that fail without the change (if possible)
  • Extended the README / documentation, if necessary
**Original Pull Request:** https://github.com/netbirdio/netbird/pull/771 **State:** closed **Merged:** No --- ## Describe your changes Application level keep alive PoC for gRPC. The concept is that mgmt server send the keep alive messages periodically. Because the current setup does not support the both way communication the server inject keep alive (empty) messages in the Sync stream. So the keep alive procedure will start after the Sync call happens. The application level keep alive will be applied only on that case when the server is behind reveres proxy. The server check it with the proper HTTP headers to ensure to necessary this feature or not. Because in the client has a bug what can cause exception I involved the version information into the gRPC function calls and the server send keep alive messages only if it is supported by the client. Example nginx config: ``` server { listen *:80 http2; server_name signal.localhost; location / { grpc_set_header x-netbird-peer '$remote_addr:$remote_port'; grpc_pass grpc://0.0.0.0:82; } } ``` ## Issue ticket number and link ### Checklist - [ ] Is it a bug fix - [ ] Is a typo/documentation fix - [x] Is a feature enhancement - [ ] It is a refactor - [ ] Created tests that fail without the change (if possible) - [ ] Extended the README / documentation, if necessary
saavagebueno added the pull-request label 2025-11-20 08:04:14 -05:00
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 pull-request
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#2868
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?