[GH-ISSUE #3427] Recommendations for 4G connected peers / data usage on metered networks #7315

New Issue

saavagebueno · 2026-08-05T01:12:26-04:00

saavagebueno commented

2026-08-05 01:12:26 -04:00

Originally created by @rgdev on GitHub (Mar 3, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3427

Originally assigned to: @nazarewk on GitHub.

Hello,

We've deployed Netbird (0.37.1) on a few 4G connected devices as a possible replacement for an older OpenVPN-based solution.

Right off the bat we've noticed a significant increase in data usage we can attribute to obvious things such as the different mesh network architecture, control plane communications and additional features (updates of routes & peers; key exchange; signal relay functionality etc). While OpenVPN typically use a megabyte a day, Netbird will use around 20 MBs.

Our use case is exclusively to enable remote access into those devices so 99% of the time the VPN link doesn't not carry much data (nearly all outgoing traffic goes through the ISP's network, not Netbird or OpenVPN).

We've implemented some generous read, write and idle timeouts on the infra side (Self Hosted Netbird) to ensure Netbird clients don't produce excessive reconnects. We've also tried setting NB_FORCED_RELAY=true (I don't think this is documented yet?) since we rely on Netbird Relay servers to carry the connections as direct P2P connections are difficult on mobile networks.

Do you have tips or recommendations for running Netbird on metered networks to keep the data usage as low as possible ?

Thanks.

Originally created by @rgdev on GitHub (Mar 3, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3427 Originally assigned to: @nazarewk on GitHub. Hello, We've deployed Netbird (0.37.1) on a few 4G connected devices as a possible replacement for an older OpenVPN-based solution. Right off the bat we've noticed a significant increase in data usage we can attribute to obvious things such as the different mesh network architecture, control plane communications and additional features (updates of routes & peers; key exchange; signal relay functionality etc). While OpenVPN typically use a megabyte a day, Netbird will use around 20 MBs. Our use case is exclusively to enable remote access into those devices so 99% of the time the VPN link doesn't not carry much data (nearly all outgoing traffic goes through the ISP's network, not Netbird or OpenVPN). We've implemented some generous read, write and idle timeouts on the infra side (Self Hosted Netbird) to ensure Netbird clients don't produce excessive reconnects. We've also tried setting NB_FORCED_RELAY=true (I don't think this is documented yet?) since we rely on Netbird Relay servers to carry the connections as direct P2P connections are difficult on mobile networks. Do you have tips or recommendations for running Netbird on metered networks to keep the data usage as low as possible ? Thanks.

saavagebueno added the mobile data-usage labels 2026-08-05 01:12:26 -04:00

saavagebueno closed this issue

2026-08-05 01:12:26 -04:00

saavagebueno commented

2026-08-05 01:12:27 -04:00

@1nerdyguy commented on GitHub (Mar 3, 2025):

I'm curious as to the answers you end up with here, so following for that.

However, I do feel you may be running into a scope issue. to 99.9% of the target audience for netbird, 20 MB a day is literally nothing. While I get that's not your case here, you can see why extreme bandwidth limitations aren't so much on the roadmap at this time?

@1nerdyguy commented on GitHub (Mar 3, 2025): I'm curious as to the answers you end up with here, so following for that. However, I do feel you may be running into a scope issue. to 99.9% of the target audience for netbird, 20 MB a day is literally nothing. While I get that's not your case here, you can see why extreme bandwidth limitations aren't so much on the roadmap at this time?

saavagebueno commented

2026-08-05 01:12:27 -04:00

@micael-pn commented on GitHub (Mar 5, 2025):

Hello,

I am also interested in this use case.

We manage thousands of IoT devices connected via 3G and 4G/LTE networks, where bandwidth and data usage are limited.

Currently, we use OpenVPN for remote maintenance access, but we are evaluating Netbird as a potential replacement. Since cellular data is billed per MB, minimizing data consumption is a key factor in our decision.

