[GH-ISSUE #2522] Netbird will not work when any VPN is active. #5170

New Issue

saavagebueno · 2026-08-05T01:01:45-04:00

saavagebueno commented

2026-08-05 01:01:45 -04:00

Originally created by @ismail0234 on GitHub (Sep 3, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2522

Describe the problem

If programs such as AvastVPN/NordVPN are active, peers cannot be pinged.

To Reproduce

Steps to reproduce the behavior:

Install Avast VPN.
Assign 2 peers to the same group and allow ICMP type in the group policy.
Peers cannot ping each other.

Expected behavior

While the VPN is active, peers should be able to ping each other without any problems.

Are you using NetBird Cloud?

No, Self Hosted.

NetBird version

0.28.7

NetBird status -dA output:

Do you face any (non-mobile) client issues?

Screenshots

Additional context

Originally created by @ismail0234 on GitHub (Sep 3, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2522 **Describe the problem** If programs such as AvastVPN/NordVPN are active, peers cannot be pinged. **To Reproduce** Steps to reproduce the behavior: 1. Install Avast VPN. 2. Assign 2 peers to the same group and allow ICMP type in the group policy. 3. Peers cannot ping each other. **Expected behavior** While the VPN is active, peers should be able to ping each other without any problems. **Are you using NetBird Cloud?** No, Self Hosted. **NetBird version** 0.28.7 **NetBird status -dA output:** - **Do you face any (non-mobile) client issues?** - **Screenshots** - **Additional context** -

saavagebueno added the waiting-feedback triage-needed labels 2026-08-05 01:01:45 -04:00

saavagebueno commented

2026-08-05 01:01:45 -04:00

@nazarewk commented on GitHub (Sep 3, 2024):

To be honest so much can go wrong here I would not expect any kind of support for running multiple VPN solutions at the same time apart from help investigating the networking side:

your other VPN might be taking over all routes
your other VPN might be inserting firewall rules forwarding packets somewhere else before Netbird rules
switching VPN activation order might help or it might not
it can be anything in between or everything all at once

I tried investigating running OpenVPN alongside Netbird, but gave up after few hours. There is a good reason most of the clients (OpenVPN Connect being one) do not even support connecting to more than one supported server at a time.

@nazarewk commented on GitHub (Sep 3, 2024): To be honest so much can go wrong here I would not expect any kind of support for running multiple VPN solutions at the same time apart from help investigating the networking side: - your other VPN might be taking over all routes - your other VPN might be inserting firewall rules forwarding packets somewhere else before Netbird rules - switching VPN activation order might help or it might not - it can be anything in between or everything all at once I tried investigating running OpenVPN alongside Netbird, but gave up after few hours. There is a good reason most of the clients (OpenVPN Connect being one) do not even support connecting to more than one supported server at a time.

saavagebueno commented

2026-08-05 01:01:45 -04:00

@ismail0234 commented on GitHub (Sep 4, 2024):

It would be nice if there was a fix for this if possible. Or is there a simple way to prioritize Netbird even when other VPNs are active?

@ismail0234 commented on GitHub (Sep 4, 2024): It would be nice if there was a fix for this if possible. Or is there a simple way to prioritize Netbird even when other VPNs are active?

saavagebueno commented

2026-08-05 01:01:46 -04:00

@nazarewk commented on GitHub (Sep 5, 2024):

As I have written it is highly specific to exact implementations of all VPN solutions you want to mix together and most likely not possible to tune without modifying their source codes. Only sane way I would see it working would be running each in their own container/VM and setting up routing on the host system yourself.

@nazarewk commented on GitHub (Sep 5, 2024): As I have written it is highly specific to exact implementations of all VPN solutions you want to mix together and most likely not possible to tune without modifying their source codes. Only sane way I would see it working would be running each in their own container/VM and setting up routing on the host system yourself.

saavagebueno commented

2026-08-05 01:01:46 -04:00

@ismail0234 commented on GitHub (Sep 5, 2024):

This does not seem to be a viable method. It doesn't seem to work in a system with hundreds/thousands of users.

@ismail0234 commented on GitHub (Sep 5, 2024): This does not seem to be a viable method. It doesn't seem to work in a system with hundreds/thousands of users.

saavagebueno commented

2026-08-05 01:01:46 -04:00

@nazarewk commented on GitHub (Sep 5, 2024):

Generally Netbird itself is quite unobtrusive, modifies very little in the system and can easily run multiple instances of itself at the same machine (minus DNS integration), the problem is often with the other VPN you are trying to run alongside either being either too invasive or having a few incompatible touch points. You'd need to analyze behavior of all solutions and figure out how to mix them yourself.

I would not be surprised if Avast took over the whole system routing table, installed it's own root certificate and MITMed/spied on all connections you're doing.

@nazarewk commented on GitHub (Sep 5, 2024): Generally Netbird itself is quite unobtrusive, modifies very little in the system and can easily run multiple instances of itself at the same machine (minus DNS integration), the problem is often with the other VPN you are trying to run alongside either being either too invasive or having a few incompatible touch points. You'd need to analyze behavior of all solutions and figure out how to mix them yourself. I would not be surprised if Avast took over the whole system routing table, installed it's own root certificate and MITMed/spied on all connections you're doing.

saavagebueno commented

2026-08-05 01:01:46 -04:00

@nazarewk commented on GitHub (Sep 5, 2024):

I think maybe you're confusing the "real" VPN/zero-trust network solutions with what is commercially branded a "VPN".

VPN stands for Virtual Private Network. Those are meant for securely connecting clients (or whole sites) to (selected set of) resources running inside a private/internal/non-public networks over (insecure/non-private) internet connection. Those can also be described/branded as zero-trust networks and offered alongside firewall solutions.
Examples of "VPNs" are: Netbird, OpenVPN, Wireguard.
Examples of zero-trust networks are: Twingate, Cisco AnyConnect, FortiClient, Citrix, ZScaler etc.

The commercial "VPN" offerings are pretty much anonymizations proxies meant for routing all of consumer device's traffic through those so: 1) they appear located somewhere else 2) the traffic is not leaking into (or peeked through) insecure public hotspots.
They are very often purpose-built for hijacking all of the traffic and not allowing anything around them (which prevents working together with other solutions) to deliver on their primary purpose of making average internet user more secure on public hotspots.
Examples of those are: Tor Network, Mullvad VPN, Avast VPN, Nord VPN, Proton VPN.

While you can explicitly configure most of "real VPN" solutions to act the same or similarily as "commercial VPN", some of them are hard to put into one of those 2 buckets.

Generally I would not expect any kind of "commercial VPN" solution to work alongside "real" VPN/zero-trust network unless 1) the "commercial VPN" were extremely well behaved and thoughtfully implemented 2) it explicitly supported running alongside other solutions.

@nazarewk commented on GitHub (Sep 5, 2024): I think maybe you're confusing the "real" VPN/zero-trust network solutions with what is commercially branded a "VPN". VPN stands for Virtual Private Network. Those are meant for securely connecting clients (or whole sites) to (selected set of) resources running inside a private/internal/non-public networks over (insecure/non-private) internet connection. Those can also be described/branded as zero-trust networks and offered alongside firewall solutions. Examples of "VPNs" are: Netbird, OpenVPN, Wireguard. Examples of zero-trust networks are: Twingate, Cisco AnyConnect, FortiClient, Citrix, ZScaler etc. The commercial "VPN" offerings are pretty much anonymizations proxies meant for routing all of consumer device's traffic through those so: 1) they appear located somewhere else 2) the traffic is not leaking into (or peeked through) insecure public hotspots. They are very often purpose-built for hijacking all of the traffic and not allowing anything around them (which prevents working together with other solutions) to deliver on their primary purpose of making average internet user more secure on public hotspots. Examples of those are: Tor Network, Mullvad VPN, Avast VPN, Nord VPN, Proton VPN. While you can explicitly configure most of "real VPN" solutions to act the same or similarily as "commercial VPN", some of them are hard to put into one of those 2 buckets. Generally I would not expect any kind of "commercial VPN" solution to work alongside "real" VPN/zero-trust network unless 1) the "commercial VPN" were extremely well behaved and thoughtfully implemented 2) it explicitly supported running alongside other solutions.

