[GH-ISSUE #3852] Netbird Loses Connection to Peers #7592

New Issue

saavagebueno · 2026-08-05T01:13:39-04:00

saavagebueno commented

2026-08-05 01:13:39 -04:00

Originally created by @trbutler on GitHub (May 20, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3852

Originally assigned to: @pappz on GitHub.

Describe the problem

A Netbird peer has internet connectivity and can talk to some of its other peers, but over time the number of available peers degrades. This also seems to harm network routes. Restarting the Netbird service temporarily restores full connectivity.

I've created an Ansible playbook to ping the peers on the network. I run the test from a Linux server that is a peer on the Netbird network that has a reliable half-gig connection to the Internet. Several of the peers it tries to reach are expected to be offline at any given time, but there are others that should always be accessible (they are in quality datacenters with redundant connections).

I've tried the setup with both Network Monitoring enabled and disabled. The problem remains the same.

Here's a table of running those Ansible ping tests. For example see how things vary right after a fresh Netbird restart late last night on the peer doing the testing (Independence), a few hours later, this morning and then again after another fresh restart of Netbird moments ago:

Host	After NB Restart	Hours Later	Next Morning	Fresh NB Restart	Location
amurmaple.anon-ZDXFz.domain	✅	❌	❌	✅	Datacenter #2 (QB)
beatrice.anon-ZDXFz.domain	✅	❌	✅	✅	Studio
bigleafmaple.anon-ZDXFz.domain	❌	❌	❌	❌	Datacenter #2 (QB)
boaz.anon-ZDXFz.domain	❌	❌	❌	❌	Office
cyprus.anon-ZDXFz.domain	✅	❌	✅	✅	Datacenter #1 (CA)
falstaff.anon-ZDXFz.domain	❌	❌	❌	❌	Home
franklin.anon-ZDXFz.domain	✅	❌	✅	✅	Studio
independence.anon-ZDXFz.domain	✅	✅	✅	✅	Studio
juniper.anon-ZDXFz.domain	✅	✅	✅	✅	Datacenter #1 (CA)
madison.anon-ZDXFz.domain	✅	✅	✅	✅	Home
maple.anon-ZDXFz.domain	✅	✅	✅	❌	Datacenter #2 (QB)
mesquite.anon-ZDXFz.domain	✅	❌	❌	✅	Datacenter #1 (CA)
oberon.anon-ZDXFz.domain	✅	✅	❌	✅	Home
rahab.anon-ZDXFz.domain	❌	❌	❌	❌	Office
rosalind.anon-ZDXFz.domain	✅	✅	✅	✅	Studio
spruce.anon-ZDXFz.domain	✅	✅	❌	✅	Datacenter #1 (CA)
sugarmaple.anon-ZDXFz.domain	✅	✅	✅	✅	Datacenter #2 (QB)
thomas.anon-ZDXFz.domain	❌	❌	❌	❌	Office
touchstone.anon-ZDXFz.domain	✅	✅	✅	✅	Studio

Notably, a number of the failed peers, such as Mesquite and Amurmaple are the ones in data centers and their public connections to the Internet remain online even as they fail. Others, such as Franklin, are right next to the server (Independence) that is doing the testing -- those two are on the same switch on the same network. But not all systems on the same network fail (Touchstone is on the same network, for example) nor do all at the datacenter fail (Spruce is actually the bare metal server to which Mesquite is a container). So, I don't see a particular obvious "genre" of hosts that go down versus others that remain up.

Maple and Spruce also utilize a HA network route to access a service (192.168.5.140) which Independence, Franklin, Beatrice and Touchstone are members of the route. It intermittently becomes unavailable, but if I restart netbird on either Maple or Spruce and the four HA members, the route will begin working again.

You'll see Maple is listed as unavailable in the most recent test (coming from Independence), but if I ping it from Oberon, Maple remains available.

Note: All the "office" location systems are offline because of a power outage. Feel free to ignore those, but I wanted to include them in the table just in case such a situation might somehow "ripple" in an unexpected way. When the power is on there, they exhibit a similar situation, where Thomas will become unavailable frequently whereas Boaz remains available most of the time. But, that isn't perfectly consistent: sometimes it is Boaz that goes down and not Thomas.

To Reproduce

Steps to reproduce the behavior:

Ensure full communication with online peers. Run ping test.
Wait several hours.
Run ping test and notice servers at two distinct datacenters are no longer reachable.
Run service netbird restart on the peer doing the test and note the peers that were offline are now reachable again. (Repeat ad infinitum.)

Expected behavior

Peers remain able to talk to each other and to access high availability network routes even if one peer goes offline.

Are you using NetBird Cloud?

Self-hosted 0.44.0

NetBird version

0.44.0 on all but one peer.

Is any other VPN software installed?

No.

Debug output

20250520.log.txt

File key:
1a6ecdff51f59139b215eb9feb49b9dd88a71ef56826d1bdb2744db0448f3680/bf0674ce-c1f1-47ef-a7f1-d4c2900eebe6

Additional context

I'm not sure if this has any relation to the problems Netbird has resuming after sleep on my network's MacOS clients, see issue #2454.

Have you tried these troubleshooting steps?

[ x ] Reviewed client troubleshooting (if applicable)
[ x ] Checked for newer NetBird versions
[ x ] Searched for similar issues on GitHub (including closed ones)
[ x ] Restarted the NetBird client
[ x ] Disabled other VPN software
[ x ] Checked firewall settings

Originally created by @trbutler on GitHub (May 20, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3852 Originally assigned to: @pappz on GitHub. **Describe the problem** A Netbird peer has internet connectivity and can talk to some of its other peers, but over time the number of available peers degrades. This also seems to harm network routes. Restarting the Netbird service temporarily restores full connectivity. I've created an Ansible playbook to ping the peers on the network. I run the test from a Linux server that is a peer on the Netbird network that has a reliable half-gig connection to the Internet. Several of the peers it tries to reach are expected to be offline at any given time, but there are others that should always be accessible (they are in quality datacenters with redundant connections). I've tried the setup with both Network Monitoring enabled and disabled. The problem remains the same. Here's a table of running those Ansible ping tests. For example see how things vary right after a fresh Netbird restart late last night on the peer doing the testing (Independence), a few hours later, this morning and then again after another fresh restart of Netbird moments ago: Host | After NB Restart | Hours Later | Next Morning | Fresh NB Restart | Location | |-------------------------------|---------------|-----------------|-----------------|---------------|---------------------| | amurmaple.anon-ZDXFz.domain | ✅ | ❌ | ❌ | ✅ | Datacenter #2 (QB) | | beatrice.anon-ZDXFz.domain | ✅ | ❌ | ✅ | ✅ | Studio | | bigleafmaple.anon-ZDXFz.domain| ❌ | ❌ | ❌ | ❌ | Datacenter #2 (QB) | | boaz.anon-ZDXFz.domain | ❌ | ❌ | ❌ | ❌ | Office | | cyprus.anon-ZDXFz.domain | ✅ | ❌ | ✅ | ✅ | Datacenter #1 (CA) | | falstaff.anon-ZDXFz.domain | ❌ | ❌ | ❌ | ❌ | Home | | franklin.anon-ZDXFz.domain | ✅ | ❌ | ✅ | ✅ | Studio | | independence.anon-ZDXFz.domain| ✅ | ✅ | ✅ | ✅ | Studio | | juniper.anon-ZDXFz.domain | ✅ | ✅ | ✅ | ✅ | Datacenter #1 (CA) | | madison.anon-ZDXFz.domain | ✅ | ✅ | ✅ | ✅ | Home | | maple.anon-ZDXFz.domain | ✅ | ✅ | ✅ | ❌ | Datacenter #2 (QB) | | mesquite.anon-ZDXFz.domain | ✅ | ❌ | ❌ | ✅ | Datacenter #1 (CA) | | oberon.anon-ZDXFz.domain | ✅ | ✅ | ❌ | ✅ | Home | | rahab.anon-ZDXFz.domain | ❌ | ❌ | ❌ | ❌ | Office | | rosalind.anon-ZDXFz.domain | ✅ | ✅ | ✅ | ✅ | Studio | | spruce.anon-ZDXFz.domain | ✅ | ✅ | ❌ | ✅ | Datacenter #1 (CA) | | sugarmaple.anon-ZDXFz.domain | ✅ | ✅ | ✅ | ✅ | Datacenter #2 (QB) | | thomas.anon-ZDXFz.domain | ❌ | ❌ | ❌ | ❌ | Office | | touchstone.anon-ZDXFz.domain | ✅ | ✅ | ✅ | ✅ | Studio | Notably, a number of the failed peers, such as Mesquite and Amurmaple are the ones in data centers and their public connections to the Internet remain online even as they fail. Others, such as Franklin, are right next to the server (Independence) that is doing the testing -- those two are on the same switch on the same network. But not all systems on the same network fail (Touchstone is on the same network, for example) nor do all at the datacenter fail (Spruce is actually the bare metal server to which Mesquite is a container). So, I don't see a particular obvious "genre" of hosts that go down versus others that remain up. Maple and Spruce also utilize a HA network route to access a service (192.168.5.140) which Independence, Franklin, Beatrice and Touchstone are members of the route. It intermittently becomes unavailable, but if I restart netbird on either Maple or Spruce _and_ the four HA members, the route will begin working again. You'll see Maple is listed as unavailable in the most recent test (coming from Independence), but if I ping it from Oberon, Maple remains available. Note: All the "office" location systems are offline because of a power outage. Feel free to ignore those, but I wanted to include them in the table just in case such a situation might somehow "ripple" in an unexpected way. When the power is on there, they exhibit a similar situation, where Thomas will become unavailable frequently whereas Boaz remains available most of the time. But, that isn't perfectly consistent: sometimes it is Boaz that goes down and not Thomas. **To Reproduce** Steps to reproduce the behavior: 1. Ensure full communication with online peers. Run ping test. 2. Wait several hours. 3. Run ping test and notice servers at two distinct datacenters are no longer reachable. 4. Run `service netbird restart` on the peer doing the test and note the peers that were offline are now reachable again. (Repeat ad infinitum.) **Expected behavior** Peers remain able to talk to each other and to access high availability network routes even if one peer goes offline. **Are you using NetBird Cloud?** Self-hosted 0.44.0 **NetBird version** 0.44.0 on all but one peer. **Is any other VPN software installed?** No. **Debug output** [20250520.log.txt](https://github.com/user-attachments/files/20353443/20250520.log.txt) File key: 1a6ecdff51f59139b215eb9feb49b9dd88a71ef56826d1bdb2744db0448f3680/bf0674ce-c1f1-47ef-a7f1-d4c2900eebe6 **Additional context** I'm not sure if this has any relation to the problems Netbird has resuming after sleep on my network's MacOS clients, see issue #2454. **Have you tried these troubleshooting steps?** - [ x ] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [ x ] Checked for newer NetBird versions - [ x ] Searched for similar issues on GitHub (including closed ones) - [ x ] Restarted the NetBird client - [ x ] Disabled other VPN software - [ x ] Checked firewall settings

saavagebueno added the triage-needed label 2026-08-05 01:13:39 -04:00

saavagebueno commented

2026-08-05 01:13:39 -04:00

@netandreus commented on GitHub (May 21, 2025):

I faced with this issue many times. Here is my story:

@netandreus commented on GitHub (May 21, 2025): I faced with this issue many times. Here is my story: - [Can't connect to service by netbird address #3821](https://github.com/netbirdio/netbird/issues/3821) - [Can't ping connected peer #3637](https://github.com/netbirdio/netbird/issues/3637) - [Pings disappear from some peers to others after one week #3245](https://github.com/netbirdio/netbird/issues/3245)

saavagebueno commented

2026-08-05 01:13:39 -04:00

@Markovich01 commented on GitHub (May 28, 2025):

Hey all,

In the absence of an official response from the NetBird team, here is my experience:

We were having the same unreliability between peers and have been scanning the repo's issues to see if other people have also been having the same problem or if there have been any suggestions for fixes/mitigations. I found your issue and after looking at your debug output I noticed that (at least some of) your peers had quantum resistance enabled. This made me consider whether Rosenpass was causing problems. To test this we disabled quantum resistance and instead set a pre-shared key on all peers, from then we have had perfect uptime. However, YMMV as I have not monitored pings as closely as you did in your original comment.

With this and the fact that our preferred Android client doesn't work with Rosenpass enabled (you can read more on their repo) we have decided to entirely stop using NetBird's implementation of quantum resistance via Rosenpass.

Hope this helps...

@Markovich01 commented on GitHub (May 28, 2025): Hey all, In the absence of an official response from the NetBird team, here is my experience: We were having the same unreliability between peers and have been scanning the repo's issues to see if other people have also been having the same problem or if there have been any suggestions for fixes/mitigations. I found your issue and after looking at your debug output I noticed that (at least some of) your peers had quantum resistance enabled. This made me consider whether Rosenpass was causing problems. To test this we disabled quantum resistance and instead set a pre-shared key on all peers, from then we have had perfect uptime. However, YMMV as I have not monitored pings as closely as you did in your original comment. With this and the fact that our preferred Android client doesn't work with Rosenpass enabled [(you can read more on their repo)](https://codeberg.org/bg443/JetBird/issues/41#issue-1087724) we have decided to entirely stop using NetBird's implementation of quantum resistance via Rosenpass. Hope this helps...

saavagebueno commented

2026-08-05 01:13:39 -04:00

@trbutler commented on GitHub (Jun 3, 2025):

@Markovich01 Thank you. I hate turning off quantum resistance, but this does indeed seem to be helping. On another, possibly related report I'd filed, I just wrote about the improved network stability I'm observing after doing as you suggested:

Following up on what @Markovich01 had suggested in #3852. I disabled quantum resistance on every peer on my Netbird network (since the peers couldn't communicate if I only turned it off on some of them) and about 12 hours later, all the peers are still talking to each other. Perhaps more notably, thus far, my attempts to wake the Mac have been smooth without the 100%+ core usage I've been sharing in this bug report. Moreover, Netbird's average CPU usage, which had been hovering between 10-20% constantly on an Apple M3 has dipped to about 0.6% (which is, obviously, way better for battery life on a laptop!).

Whereas previously Netbird would be the most demanding process upon wake and remain in the top five most demanding processes constantly, it seems to be hovering around the 15th most demanding process in Activity Monitor at the moment.

This makes me strongly suspect the bug with waking up a Mac has something to do with Rosenpass. I've been using Rosenpass in Permissive mode, incidentally -- I have not tested it in the non-permissive mode. What is less clear is if it has to do directly with Rosenpass on MacOS or the general network instability that seems to be happening with Rosenpass, since this switch does seem to be improving the general Netbird network instability I reported in that other bug report, as well.

This makes me think if whatever is causing issues with Quantum Resistance were fixed, it might fix problems with MacOS sleep-wake, as well. Hopefully it will continue this trend -- at least it appears my Netbird network has become more reliably usable than it has been in recently months!

@trbutler commented on GitHub (Jun 3, 2025): @Markovich01 Thank you. I hate turning off quantum resistance, but this does indeed seem to be helping. On [another, possibly related report I'd filed](https://github.com/netbirdio/netbird/issues/2454#issuecomment-2936722278), I just wrote about the improved network stability I'm observing after doing as you suggested: > Following up on what [@Markovich01](https://github.com/Markovich01) had suggested in [#3852](https://github.com/netbirdio/netbird/issues/3852). I disabled quantum resistance on every peer on my Netbird network (since the peers couldn't communicate if I only turned it off on some of them) and about 12 hours later, all the peers are still talking to each other. Perhaps more notably, thus far, my attempts to wake the Mac have been smooth without the 100%+ core usage I've been sharing in this bug report. Moreover, Netbird's _average_ CPU usage, which had been hovering between 10-20% constantly on an Apple M3 has dipped to about 0.6% (which is, obviously, way better for battery life on a laptop!). > > Whereas previously Netbird would be the most demanding process upon wake and remain in the top five most demanding processes constantly, it seems to be hovering around the 15th most demanding process in Activity Monitor at the moment. > > This makes me strongly suspect the bug with waking up a Mac has something to do with Rosenpass. I've been using Rosenpass in Permissive mode, incidentally -- I have not tested it in the non-permissive mode. What is less clear is if it has to do directly with Rosenpass on MacOS or the general network instability that seems to be happening with Rosenpass, since this switch does seem to be improving the general Netbird network instability I reported in that other bug report, as well. This makes me think if whatever is causing issues with Quantum Resistance were fixed, it might fix problems with MacOS sleep-wake, as well. Hopefully it will continue this trend -- at least it appears my Netbird network has become more reliably usable than it has been in recently months!

saavagebueno commented

2026-08-05 01:13:39 -04:00

@trbutler commented on GitHub (Jul 13, 2025):

About a month after @Markovich01's suggestion, I've continued with Rosenpass off and Netbird is running incredibly reliably (system resource usage has been dramatically been reduced and fails on wake from sleep per #2454 have also been resolved). That's wonderful for being able to depend on Netbird's network, but it's unfortunate not being able to use Rosenpass and it seems to confirm there's a Rosenpass problem at the heart of both this report and #2454.

@trbutler commented on GitHub (Jul 13, 2025): About a month after @Markovich01's suggestion, I've continued with Rosenpass off and Netbird is running incredibly reliably (system resource usage has been dramatically been reduced and fails on wake from sleep per #2454 have also been resolved). That's wonderful for being able to depend on Netbird's network, but it's unfortunate not being able to use Rosenpass and it seems to confirm there's a Rosenpass problem at the heart of both this report and #2454.

saavagebueno commented

2026-08-05 01:13:39 -04:00

@nazarewk commented on GitHub (Jul 14, 2025):

@trbutler, thanks a lot for the delayed feedback and the summary of what else was fixed by disabling Rosenpass. I'll pass it down to the team.

@nazarewk commented on GitHub (Jul 14, 2025): @trbutler, thanks a lot for the delayed feedback and the summary of what else was fixed by disabling Rosenpass. I'll pass it down to the team.

saavagebueno commented

2026-08-05 01:13:39 -04:00

@itoffshore commented on GitHub (Feb 7, 2026):

I've hit this issue with 40 peers with udp 3478 allowed outbound. I've just checked all my fw logs & only see some udp 3478 packets dropped on eth0 from unknown hosts to 1 peer.

Maybe look at how yggdrasil-network does things. It's been 100% stable over months with system updates every few days in openSUSE's Micro OS (an immutable rolling release with reboots for updates every 2-3 days). Possibly it's reliability is related to yggdrasil being an ipv6 network rather than ipv4 (so no need for STUN / TURN) - less moving parts = less to go wrong.

My peers only connect to each other with no connections to the public yggdrasil network. The routing algo they use is self-healing.

This has only become an issue over the last 2 weeks. Previously my setup with netbird cloud ran flawlessly for months on end with 10 peers. I have noticed with wireguard once you get to 11-12 peers the mesh begins to have issues (which is what led me to Netbird in the first place)

Perhaps Netbird over mainly ipv6 with some ipv4 relays (for peers without ipv6) - will improve reliability & be easier to scale ?

I only have yggdrasil running on 3 peers at the moment (for a Garage S3 cluster - I discovered yggdrasil recommended on their wiki) & plan to run it everywhere - my thoughts being running an ipv4 & ipv6 mesh with services listening on both interfaces would improve reliability. I also plan to self host netbird next to help isolate the issue.

@itoffshore commented on GitHub (Feb 7, 2026): I've hit this issue with 40 peers with `udp 3478` allowed outbound. I've just checked all my fw logs & only see some `udp 3478` packets dropped on `eth0` from unknown hosts to `1` peer. Maybe look at how yggdrasil-network does things. It's been 100% stable over months with system updates every few days in openSUSE's Micro OS (an immutable rolling release with reboots for updates every 2-3 days). Possibly it's reliability is related to yggdrasil being an ipv6 network rather than ipv4 (so no need for STUN / TURN) - less moving parts = less to go wrong. My peers only connect to each other with no connections to the public yggdrasil network. The routing algo they use is self-healing. This has only become an issue over the last 2 weeks. Previously my setup with netbird cloud ran flawlessly for months on end with `10` peers. I have noticed with wireguard once you get to 11-12 peers the mesh begins to have issues (which is what led me to Netbird in the first place) Perhaps Netbird over mainly ipv6 with some ipv4 relays (for peers without ipv6) - will improve reliability & be easier to scale ? I only have yggdrasil running on 3 peers at the moment (for a Garage S3 cluster - I discovered yggdrasil recommended on their wiki) & plan to run it everywhere - my thoughts being running an ipv4 & ipv6 mesh with services listening on both interfaces would improve reliability. I also plan to self host netbird next to help isolate the issue.

saavagebueno commented

2026-08-05 01:13:39 -04:00

@0-wHiTeHand-0 commented on GitHub (Jul 7, 2026):

Same here. With PQ on the tunnels are very unreliable. With PQ off everything works perfectly.

@0-wHiTeHand-0 commented on GitHub (Jul 7, 2026): Same here. With PQ on the tunnels are very unreliable. With PQ off everything works perfectly.

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