Compared to OpenVPN, how does Netbird handle data usage? Are there specific configurations to optimize and reduce cellular consumption as much as possible (both on client and server side)?

Thanks in advance for your insights!

@micael-pn commented on GitHub (Mar 5, 2025): Hello, I am also interested in this use case. We manage thousands of IoT devices connected via 3G and 4G/LTE networks, where bandwidth and data usage are limited. Currently, we use OpenVPN for remote maintenance access, but we are evaluating Netbird as a potential replacement. Since cellular data is billed per MB, minimizing data consumption is a key factor in our decision. Compared to OpenVPN, how does Netbird handle data usage? Are there specific configurations to optimize and reduce cellular consumption as much as possible (both on client and server side)? Thanks in advance for your insights!

saavagebueno commented

2026-08-05 01:12:27 -04:00

@ohmer1 commented on GitHub (Mar 10, 2025):

I'm curious as to the answers you end up with here, so following for that.

However, I do feel you may be running into a scope issue. to 99.9% of the target audience for netbird, 20 MB a day is literally nothing. While I get that's not your case here, you can see why extreme bandwidth limitations aren't so much on the roadmap at this time?

If the client is really using 20MB/day by itself, this mean 600MB/month. IMO, this is huge for a mobile device with limited 3G/LTE quota.

@ohmer1 commented on GitHub (Mar 10, 2025): > I'm curious as to the answers you end up with here, so following for that. > > However, I do feel you may be running into a scope issue. to 99.9% of the target audience for netbird, 20 MB a day is literally nothing. While I get that's not your case here, you can see why extreme bandwidth limitations aren't so much on the roadmap at this time? If the client is really using 20MB/day by itself, this mean 600MB/month. IMO, this is huge for a mobile device with limited 3G/LTE quota.

saavagebueno commented

2026-08-05 01:12:27 -04:00

@1nerdyguy commented on GitHub (Mar 10, 2025):

I'm curious as to the answers you end up with here, so following for that.
However, I do feel you may be running into a scope issue. to 99.9% of the target audience for netbird, 20 MB a day is literally nothing. While I get that's not your case here, you can see why extreme bandwidth limitations aren't so much on the roadmap at this time?

If the client is really using 20MB/day by itself, this mean 600MB/month. IMO, this is huge for a mobile device with limited 3G/LTE quota.

Agreed, however I am stating again that those who are on mobiles with limited 3g/LTE quotas represent a fraction of the users for Netbird. Not that the concern isn't valid, it's just a priority thing.

@1nerdyguy commented on GitHub (Mar 10, 2025): > > I'm curious as to the answers you end up with here, so following for that. > > However, I do feel you may be running into a scope issue. to 99.9% of the target audience for netbird, 20 MB a day is literally nothing. While I get that's not your case here, you can see why extreme bandwidth limitations aren't so much on the roadmap at this time? > > If the client is really using 20MB/day by itself, this mean 600MB/month. IMO, this is huge for a mobile device with limited 3G/LTE quota. Agreed, however I am stating again that those who are on mobiles with limited 3g/LTE quotas represent a fraction of the users for Netbird. Not that the concern isn't valid, it's just a priority thing.

saavagebueno commented

2026-08-05 01:12:27 -04:00

@nazarewk commented on GitHub (Mar 11, 2025):

I will be picking up this topic and trying to provide you with more details as the IoT/data constrained use cases seem to pop up here and there.

For now I established that:

High data usage can occur in cases where there are a lot of offline peers in the network due to connection retries,
Every P2P connection is expected to consume ~140 bytes initially and ~90 bytes every few seconds for liveness checks (backing UDP in itself has no concept of connection being alive, so data needs to be sent back and forth to confirm)

I will ask the developers about what can be done to reduce the data usage and get back to you with more details.

