[GH-ISSUE #6953] Client grows to 6 GB RSS and spins ~60% of a core while Management is unreachable (0.73.2, linux/arm64) #12286

New Issue

saavagebueno · 2026-08-05T01:32:47-04:00

saavagebueno commented

2026-08-05 01:32:47 -04:00

Originally created by @howdude230 on GitHub (Jul 29, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/6953

Summary

On a self-hosted deployment, netbird up --foreground-mode grew to 6.0 GB RSS
and consumed 52 hours of CPU time over 87 hours of wall time (~60% of one
core, sustained) while it was unable to reach the Management service.

The client did not exit, back off to a steady state, or cap its retry cost. It
kept allocating until the host ran out of memory and the kernel/init OOM killer
began terminating unrelated workloads on the same machine.

The memory is released immediately and completely on restart: a freshly started
client on the same host with the same (still failing) Management endpoint sits at
125 MB RSS with 12 s of CPU time. So the growth tracks time-spent-failing,
not configuration or workload.

Environment


NetBird client	0.73.2, installed as an OS extension/container
Management server	self-hosted (version not independently verified at runtime; source pin records 0.71.x)
OS	Talos Linux v1.13.6, Go 1.26.5
Arch	linux/arm64
Host	2 vCPU / 11.9 GB RAM
Peers in account	12
Client invocation	`netbird up --foreground-mode`

Impact

The client and the Management service it depends on were on the same host. That
made the failure self-sustaining:

Management becomes unreachable.
Client retries; RSS and CPU climb without bound.
Host exhausts memory; the OOM killer starts killing the lowest-priority
cgroups.
Among the victims is the reverse proxy that serves the Management
endpoint.
Management is now definitively unreachable → back to step 2, permanently.

Once tipped, this could not self-heal. It ran for over an hour and only
recovered by manually restarting the NetBird client, which released 5.6 GB
instantly and let everything else recover.

This co-location is a deployment choice, not a NetBird bug, and we are not
asking you to fix it. It is included only because it explains why unbounded
retry cost escalated into a total outage rather than a degraded tunnel. On a
host where NetBird is not co-located with its own dependencies, the same
behaviour would still eventually OOM the host — it would just take longer to
matter.

Evidence

Process table at peak (host had 11904 MB total, 800 MB available):

PID     THREADS  CPU-TIME    VIRT    RES     COMMAND
15848   12       188030.32   7.3 GB  6.0 GB  /usr/local/bin/netbird up --foreground-mode

Wall clock for that PID: 87 h 25 m
CPU time: 188,030 s = 52.2 h → ~60% of one core, sustained, for days

After a plain restart, same host, Management still unreachable:

PID     THREADS  CPU-TIME  VIRT    RES     COMMAND
195115  10       12.35     1.4 GB  125 MB  /usr/local/bin/netbird up --foreground-mode

Log signature

Two patterns dominate the log while Management is down.

1. gRPC channel counter climbing. Each reconnect attempt appears to create a
new channel rather than reusing one — note Channel #31 SubChannel #32:

WARNING: [core] [Channel #31 SubChannel #32] grpc: addrConn.createTransport
  failed to connect to {Addr: "mgmt.example.net:443", ServerName: "mgmt.example.net:443", }.
  Err: connection error: desc = "transport: Error while dialing:
  nbnet.NewDialer().DialContext: dial tcp 203.0.113.10:443: i/o timeout"

2. High-rate writes to closed UDP sockets. These arrive in bursts, many
within the same millisecond, referencing peer sockets that are already gone:

level=ERROR msg="Failed to send" pid="<REDACTED-PEER-KEY>"
  error="write udp [::]:48535-><PEER-MESH-IP>:59693: use of closed network connection"
level=ERROR msg="Failed to send" pid="<REDACTED-PEER-KEY>"
  error="write udp [::]:48535-><PEER-MESH-IP>:59693: use of closed network connection"
level=ERROR msg="Failed to send" pid="<REDACTED-PEER-KEY>"
  error="write udp [::]:48535-><PEER-MESH-IP>:59693: use of closed network connection"
  ... (repeating at high frequency, same source port, same destination)

The repeated use of closed network connection against a stable source port
(48535) suggests send paths for dead peer connections are retained and kept
being driven rather than torn down.

3. Login failure loop. In --foreground-mode the process exits on login
failure and is restarted by the supervisor:

ERRO client/grpc.go:121: failed creating connection to Management Service:
  create connection: dial context: context deadline exceeded
ERRO auth/auth.go:51: failed connecting to Management Service https://mgmt.example.net:443:
  create connection: dial context: context deadline exceeded
Error: foreground login failed: failed to create auth client: create connection:
  dial context: context deadline exceeded

Note this exit-and-restart path is what keeps memory low now. The 6 GB process
was a long-lived one that had already authenticated and then lost Management,
so it stayed resident and retried in-process instead of exiting.

What we did not capture

Being straightforward about the limits of this report:

No pprof heap or goroutine dump was taken. The incident was live, the
host was minutes from full exhaustion, and the process was restarted to
restore service. That evidence is gone.
We therefore cannot point at a specific allocation site, and we are not
claiming a diagnosed root cause in your code. What is established is the
observable behaviour: unbounded RSS + CPU growth strictly correlated with
time-spent-unable-to-reach-Management, fully reset by restart.
Management-side logs for the same window were not preserved.

If it would help, we can attempt a controlled reproduction (below) with
pprof enabled and attach real profiles.

Suggested reproduction

Bring up a client with netbird up --foreground-mode against a reachable
self-hosted Management, with a non-trivial peer count (ours: 12).
Let it fully connect and establish peer sessions.
Make Management unreachable in a way that blackholes rather than
refuses — drop traffic to the Management address so dials hit
i/o timeout, not connection refused. (In our case the TCP path timed
out; that distinction may matter for which retry path is taken.)
Leave it. Sample RSS and CPU time hourly.

We observed growth over days rather than minutes, so this likely needs to run
for hours to be visible.

What we would expect

Retry cost bounded — reconnect attempts reuse a channel, or old channels are
closed and collected.
Send paths for peers that are no longer reachable are torn down rather than
driven at high frequency against closed sockets.
Idle-but-disconnected steady state that does not grow without bound, so an
unreachable Management degrades the tunnel instead of eventually taking down
the host.

Workaround for other operators

Restarting the client immediately releases all of it. If you run the client on
a host alongside anything you care about, constrain it — a memory limit on the
NetBird service turns "host dies" into "NetBird restarts", which is strictly
better and is self-correcting.

Identifiers in this report are anonymized: hostnames, public and mesh IP
addresses, and peer public keys have been replaced with placeholders. Version
numbers, byte counts, CPU times, thread counts, port numbers and log structure
are verbatim.

Originally created by @howdude230 on GitHub (Jul 29, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/6953 ## Summary On a self-hosted deployment, `netbird up --foreground-mode` grew to **6.0 GB RSS** and consumed **52 hours of CPU time over 87 hours of wall time** (~60% of one core, sustained) while it was unable to reach the Management service. The client did not exit, back off to a steady state, or cap its retry cost. It kept allocating until the host ran out of memory and the kernel/init OOM killer began terminating unrelated workloads on the same machine. The memory is released immediately and completely on restart: a freshly started client on the same host with the same (still failing) Management endpoint sits at **125 MB RSS** with **12 s** of CPU time. So the growth tracks time-spent-failing, not configuration or workload. ## Environment | | | |---|---| | NetBird client | **0.73.2**, installed as an OS extension/container | | Management server | self-hosted (version not independently verified at runtime; source pin records 0.71.x) | | OS | Talos Linux v1.13.6, Go 1.26.5 | | Arch | **linux/arm64** | | Host | 2 vCPU / 11.9 GB RAM | | Peers in account | 12 | | Client invocation | `netbird up --foreground-mode` | ## Impact The client and the Management service it depends on were on the same host. That made the failure self-sustaining: 1. Management becomes unreachable. 2. Client retries; RSS and CPU climb without bound. 3. Host exhausts memory; the OOM killer starts killing the lowest-priority cgroups. 4. Among the victims is the reverse proxy that **serves the Management endpoint**. 5. Management is now definitively unreachable → back to step 2, permanently. Once tipped, this could not self-heal. It ran for over an hour and only recovered by manually restarting the NetBird client, which released 5.6 GB instantly and let everything else recover. This co-location is a deployment choice, not a NetBird bug, and we are not asking you to fix it. It is included only because it explains why unbounded retry cost escalated into a total outage rather than a degraded tunnel. On a host where NetBird is *not* co-located with its own dependencies, the same behaviour would still eventually OOM the host — it would just take longer to matter. ## Evidence Process table at peak (host had 11904 MB total, 800 MB available): ``` PID THREADS CPU-TIME VIRT RES COMMAND 15848 12 188030.32 7.3 GB 6.0 GB /usr/local/bin/netbird up --foreground-mode ``` - Wall clock for that PID: **87 h 25 m** - CPU time: **188,030 s = 52.2 h** → ~60% of one core, sustained, for days After a plain restart, same host, Management **still** unreachable: ``` PID THREADS CPU-TIME VIRT RES COMMAND 195115 10 12.35 1.4 GB 125 MB /usr/local/bin/netbird up --foreground-mode ``` ### Log signature Two patterns dominate the log while Management is down. **1. gRPC channel counter climbing.** Each reconnect attempt appears to create a new channel rather than reusing one — note `Channel #31 SubChannel #32`: ``` WARNING: [core] [Channel #31 SubChannel #32] grpc: addrConn.createTransport failed to connect to {Addr: "mgmt.example.net:443", ServerName: "mgmt.example.net:443", }. Err: connection error: desc = "transport: Error while dialing: nbnet.NewDialer().DialContext: dial tcp 203.0.113.10:443: i/o timeout" ``` **2. High-rate writes to closed UDP sockets.** These arrive in bursts, many within the same millisecond, referencing peer sockets that are already gone: ``` level=ERROR msg="Failed to send" pid="<REDACTED-PEER-KEY>" error="write udp [::]:48535-><PEER-MESH-IP>:59693: use of closed network connection" level=ERROR msg="Failed to send" pid="<REDACTED-PEER-KEY>" error="write udp [::]:48535-><PEER-MESH-IP>:59693: use of closed network connection" level=ERROR msg="Failed to send" pid="<REDACTED-PEER-KEY>" error="write udp [::]:48535-><PEER-MESH-IP>:59693: use of closed network connection" ... (repeating at high frequency, same source port, same destination) ``` The repeated `use of closed network connection` against a **stable source port** (`48535`) suggests send paths for dead peer connections are retained and kept being driven rather than torn down. **3. Login failure loop.** In `--foreground-mode` the process exits on login failure and is restarted by the supervisor: ``` ERRO client/grpc.go:121: failed creating connection to Management Service: create connection: dial context: context deadline exceeded ERRO auth/auth.go:51: failed connecting to Management Service https://mgmt.example.net:443: create connection: dial context: context deadline exceeded Error: foreground login failed: failed to create auth client: create connection: dial context: context deadline exceeded ``` Note this exit-and-restart path is what keeps memory low *now*. The 6 GB process was a long-lived one that had already authenticated and then lost Management, so it stayed resident and retried in-process instead of exiting. ## What we did not capture Being straightforward about the limits of this report: - **No `pprof` heap or goroutine dump was taken.** The incident was live, the host was minutes from full exhaustion, and the process was restarted to restore service. That evidence is gone. - We therefore **cannot point at a specific allocation site**, and we are not claiming a diagnosed root cause in your code. What is established is the observable behaviour: unbounded RSS + CPU growth strictly correlated with time-spent-unable-to-reach-Management, fully reset by restart. - Management-side logs for the same window were not preserved. If it would help, we can attempt a controlled reproduction (below) with `pprof` enabled and attach real profiles. ## Suggested reproduction 1. Bring up a client with `netbird up --foreground-mode` against a reachable self-hosted Management, with a non-trivial peer count (ours: 12). 2. Let it fully connect and establish peer sessions. 3. Make Management unreachable in a way that **blackholes** rather than refuses — drop traffic to the Management address so dials hit `i/o timeout`, not `connection refused`. (In our case the TCP path timed out; that distinction may matter for which retry path is taken.) 4. Leave it. Sample RSS and CPU time hourly. We observed growth over days rather than minutes, so this likely needs to run for hours to be visible. ## What we would expect - Retry cost bounded — reconnect attempts reuse a channel, or old channels are closed and collected. - Send paths for peers that are no longer reachable are torn down rather than driven at high frequency against closed sockets. - Idle-but-disconnected steady state that does not grow without bound, so an unreachable Management degrades the tunnel instead of eventually taking down the host. ## Workaround for other operators Restarting the client immediately releases all of it. If you run the client on a host alongside anything you care about, constrain it — a memory limit on the NetBird service turns "host dies" into "NetBird restarts", which is strictly better and is self-correcting. --- *Identifiers in this report are anonymized: hostnames, public and mesh IP addresses, and peer public keys have been replaced with placeholders. Version numbers, byte counts, CPU times, thread counts, port numbers and log structure are verbatim.*

saavagebueno commented

2026-08-05 01:32:47 -04:00

@linear-code[bot] commented on GitHub (Jul 29, 2026):

NET-1452

@linear-code[bot] commented on GitHub (Jul 29, 2026):  <p><a href="https://linear.app/netbird/issue/NET-1452">NET-1452</a></p>

saavagebueno commented

2026-08-05 01:32:48 -04:00

@Optic00 commented on GitHub (Jul 31, 2026):

I found and locally reproduced a concrete root-cause candidate for the unbounded CPU/RSS growth.

The exact log signature from this report:

level=ERROR msg="Failed to send" pid="..." error="write udp ... use of closed network connection"

comes from cunicu.li/go-rosenpass v0.5.42. NetBird v0.73.2 used that version, and v0.74.6, v0.76.0, and current main still use the same version.

An initiator handshake schedules a self-rescheduling retransmission timer. In v0.5.42:

handshake expiry removes the handshake from the map without stopping that timer;
initiatorHandshake.Close() stops only the expiry timer;
the surviving timer retains the handshake, peer, server, handlers, and closed UDP connection while continuing to send roughly every 10 seconds.

I reproduced this with a black-holed peer. At handshake expiry the test had recorded 8 sends; one second later it had reached 15. This behavior is covered by the existing upstream fix:

https://codeberg.org/cunicu/go-rosenpass/pulls/231

During validation I found two additional orphan paths in the same lifecycle:

a retransmission timer is created before the initial send, so an initial send failure can leave an unregistered timer behind;
a pending peer rekey timer can fire after Server.Close() and start another handshake on the closed socket.

Focused tests reproduced both cases. With go-rosenpass PR #231's timer synchronization plus fixes for those two cases, all three tests pass under the Go race detector.

This is a strong explanation for the continuing Failed to send traffic and retained memory. The increasing gRPC channel IDs probably indicate repeated NetBird engine generations, which would amplify the Rosenpass leak by repeatedly creating and closing servers. It may not explain every part of the incident by itself.

Could you confirm whether quantum resistance/Rosenpass was enabled on the affected client? The pid log field strongly suggests that it was.

The proposed contribution path is:

complete and merge the upstream go-rosenpass timer fix;
publish a new go-rosenpass tag;
submit a focused NetBird dependency-bump PR;
reproduce once more with a patched client and compare baseline versus post-blackhole heap/goroutine profiles.

Debug bundles or profiles may contain sensitive deployment information and should be shared privately with the maintainers.

@Optic00 commented on GitHub (Jul 31, 2026): I found and locally reproduced a concrete root-cause candidate for the unbounded CPU/RSS growth. The exact log signature from this report: ```text level=ERROR msg="Failed to send" pid="..." error="write udp ... use of closed network connection" ``` comes from `cunicu.li/go-rosenpass` v0.5.42. NetBird v0.73.2 used that version, and v0.74.6, v0.76.0, and current main still use the same version. An initiator handshake schedules a self-rescheduling retransmission timer. In v0.5.42: - handshake expiry removes the handshake from the map without stopping that timer; - `initiatorHandshake.Close()` stops only the expiry timer; - the surviving timer retains the handshake, peer, server, handlers, and closed UDP connection while continuing to send roughly every 10 seconds. I reproduced this with a black-holed peer. At handshake expiry the test had recorded 8 sends; one second later it had reached 15. This behavior is covered by the existing upstream fix: https://codeberg.org/cunicu/go-rosenpass/pulls/231 During validation I found two additional orphan paths in the same lifecycle: - a retransmission timer is created before the initial send, so an initial send failure can leave an unregistered timer behind; - a pending peer rekey timer can fire after `Server.Close()` and start another handshake on the closed socket. Focused tests reproduced both cases. With [go-rosenpass PR #231](https://codeberg.org/cunicu/go-rosenpass/pulls/231)'s timer synchronization plus fixes for those two cases, all three tests pass under the Go race detector. This is a strong explanation for the continuing `Failed to send` traffic and retained memory. The increasing gRPC channel IDs probably indicate repeated NetBird engine generations, which would amplify the Rosenpass leak by repeatedly creating and closing servers. It may not explain every part of the incident by itself. Could you confirm whether quantum resistance/Rosenpass was enabled on the affected client? The `pid` log field strongly suggests that it was. The proposed contribution path is: 1. complete and merge the upstream go-rosenpass timer fix; 2. publish a new go-rosenpass tag; 3. submit a focused NetBird dependency-bump PR; 4. reproduce once more with a patched client and compare baseline versus post-blackhole heap/goroutine profiles. Debug bundles or profiles may contain sensitive deployment information and should be shared privately with the maintainers.

Sign in to join this conversation.

Branches Tags

main

claude/agent-network-test-cases-p743vw

android/gui-integration

revert/component-types

feat-post_quantum_ml_kem

ice-stun-wg-demux

dependabot/npm_and_yarn/proxy/web/npm_and_yarn-b39864987c

agent-network-setup-poc

dependabot/go_modules/aws-sdk-8f849ebaed

dependabot/github_actions/actions-a940c7c866

dependabot/go_modules/otel-e34c790afd

dependabot/go_modules/testcontainers-de325c0dd6

dependabot/go_modules/wireguard-dbd6b95108

dependabot/go_modules/pion-5f703e1eca

dependabot/go_modules/gorm-2271c8195b

fix-login-needed-check

dependabot/go_modules/google.golang.org/grpc-1.82.1

fix/ui-gtk3-support

enterprise-traefik-and-migration-fixes

disambiguate_p2p_metrics

revert/component-types-hookup

embedded-vnc

feature/ios-ssh

docs/agent-network-docs-update

dependabot/go_modules/github.com/aws/aws-sdk-go-v2/service/s3-1.106.3

dependabot/go_modules/github.com/pion/stun/v3-3.1.5

fix-ssh-authorized-users-multi-rule

peer-acl-multi-source

reverse-proxy-crowdsec-appsec

reverse-proxy-allow-match-or

client-local-metrics

lazy-conn-per-peer

lazy-conn-rosenpass

dependabot/go_modules/github.com/gopacket/gopacket-1.7.0

dependabot/go_modules/goauthentik.io/api/v3-3.2026050.6

dependabot/go_modules/github.com/pires/go-proxyproto-0.15.0

dependabot/go_modules/github.com/jackc/pgx/v5-5.10.0

dependabot/go_modules/github.com/oapi-codegen/runtime-1.6.0

dependabot/go_modules/github.com/eko/gocache/lib/v4-4.2.4

dependabot/go_modules/github.com/pkg/sftp-1.13.11

dependabot/go_modules/github.com/coreos/go-oidc/v3-3.20.0

ssh-windows-privilege-check

fix/explicit-cors-handling

fix/remove-math-rand

test/gui-memory-leak-fix

fix/ui-status-dispatch

install-script-ui-dependencies

fix/grpc-get-network-map

fix/subscribe-status-coalesce

fix/tray-menu-item-leak

fix/windows-tray-race

feature/changeset

worktree-dns-route-qtype-fallthrough

mdm_integration

mlsmaycon-patch-2

feat/agent-network-ollama

proxy-tunnel-cache-ttl-env

coderabbitai/utg/1e5b0a5

grpc-acl

test/battery-drain

components-impl-drop-indexes-use-xids-no-resource-policy-map

fix/nmap-relevant-groups

e2e-guardrail-blocks-unselected-model

fix/lazyconn-cold-start-allowed-ips

vertex-guardrails-model-access-e2e

add-atomic-cache-ops

refactor/relay-foreign-cache

ci/trigger-release-tests

feature/kimi-3-agent-networks-dns-warmup

feature/dns-lazy-conn-warmup

daemon-ipc-acl

feature/ui-translation-key-parity-check

refactor/relay-foreign-cache-tests

fix/lazyconn-idle-keep-wg-peer

dmitri-propagate-auth-grant-types-on-combined

0.74.7-branch

diagnose-empty-vs-corrupt-state

windows-sleep-detector

fix/cli-up-wait-for-daemon

rp_key_persistency

feature/native-grpc

0.74.6-branch

0.74.6-branch-sync

0.74.5-branch-sync

0.74.4-branch

fix/remove-stale-peers-removal

fix/remove-stale-proxy-logic

fix/nsis-preserve-autostart-on-upgrade

refactor/peer-event-bus

dependabot/go_modules/goauthentik.io/api/v3-3.2026050.3

dependabot/go_modules/github.com/pkg/sftp-1.13.10

components-impl-drop-indexes

fix-reset-aggregation-window-flake

dependabot/go_modules/github.com/pion/dtls/v3-3.1.5

0.74.x

fix/relay-states-lock

update-process-pkg

update-gopsutil-v4

fix/relay_states_lock

increase-sysinfo-timeout

dependabot/go_modules/github.com/Azure/go-ntlmssp-0.1.1

dependabot/go_modules/github.com/eko/gocache/store/redis/v4-4.2.6

dependabot/go_modules/github.com/eko/gocache/lib/v4-4.2.3

fix/fail-to-create-upnp-port-mapping-on-opnsense-firewall

0.74.3-branch

fix/routeselector-atomic-exit-node

netmap_progressive_alignment

nmap/components-impl

dependabot/go_modules/github.com/jackc/pgx/v5-5.9.2

dependabot/go_modules/github.com/oapi-codegen/runtime-1.4.2

dependabot/go_modules/github.com/gopacket/gopacket-1.6.1

dependabot/go_modules/github.com/coreos/go-oidc/v3-3.19.0

dependabot/go_modules/github.com/pires/go-proxyproto-0.12.0

fix/signal-watchdog-sync-stop

docs/agent-network

test/affected-logic

fix/revert-ice-filter

refactor/simplify-affected-peers

pascal-filter-policies-by-direction

claude/lock-contention-peer-connect-g8t6au

dmitri-filter-policies-by-direction

refactor/migrate-profiles-to-go

profile-bindings-ios

fix/skip-restart-unchanged-route

fix/mgmt-cache-async-resolve

refactor/wails-update-105

client_lifetime_serialization_refactor

fix/browser-ssh-2

fix/ipv6-and-netstack-accept-loop

fix/browser-ssh

profile-id-name-test

refactor/mgmt-bootstrap

feat/getting-started-unified-wizard

socket-grpc-permissions

fix/mysql-index-migration

windows-dns-firewall

tests/enable-race-on-tests

ui-refactor-gtk3

feature/affected-peers-grpc

profile-id

lazyconn-first-packet-fix-v2

claude/focused-gates-VMTgb

ui-tray-linux-leftclick

fix/ctx-enrichment

daemon-owner

feature/android-client-ssh

worktree-accept-ra-forwarding

nmap/combined-deploy

task/align_protobuff_toolset

feature/session-extend

add-json-yaml-flags

refactor/ephemeral-cleanup

claude/webtransport-relay-wasm-mUjY9

claude/vnc-udp-feasibility-6KB1U

fix/wgport-config

e2e-windows-dns-combined

fix/login-cmd-root-flags

feat/reseller-openapi-spec

github-issue-resolver

add-steamos-support

fix-darwin-uninstaller

flutter-test

ci/freebsd-pkg-bootstrap

cached-serial-check-on-sync

fix-mgmt-cache-bypass-overlay

revert-easyjson-5938

revert-ice-5820

revert-firewalld-5928

refactor/permissions-manager

revert-dns-5935-systemd-resolved

revert-dns-5935-5945

revert-dns-5945-mgmt-cache

feature/log-most-busy-peers

prototype/ui-wails

coderabbitai/utg/8ae8f20

feature/use-peer-fqdn-on-https

release/0.68.3

add-slack-channel

claude/rdp-token-passthrough-eNcqW

transparent-proxy

fix/macos-stale-route-eexist

crowdsec-selfhosted

fix/remove-otel-units

entire/checkpoints/v1

fix/getting-started

feat/static-connectors-combined-server

feature/use-local-keys-embedded

feature/fleetdm

set-env-only-if-not-fork

feature/expose-has-channel

fix/connection-status-race

fix/filter-cgnat-cni-ice-candidates

feature/check-cert-locker-before-acme

test/proxy-fixes

test/proxy-mtu

prototype/ui-tauri

test/proxy-speed

fix-reused-ports

feat/migrate-to-embedded-idp

feature/add-serial-to-proxy-merged

deploy/proxy-serial

test/connection

feature/disable-legacy-port

feature/flag-to-disable-legacy-port

test/perftest

fix/http-redirect

poc-token-command

dn-reverse-proxy

prototype/reverse-proxy-rename

prototype/reverse-proxy-logs-pagination

feature/client-metrics

prototype/reverse-proxy-clusters

debug-dns-route

fix/win-dns-batch

add-extra-route-logs

job-stream-notify-disconnection-eof

deploy/secrets-manager

trigger-proxy-update

bug/update-ios-client-code-build-tags

sync-client-netmap-serial

log/conn-disconn

nmap/compaction-deploy

ci-win-test

feature/disk-encryption-check

wasm-debug

swap-dns-prio

fix/dex-config

feature/migrate-auto-groups-to-table

nmap/compaction

dex-nocgo-stub

feature/exclude-terraform-from-rate-limiting

test-freebsd

retries-refactor

coderabbitai/docstrings/b7e98ac

feat/integrate-zitadel

bug/ios-hanging-reconection

zitadel-idp

feat/network-map-serial

refactor/get-account-no-users

feat/auto-upgrade

feature/report-high-pat-id

feature/temporary-access-for-resource

fix/nmap-fwrules

dont-restart-dns

prototype/ui

update-gomobile

go-dns-for-ice

wasm-ldflags

test-ldflags

wasmbuild-test

feature/networks-s2s

vk/compare-nmaps

dbg/bothmaps

reorder-dns-shutdown

fix/relay-reconnection-race

fix/nmap-exitnodes

vk/debug/nmap-both

move-licensed-code

feat/better-daemon-connection-lost-message

feat/auto-update-2

test/timings

refactor/getaccount-raw

tests/nmap-getaccount

refactor/nmap

refactor/nmap-limit-buffer

feature/detect-mac-wakeup

feature/extract-modules

quick-setings

feat/sync-limiter

feature/store-cache-impl

fix-install-version

feature/store-metrics

feature/metrics-on-store

feature/use-gorm-cache

loadtest-signal

unsymmetrical-squash

refactor/reducate-signaling

test/update-reduce

feature/store-cache

feature/remote-debug

cli-ws-proxy-backend-addr

feat/mgmt-map-serial

snyk-fix-d9d0081a4c7f9137bdb59d0d50a141a2

snyk-fix-7415cea5a11acd66753540ca2c598c63

job-yml-update

feature/android-allow-selecting-routes

fix/up-sequence

fix/dns-hash-update

snyk-fix-967adae9863f17f108ce8948d9117b8d

log/getaccount-by-peer

signal-suppressor

dns-exit-node

feature/auto-updates

feature/cache-srv-key

merged-fixes

fix/missed-offers-and-debug

debug-and-fixes

poc-wasm-clean-backend-s2s

test/remote-debug

debug-api

fix/remove-gpo-if-empty

fix/test-freebsd

fix/mysql-setup

fix/remove-logout-btn

handle-existing-domain-user

chore/unify-domain-validation

snyk-fix-c5fafc8a50ce1f29046e25a1fc346185

feat/profile-edit-btn

snyk-fix-a54966211e18d4cf67e5a2757cc006d1

log-short-id

feat/logout-ephemeral

log-checks

batch-wg-ops

nb-interface-default

feat/aws-integration

add/race-test

feature/relay-feature-versioning

fix/systemd-service-logs

poc/preprocessed-map

add-account-onboarding

bind-ipv6

fix/merge-main

logs/peerlogs-addpeer

feature/net-297-network-migration

feature/support-skip-auto-apply-exit-node-routes

set-cmd

set-command-with-cursor

feature/limit-update-channel

stop-using-locking-share

feature/poc-lazy-detection

feature/net-248-removal-of-sync-mutex-locks

test/multiple-peer-logging

preresolve

add-ns-punnycode-support

apply-routes-early

windows-search-domains

fix/connecting-route-filter

feature/management/rest-client/impersonate

debug-local-records

resource-fields-snake-case

test/grpc-rate-limit

traffic-correlation-policy

feature/rest-client-options

feat/events-metrics

feature/buf-cli

test/add-ratelimiter

test/remove-write-lock-on-add-peer

fix/add-peer-semaphore

feature/users-roles-endpoint

mlsmaycon-patch-1

debug-user-role

chore/primary-key-on-networks

feature/update-account-peers-buffer-startup

remove-ubuntu2004-runners

refactor/permissions-no-pat-allowed

ref/logrus-factory

use-conntrack-zone

deploy/permissions-account

feature/lazy-connection-idle

ref/improve-test-cov

restore-pr-3440

test/increase-grpc-timeouts

feat/buffer-account-peers-update

test/networkmapgeneration-changes

feature/base-manager

feature/flow-receiver

chore/benchmark-with-large-runner

refactor/handshake-initiator

client/ui-update-systray-icons

userspace-router

wgwatcher-test

output-if-key-already-exists

fix/relay-reconnection

feature/port-forwarding-client-codecleaning

detached2

test/callbacks-nil-iceconninfo

refactor/optimize-peer-expiration

enable-udp-port-for-docker-template

fix/relay-update

feature/apply-posture-netmap

fix/group-update-existing-resource

conntrack-stats

upgrade-okta-sdk

multi-price

test/conn-stat

set-min-parallel-tests-for-management

dns-interceptor

debug-dns

router-dns

add-static-system-info

debug-0.29.4

debug-0.33.0

account-refactoring

relay/2800_quic

route-get-account-refactoring

test/seed-random-routes

feature/get-account-refactoring

test/reconnect-race-condition

refactor/get-account-usage

feature/add-session-id-to-update-channel

improve-ipv4conn

fix/async-pion-event-handling

debug

add-offload

feature/validate-group-association-debug

fix/limit-conn-for-sqlite

test/engine-iface

test/transaction-for-jwt-sync

fix/engine-stop-in-foreground

feature/add-mysql-support

test-migration

refactor/header-size-values

relay/eliminate-gob

test/signal-dispatcher-with-relay

relay/debug

validate-icon

feature/ipv6-support

use-pre-expanded-peers-map

feature/use-signal-dispatcher

validate/peer-status

add-read-write-times

fix/sync-peer-race

feature/relay-status

netmap

evaluate/network-map-hash

fix/lower-dns-resolve-interval-on-fail

feature/relay

fix/go-mod-version

upgrade-nftables

synology-userspace-mode

fix/use-ip-for-default-routes-on-darwin

fix/proxy_close

enable-release-workflow-on-pr

deploy/peer-performance

feature/permanent-turn

feature/permanent-turn-proxy

deploy/posture-check-sqlite

feature/optimize_sqlite_save

debug-ios-behavior

fix/delete-route-only-after-adding

tshoot/windows-logger

remove-new-routing

refactor/eliminate-repo-dependency

add-arm-to-ci

refactor-demo-account-object

test/abc2

test/abc

send-ssh-rosenpass-config-meta

refactor-demo

ensure-schedule-never-runs-non-positive

feature/peer-validator-groupmgm

feature/peer-validator-fix

fix/include-active-dashboard-users

fix/handle-canceling-schedule

fix/geo-download

debug-google-workspace

yury/resolve-ip-to-location

feature/extend-sysinfo

sqlite-async-peer-status

yury/add-postgresql-store

fix/route

test-build

posture-checks-poc

debug-keycloak-idp

poc/netstack

for-pascal-tmp

peer-logout-management

manual-peer-logout

detached

chore/refactor-management

test/dns-bind

fix/enforce-acl-for-containers

yury/use-sync-map-in-updatechannel

fix/events-key-handling

filter-cache-on-load-account

fix/user-expiration

handle-user-context-cancellation

nb-client-k8s-statefulset

fake-addr

fix/iptables_in_docker

ebpf-debug

update-getting-started-flow-use-postgres

fix/peer_list_notification

feature/device-authentication-with-client-secret

feature/keep_alive

feat-groups-from-jwt

separate_proxy_from_wgconfig

fix/wg_conn

wg_conn_fix

wg_bind_parallel_processing

fix-rollback-get-acls

proxy_cfg_cleanup

performance-improvement-rego

update-lock-log-level

feat-client-side-acl

refactor/move_grpcserver_logic_to_account_manager

feature/event-storage

feature/update-idp-redeeming-invite

feature/api-peer-info

return-groupminimum-setupkey

feature/interface-bind

documentation_enhancement

fix-peer-registration

ssh

users_cache

pass-client-caller

client_caller_type

revert-283-feat-fix-windows-installer

periodic-peer-updates

ebpf

braginini/wasm

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: DYNR/netbird#12286