saavagebueno commented

2026-08-05 01:01:46 -04:00

@ismail0234 commented on GitHub (Sep 5, 2024):

If there is no solution for this that netbird can do, then I guess it is not a bug.

@ismail0234 commented on GitHub (Sep 5, 2024): If there is no solution for this that netbird can do, then I guess it is not a bug.

saavagebueno commented

2026-08-05 01:01:46 -04:00

@alexsyw commented on GitHub (Sep 7, 2024):

I ran into the same problem, Tailscale is installed on the machines and no ACL rules work :(
Disabling tailscale it helps, will there be a solution to this problem?

@alexsyw commented on GitHub (Sep 7, 2024): I ran into the same problem, Tailscale is installed on the machines and no ACL rules work :( Disabling tailscale it helps, will there be a solution to this problem?

saavagebueno commented

2026-08-05 01:01:46 -04:00

@tjuberg commented on GitHub (Sep 8, 2024):

I'm investigating a similar issue, and this seems to be related, so apologies if this misses the mark.
Although I have no illusions of the ability to co-exist with any traditional VPN solutions as they in most cases by nature take the "this is my world and no one else are allowed" approach and traditionally this has also been the desired approach for customers. In a more fragmented and globalized reality where traditional VPNs have had growing pains amongst others.

I had hoped to be able to coexist with other wireguard based solutions in more modern security settings, as there is no technical reason it could not be done without larger problems.

In my case the investigation kicked off on a Linux system where I need to have Tailscale and ideally netbird at once to avoid having to do separate systems and duplication of work.

The first obvious hurdle is that Netbird configures it's DNS server on the interface to be its own client RFC 6598 IP. This causes a constant log spam of

systemd-resolved[63872]: Using degraded feature set TCP instead of UDP for DNS server 100.97.NNN.NN

Now, while there is a range collison between Netbird and Tailscale in this instance, I suspect that the actual underlying problem is either in how netbird handles DNS in combination with the desicion to use such a large address space to be routed increasing the chance of collisions for anyone unfortunate enough to reside behind a CGNAT.

Abusing RFC 6598 subnets is not isolated to Netbird or Tailscale, but also commonplace nowdays both for container solutions and kubernetes further increasing likelyhood of conflicts when using /16 by default.

Tailscale approach:

IP4.ROUTE[1]: dst = 100.76.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[2]: dst = 100.81.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[3]: dst = 100.91.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[4]: dst = 100.99.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[5]: dst = 100.113.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[6]: dst = 100.93.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[7]: dst = 100.97.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[8]: dst = 100.99.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[9]: dst = 100.100.100.100/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[10]: dst = 100.89.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[11]: dst = 100.90.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[12]: dst = 100.96.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[13]: dst = 100.103.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[14]: dst = 100.105.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[15]: dst = 100.124.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[16]: dst = 100.91.70.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[17]: dst = 100.116.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52
IP4.ROUTE[18]: dst = 100.125.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52

If memory serves, this is their DNS server IP, along with clients in my tailnet

In contrast to netbird's broader approach:

IP4.ROUTE[1]: dst = 100.97.0.0/16, nh = 0.0.0.0, mt = 0

Most specific route wins, and it would at minimum be wise to add some kind of check and warning if nothing else when such conflicts arises with a link to a caveat knowledgebase to inform.

I don't expect this to turn into a supported use case, but it would have been nice.

@tjuberg commented on GitHub (Sep 8, 2024): I'm investigating a similar issue, and this seems to be related, so apologies if this misses the mark. Although I have no illusions of the ability to co-exist with any traditional VPN solutions as they in most cases by nature take the "this is my world and no one else are allowed" approach and traditionally this has also been the desired approach for customers. In a more fragmented and globalized reality where traditional VPNs have had growing pains amongst others. I had hoped to be able to coexist with other wireguard based solutions in more modern security settings, as there is no technical reason it could not be done without larger problems. In my case the investigation kicked off on a Linux system where I need to have Tailscale and ideally netbird at once to avoid having to do separate systems and duplication of work. The first obvious hurdle is that Netbird configures it's DNS server on the interface to be its own client RFC 6598 IP. This causes a constant log spam of > systemd-resolved[63872]: Using degraded feature set TCP instead of UDP for DNS server 100.97.NNN.NN Now, while there is a range collison between Netbird and Tailscale in this instance, I suspect that the actual underlying problem is either in how netbird handles DNS in combination with the desicion to use such a large address space to be routed increasing the chance of collisions for anyone unfortunate enough to reside behind a CGNAT. Abusing RFC 6598 subnets is not isolated to Netbird or Tailscale, but also commonplace nowdays both for container solutions and kubernetes further increasing likelyhood of conflicts when using /16 by default. Tailscale approach: > IP4.ROUTE[1]: dst = 100.76.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[2]: dst = 100.81.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[3]: dst = 100.91.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[4]: dst = 100.99.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[5]: dst = 100.113.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[6]: dst = 100.93.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[7]: dst = 100.97.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[8]: dst = 100.99.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[9]: dst = 100.100.100.100/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[10]: dst = 100.89.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[11]: dst = 100.90.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[12]: dst = 100.96.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[13]: dst = 100.103.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[14]: dst = 100.105.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[15]: dst = 100.124.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[16]: dst = 100.91.70.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[17]: dst = 100.116.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 IP4.ROUTE[18]: dst = 100.125.NNN.NNN/32, nh = 0.0.0.0, mt = 0, table=52 If memory serves, this is their DNS server IP, along with clients in my tailnet In contrast to netbird's broader approach: > IP4.ROUTE[1]: dst = 100.97.0.0/16, nh = 0.0.0.0, mt = 0 Most specific route wins, and it would at minimum be wise to add some kind of check and warning if nothing else when such conflicts arises with a link to a caveat knowledgebase to inform. I don't expect this to turn into a supported use case, but it would have been nice.

saavagebueno commented

2026-08-05 01:01:46 -04:00

@nazarewk commented on GitHub (Apr 28, 2025):

Hello @ismail0234,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

@nazarewk commented on GitHub (Apr 28, 2025): Hello @ismail0234, We're currently reviewing our open issues and would like to verify if this problem still exists in the [latest NetBird version](https://github.com/netbirdio/netbird/releases). Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within **2 weeks**, but feel free to reopen it with updated information. Thanks for your contribution to improving the project!

saavagebueno commented

2026-08-05 01:01:46 -04:00

@ismail0234 commented on GitHub (Apr 28, 2025):

I will check

@ismail0234 commented on GitHub (Apr 28, 2025): I will check

saavagebueno commented

2026-08-05 01:01:46 -04:00

@piradata commented on GitHub (Nov 25, 2025):

the problem still happen, but i think it can be close, as it is not actually a bug.

but, what could be done, is improve the error message that happen if you are for example on the cellphone with the protonvpn and opens the netbird app

netbird keeps giving this message while i have the following enable

the moment I disable this "always active vpn" setting, the netbird app works.

@piradata commented on GitHub (Nov 25, 2025): the problem still happen, but i think it can be close, as it is not actually a bug. but, what could be done, is improve the error message that happen if you are for example on the cellphone with the protonvpn and opens the netbird app ![Screenshot_20251126-012119.NetBird.png](https://github.com/user-attachments/assets/e2634169-a870-4dc4-b85e-936039f57ff5) netbird keeps giving this message while i have the following enable ![Screenshot_20251126-012110.Configurar.png](https://github.com/user-attachments/assets/5fa71e75-016f-4d9d-8bb4-47c3488418d1) the moment I disable this "always active vpn" setting, the netbird app works.

saavagebueno commented

2026-08-05 01:01:46 -04:00

@TheOverpassArsonist commented on GitHub (Mar 8, 2026):

There is a degree to which compatibility will be determined by the rationality (or lackthereof) of the other VPN.

Mullvad, for instance, works perfectly fine so long as you enable local-network sharing. Meanwhile Tailscale and Mullvad throw a temper tantrum, because Tailscale does not let you assign any IP's outside of the CGNAT range no matter what you do (which is a completely absurd limitation for a VPN specifically designed to let you connect to your devices) and Mullvad's local-network sharing option has a hard-coded list of IP ranges it counts as 'local'. (which is bad, and I do hope they change, but it's nowhere near as egregious as Tailscale because at least Mullvad is more focussed on privacy than connectivity)

It's very much a 'weakest link' issue and from what I can tell so far Netbird is a pretty strong link. I've tried a lot of different VPN combinations and to my recollection Netbird has never been the issue. (for instance as far as I'm aware this is an unsolvable problem on mobile because both iOS and Android enforce an absurd one-active-VPN-at-a-time limit. There's no technical reason you can't have several, but the OSes don't allow it last I checked. Granted it's been a while since I've checked on iOS so maybe they fixed it there.)

@TheOverpassArsonist commented on GitHub (Mar 8, 2026): There is a degree to which compatibility will be determined by the rationality (or lackthereof) of the other VPN. Mullvad, for instance, works perfectly fine so long as you enable local-network sharing. Meanwhile Tailscale and Mullvad throw a temper tantrum, because Tailscale does not let you assign any IP's outside of the CGNAT range no matter what you do (which is a completely absurd limitation for a VPN specifically designed to let you connect to your devices) and Mullvad's local-network sharing option has a hard-coded list of IP ranges it counts as 'local'. (which is bad, and I do hope they change, but it's nowhere near as egregious as Tailscale because at least Mullvad is more focussed on privacy than connectivity) It's very much a 'weakest link' issue and from what I can tell so far Netbird is a pretty strong link. I've tried a lot of different VPN combinations and to my recollection Netbird has never been the issue. (for instance as far as I'm aware this is an unsolvable problem on mobile because both iOS and Android enforce an absurd one-active-VPN-at-a-time limit. There's no technical reason you can't have several, but the OSes don't allow it last I checked. Granted it's been a while since I've checked on iOS so maybe they fixed it there.)

saavagebueno commented

2026-08-05 01:01:46 -04:00

@tritaum commented on GitHub (Apr 28, 2026):

has any movement or progress been made on this issue? implementation??

For Mullvad users that need an immediate solution for Linux I just created this mullvad daemon upstream-synced fork which allows you to exclude IPs/IP ranges from the mullvad tunnel, its very straightforward to setup, just replace your current daemon with the one in Releases or install it directly using the AUR package named patched-mullvad-vpn-daemon-bin

If you want to check the source code, report bugs or make suggestions theres a Github repo for that:
https://github.com/tritaum/ip-split-tunneling-mullvad

@tritaum commented on GitHub (Apr 28, 2026): > has any movement or progress been made on this issue? implementation?? For Mullvad users that need an immediate solution for Linux I just created this mullvad daemon upstream-synced fork which allows you to exclude IPs/IP ranges from the mullvad tunnel, its very straightforward to setup, just replace your current daemon with the one in [Releases](https://github.com/tritaum/ip-split-tunneling-mullvad/releases) or install it directly using the AUR package named [patched-mullvad-vpn-daemon-bin](https://aur.archlinux.org/packages/patched-mullvad-vpn-daemon-bin) If you want to check the source code, report bugs or make suggestions theres a Github repo for that: https://github.com/tritaum/ip-split-tunneling-mullvad

saavagebueno commented

2026-08-05 01:01:46 -04:00

@d10n commented on GitHub (May 13, 2026):

For Linux only, my repo cleanly enables NetBird and Mullvad to work together (without needing a patched daemon): https://github.com/d10n/netbird-mullvad-bypass
It's packaged for Arch, Fedora, and Debian, but you can just manually install the config files if you prefer.

@d10n commented on GitHub (May 13, 2026): For Linux only, my repo cleanly enables NetBird and Mullvad to work together (without needing a patched daemon): https://github.com/d10n/netbird-mullvad-bypass It's packaged for Arch, Fedora, and Debian, but you can just manually install the config files if you prefer.

saavagebueno commented

2026-08-05 01:01:46 -04:00

@Binocularbath commented on GitHub (Jun 30, 2026):

Just thought I'd jump in on this ticket as I'm wondering a similar thing. Is there anyway to use netbird and a traditional VPN from my android?

I'm currently on tailscale but looking to migrate. I'm just hoping to find a solution where I can be protected by my VPN while still about to access my home machine. Any comments appreciated

@Binocularbath commented on GitHub (Jun 30, 2026): Just thought I'd jump in on this ticket as I'm wondering a similar thing. Is there anyway to use netbird and a traditional VPN from my android? I'm currently on tailscale but looking to migrate. I'm just hoping to find a solution where I can be protected by my VPN while still about to access my home machine. Any comments appreciated

saavagebueno referenced this issue

2026-08-05 01:24:21 -04:00

[GH-ISSUE #5170] Wildcard DNS records from authoritative DNS fail to resolve when using custom zones #10023

saavagebueno referenced this issue

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

[GH-ISSUE #5170] Wildcard DNS records from authoritative DNS fail to resolve when using custom zones #10704

saavagebueno referenced this issue

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

[GH-ISSUE #5170] Wildcard DNS records from authoritative DNS fail to resolve when using custom zones #10837

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