@nazarewk commented on GitHub (Mar 11, 2025): I will be picking up this topic and trying to provide you with more details as the IoT/data constrained use cases seem to pop up here and there. For now I established that: 1. High data usage can occur in cases where there are a lot of *offline* peers in the network due to connection retries, 2. Every P2P connection is expected to consume ~140 bytes initially and ~90 bytes every few seconds for liveness checks (backing UDP in itself has no concept of connection being alive, so data needs to be sent back and forth to confirm) I will ask the developers about what can be done to reduce the data usage and get back to you with more details.

saavagebueno commented

2026-08-05 01:12:28 -04:00

@Yxnt commented on GitHub (Mar 12, 2025):

I will be picking up this topic and trying to provide you with more details as the IoT/data constrained use cases seem to pop up here and there.

For now I established that:

High data usage can occur in cases where there are a lot of offline peers in the network due to connection retries,

Every P2P connection is expected to consume ~140 bytes initially and ~90 bytes every few seconds for liveness checks (backing UDP in itself has no concept of connection being alive, so data needs to be sent back and forth to confirm)

I will ask the developers about what can be done to reduce the data usage and get back to you with more details.

@nazarewk Many thx, Although the primary user scenario for Netbird is currently on the PC/Server side, I am presently working at a robotics company. Over the past few years, we have been experimenting with various SDN software (ZeroTier, Tailscale, Nebula) to manage the private networks of our devices. The solution we are currently using is Nebula, but it requires us to manually manage certificates. As a result, I’ve been attempting to integrate our thousands of devices into Netbird. Three months ago, we connected 400 devices to Netbird for the first time and found that the bandwidth of the server hosting Netbird’s Signal and Coturn components was fully saturated. This server, which has only 10M bandwidth, remained under full load for an extended period. At the same time, we observed that the 4G data usage on the robot side exceeded 3GB that day (with each of the 400 robots consuming over 3GB). In an IoT scenario, the cost of 4G network data is quite high. Consequently, we abandoned this approach and continued using Nebula to ensure functionality without incurring additional data costs. However, we kept around four robotic devices running Netbird. Yesterday, after analyzing the data, I discovered that over the past two weeks, the total data usage for some devices reached 13GB. At that point, our Netbird server had a total of 103 devices connected, with 30 to 40 devices active during the day and possibly only about 10 devices active 24/7.

@Yxnt commented on GitHub (Mar 12, 2025): > I will be picking up this topic and trying to provide you with more details as the IoT/data constrained use cases seem to pop up here and there. > > For now I established that: > > 1. High data usage can occur in cases where there are a lot of _offline_ peers in the network due to connection retries, > 2. Every P2P connection is expected to consume ~140 bytes initially and ~90 bytes every few seconds for liveness checks (backing UDP in itself has no concept of connection being alive, so data needs to be sent back and forth to confirm) > > I will ask the developers about what can be done to reduce the data usage and get back to you with more details. @nazarewk Many thx, Although the primary user scenario for Netbird is currently on the PC/Server side, I am presently working at a robotics company. Over the past few years, we have been experimenting with various SDN software (ZeroTier, Tailscale, Nebula) to manage the private networks of our devices. The solution we are currently using is Nebula, but it requires us to manually manage certificates. As a result, I’ve been attempting to integrate our thousands of devices into Netbird. Three months ago, we connected 400 devices to Netbird for the first time and found that the bandwidth of the server hosting Netbird’s Signal and Coturn components was fully saturated. This server, which has only 10M bandwidth, remained under full load for an extended period. At the same time, we observed that the 4G data usage on the robot side exceeded 3GB that day (with each of the 400 robots consuming over 3GB). In an IoT scenario, the cost of 4G network data is quite high. Consequently, we abandoned this approach and continued using Nebula to ensure functionality without incurring additional data costs. However, we kept around four robotic devices running Netbird. Yesterday, after analyzing the data, I discovered that over the past two weeks, the total data usage for some devices reached 13GB. At that point, our Netbird server had a total of 103 devices connected, with 30 to 40 devices active during the day and possibly only about 10 devices active 24/7.

saavagebueno commented

2026-08-05 01:12:28 -04:00

@nazarewk commented on GitHub (Mar 17, 2025):

Just to let you know we are working on a "lazy connections" feature which should positively affect both data and battery usage issues.

https://github.com/netbirdio/netbird/pull/3379

@nazarewk commented on GitHub (Mar 17, 2025): Just to let you know we are working on a "lazy connections" feature which should positively affect both data and battery usage issues. https://github.com/netbirdio/netbird/pull/3379

saavagebueno commented

2026-08-05 01:12:28 -04:00

@Yxnt commented on GitHub (May 27, 2025):

Hi@nazarewk
It looks like #3379 has been merged. Can I now try updating to v0.45.0 or higher to test this feature? How much will it reduce traffic optimization?

@Yxnt commented on GitHub (May 27, 2025): Hi@nazarewk It looks like #3379 has been merged. Can I now try updating to v0.45.0 or higher to test this feature? How much will it reduce traffic optimization?

saavagebueno commented

2026-08-05 01:12:28 -04:00

@bySimpson commented on GitHub (Aug 30, 2025):

Anyone figured something out in this regard? Currently I'm facing the issue that 4 clients create roughly 90GB of egress traffic per day (traffic almost split evenly between nodes; not a metered network, however it's speed limited which causes latency issues for other clients in the same network due to low maximum upload on the connection). Lazy connections does not really seem to change anything. Network consists of 14 peers where ~4 are almost always offline. Most of the traffic goes directly to the netbird server.

@bySimpson commented on GitHub (Aug 30, 2025): ![Image](https://github.com/user-attachments/assets/87816b49-ba88-492e-882a-8fbe395d983e) Anyone figured something out in this regard? Currently I'm facing the issue that 4 clients create roughly 90GB of egress traffic per day (traffic almost split evenly between nodes; not a metered network, however it's speed limited which causes latency issues for other clients in the same network due to low maximum upload on the connection). Lazy connections does not really seem to change anything. Network consists of 14 peers where ~4 are almost always offline. Most of the traffic goes directly to the netbird server.

saavagebueno commented

2026-08-05 01:12:28 -04:00

@rgdev commented on GitHub (Sep 22, 2025):

Closing as we could not fit Netbird in our data-limited environment and went for an in-house solution instead.

Since our testing was done on a pretty old build (0.37.x) I recommend opening a new issue if the problem still occurs in more recent versions of Netbird.

@rgdev commented on GitHub (Sep 22, 2025): Closing as we could not fit Netbird in our data-limited environment and went for an in-house solution instead. Since our testing was done on a pretty old build (0.37.x) I recommend opening a new issue if the problem still occurs in more recent versions of Netbird.

saavagebueno commented

2026-08-05 01:12:28 -04:00

@ITCMD commented on GitHub (Jun 25, 2026):

Wanted to add that we seem to be hitting a similar issue. We've got IOT networks in the field and have netbird sitting idle ready for us to hop on when we need to. They don't have much for peers. Lazy connections are on. They're hitting upwards of 2 gigs a month of idle netbird usage. This results in hundreds of $ of charge. We really need to be able to put nodes in some sort of a sleep mode that can be woken from the server... ie an ultra lazy mode or something.

Otherwise, netbird is perfect and a huge upgrade from tailscale.

@ITCMD commented on GitHub (Jun 25, 2026): Wanted to add that we seem to be hitting a similar issue. We've got IOT networks in the field and have netbird sitting idle ready for us to hop on when we need to. They don't have much for peers. Lazy connections are on. They're hitting upwards of 2 gigs a month of idle netbird usage. This results in hundreds of $ of charge. We really need to be able to put nodes in some sort of a sleep mode that can be woken from the server... ie an ultra lazy mode or something. Otherwise, netbird is perfect and a huge upgrade from tailscale.

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#7315