[GH-ISSUE #1718] Access control policies don't work #3086

New Issue

saavagebueno · 2026-08-05T00:50:32-04:00

saavagebueno commented

2026-08-05 00:50:32 -04:00

Originally created by @sisumara on GitHub (Mar 15, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1718

Describe the problem

Today I've deployed a new setup which has separated IDP based on Zitadel and Netbird which I've configured using advanced configuration guide. I have one server in a cloud which has docker installation with couple of services and netbird agent installed in the same network with docker services. I've deleted default access policy rule and added custom one, which allows the only UDP traffic.

I've added a new route with peer and the docker network.

And traffic began to flow from User peer to OracleDC peer, but not the traffic which is limited by the access policy rule, but any traffic. So, in this case I allowed the only UDP traffic, but I can ping hosts in remote network and access to the services on 80,443/tcp ports.

To Reproduce

Steps to reproduce the behavior:

Deploy a new service
Add some peers to different groups.
Create network route which sits behind one of the peers.
Delete default access policy and create a new one which limits the access to the peers with network routes.
Feel free to access to any resources in the route without limitations of created access policy.

Expected behavior

Limited traffic according to created Access Policy.

Are you using NetBird Cloud?

self-host NetBird's control plane.

NetBird version

0.26.3

Thank you

Originally created by @sisumara on GitHub (Mar 15, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1718 **Describe the problem** Today I've deployed a new setup which has separated IDP based on Zitadel and Netbird which I've configured using advanced configuration guide. I have one server in a cloud which has docker installation with couple of services and netbird agent installed in the same network with docker services. I've deleted default access policy rule and added custom one, which allows the only UDP traffic. <img width="1496" alt="Screenshot 2024-03-15 at 4 54 41 PM" src="https://github.com/netbirdio/netbird/assets/61536902/1ae572f8-dc72-4b31-af60-d7770dd0f66c"> I've added a new route with peer and the docker network. <img width="1496" alt="Screenshot 2024-03-15 at 4 56 58 PM" src="https://github.com/netbirdio/netbird/assets/61536902/0efa39b5-7852-466b-9b54-f91d4c5d05fe"> And traffic began to flow from User peer to OracleDC peer, but not the traffic which is limited by the access policy rule, but any traffic. So, in this case I allowed the only UDP traffic, but I can ping hosts in remote network and access to the services on 80,443/tcp ports. **To Reproduce** Steps to reproduce the behavior: 1. Deploy a new service 2. Add some peers to different groups. 3. Create network route which sits behind one of the peers. 4. Delete default access policy and create a new one which limits the access to the peers with network routes. 5. Feel free to access to any resources in the route without limitations of created access policy. **Expected behavior** Limited traffic according to created Access Policy. **Are you using NetBird Cloud?** self-host NetBird's control plane. **NetBird version** `0.26.3` Thank you

saavagebueno added the client question routes labels 2026-08-05 00:50:32 -04:00

saavagebueno closed this issue

2026-08-05 00:50:32 -04:00

saavagebueno commented

2026-08-05 00:50:33 -04:00

@braginini commented on GitHub (Mar 16, 2024):

Hey @sisumara
This is a know limitation. The access control rule you have set up is applied to the routing peer but not the machines behind it.
We are working on enhancing the access control to apply port and protocol restrictions on the machines behind the router.

Do you want to limit ports and protocols for the whole network behind the router or individual resources?

@braginini commented on GitHub (Mar 16, 2024): Hey @sisumara This is a know limitation. The access control rule you have set up is applied to the routing peer but not the machines behind it. We are working on enhancing the access control to apply port and protocol restrictions on the machines behind the router. Do you want to limit ports and protocols for the whole network behind the router or individual resources?

saavagebueno commented

2026-08-05 00:50:33 -04:00

@sisumara commented on GitHub (Mar 17, 2024):

Hey @sisumara This is a know limitation. The access control rule you have set up is applied to the routing peer but not the machines behind it. We are working on enhancing the access control to apply port and protocol restrictions on the machines behind the router.

So, I can limit traffic flow with access policies the only to the peers, right?

Do you want to limit ports and protocols for the whole network behind the router or individual resources?

I have couple of cases and in some of them it needs to limit the whole network in some of them just certain hosts in the network.

@sisumara commented on GitHub (Mar 17, 2024): > Hey @sisumara This is a know limitation. The access control rule you have set up is applied to the routing peer but not the machines behind it. We are working on enhancing the access control to apply port and protocol restrictions on the machines behind the router. > So, I can limit traffic flow with access policies the only to the peers, right? > Do you want to limit ports and protocols for the whole network behind the router or individual resources? I have couple of cases and in some of them it needs to limit the whole network in some of them just certain hosts in the network.

saavagebueno commented

2026-08-05 00:50:33 -04:00

@barto95100 commented on GitHub (Mar 22, 2024):

YEs the same, test to accept juste in TCP port 32400 (plex) and the host with netbird agent havec access to connecte on SSH :
explain flow

host peer agent ----> host routing peer -----> server plex

I want to block the host peer agent just right access on port 32400 and not all port in host beinhind routing peer

@barto95100 commented on GitHub (Mar 22, 2024): YEs the same, test to accept juste in TCP port 32400 (plex) and the host with netbird agent havec access to connecte on SSH : explain flow host peer agent ----> host routing peer -----> server plex I want to block the host peer agent just right access on port 32400 and not all port in host beinhind routing peer

saavagebueno commented

2026-08-05 00:50:33 -04:00

@Cheekie25 commented on GitHub (Apr 16, 2025):

I have the same need: I would like to limit ports and protocols for the whole network behind the router.
Do you any ETA for this feature ?
Do you know any workaround ?
Thank you

@Cheekie25 commented on GitHub (Apr 16, 2025): I have the same need: I would like to limit ports and protocols for the whole network behind the router. Do you any ETA for this feature ? Do you know any workaround ? Thank you

saavagebueno commented

2026-08-05 00:50:33 -04:00

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

I have the same need: I would like to limit ports and protocols for the whole network behind the router. Do you any ETA for this feature ? Do you know any workaround ? Thank you

I am pretty sure it's perfectly achievable and working with:

introduction of protocols and ports on access policies
the new Networks feature (made of Resources and Routing Peers) on the current version.

I am closing this because I believe this is fully addressed, but feel free to comment and we'll reopen.

@nazarewk commented on GitHub (Apr 17, 2025): > I have the same need: I would like to limit ports and protocols for the whole network behind the router. Do you any ETA for this feature ? Do you know any workaround ? Thank you I am pretty sure it's perfectly achievable and working with: - introduction of protocols and ports on access policies - the new Networks feature (made of Resources and Routing Peers) on the current version. I am closing this because I believe this is fully addressed, but feel free to comment and we'll reopen.

saavagebueno commented

2026-08-05 00:50:33 -04:00

@Cheekie25 commented on GitHub (Apr 17, 2025):

Thank you for your answer.

My goal is to be able to reach some web service on a specific port of a resource but that the other web services on the same resource do not be accessible.

I just tried the following setup without success:

One docker peer "NAS" with network mode host (v0.41.3).
Groups "All" and "Secret".
One iPhone (v0.36.4-dev according to the the UI and 0.0.9 in the app. No update is available in the App Store).
Group "All".
One network named "Private" with one resource "MY NAS" with 192.168.1.50/32 for the address.
Group "Secret".
Routing peer: "NAS" (Masquerade activated).

I have two http web services running on "MY NAS".
One on port 9000 and one on port 82.

Now if I don't set any policy to the "Private" network, I can't reach any service of my "MY NAS" resource from the iPhone.
But if I add a policy that links the groups, "All" to "Secrets", I can reach all of the service.

The issue is that even if the policy has the only direction "All" to "Secrets" and that the port 9000 and TCP protocol are specified, I can still reach the web service on the port 82 that is running on the same resource.

I'm I missing something ?

@Cheekie25 commented on GitHub (Apr 17, 2025): Thank you for your answer. My goal is to be able to reach some web service on a specific port of a resource but that the other web services on the same resource do not be accessible. I just tried the following setup without success: - One docker peer "NAS" with network mode host (v0.41.3). Groups "All" and "Secret". - One iPhone (v0.36.4-dev according to the the UI and 0.0.9 in the app. No update is available in the App Store). Group "All". - One network named "Private" with one resource "MY NAS" with 192.168.1.50/32 for the address. Group "Secret". Routing peer: "NAS" (Masquerade activated). I have two http web services running on "MY NAS". One on port 9000 and one on port 82. Now if I don't set any policy to the "Private" network, I can't reach any service of my "MY NAS" resource from the iPhone. But if I add a policy that links the groups, "All" to "Secrets", I can reach all of the service. The issue is that even if the policy has the only direction "All" to "Secrets" and that the port 9000 and TCP protocol are specified, I can still reach the web service on the port 82 that is running on the same resource. I'm I missing something ?

saavagebueno commented

2026-08-05 00:50:33 -04:00

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

I'm I missing something ?

You should use a dedicated group (let's call it X) for your client devices instead of All.
Then create Access Control policy allowing access from Group X to Group Secret
limit the policy to ports 9000 & 82. Note you need to select either TCP or UDP to do that
(optionally) duplicate the rule if you need access to both TCP and UDP on those ports

There is one caveat: if you were to separate Resource's Group from Routing Peer's Group and the 192.168.1.50 belonged to the Peer doing the routing (NetBird was installed on the same NAS) you would need to allow access to both Groups to be able to access NAS's LAN IP over NetBird.

@nazarewk commented on GitHub (Apr 18, 2025): > I'm I missing something ? 1. You should use a dedicated group (let's call it `X`) for your client devices instead of `All`. 2. Then create Access Control policy allowing access from Group `X` to Group `Secret` 3. limit the policy to ports 9000 & 82. Note you need to select either `TCP` or `UDP` to do that 4. (optionally) duplicate the rule if you need access to both TCP and UDP on those ports There is one caveat: if you were to separate Resource's Group from Routing Peer's Group and the `192.168.1.50` belonged to the Peer doing the routing (NetBird was installed on the same NAS) you would need to allow access to **both** Groups to be able to access NAS's LAN IP over NetBird.

saavagebueno commented

2026-08-05 00:50:33 -04:00

@Cheekie25 commented on GitHub (Apr 21, 2025):

I tried several setups, here are 3 but I tried others. In each case: either nothing can be reached, or everything can.
I haven't found any case where only the 9000 port of the resource would be reachable (and the 82 port wouldn't).

Devices and IPs
Devices and IPs	iPhone 100.75.71.147 -	NAS (Routing peer) 100.75.15.109 192.168.1.50	MY NAS (Resource) - 192.168.1.50/32
Groups	X	Secret	Secret

Policies	Result
X --> Secret (TCP port 9000)	iPhone can connect to 192.168.1.50:9000 and 192.168.1.50:82

Devices and IPs
Devices and IPs	iPhone 100.75.71.147 -	NAS (Routing peer) 100.75.15.109 192.168.1.50	MY NAS (Resource) - 192.168.1.50/32
Groups	X	Secret	Res

Policies	Result
X --> Secret (TCP port 9000)	iPhone can't connect to 192.168.1.50
Secret --> Res (TCP port 9000)	iPhone can't connect to 192.168.1.50

Devices and IPs
Devices and IPs	iPhone 100.75.71.147 -	NAS (Routing peer) 100.75.15.109 192.168.1.50	MY NAS (Resource) - 192.168.1.50/32
Groups	X	Secret	Res

Policies	Result
X --> Res (TCP port 9000)	iPhone can connect to 192.168.1.50:9000 and 192.168.1.50:82

@Cheekie25 commented on GitHub (Apr 21, 2025): I tried several setups, here are 3 but I tried others. In each case: either nothing can be reached, or everything can. I haven't found any case where only the 9000 port of the resource would be reachable (and the 82 port wouldn't). 1) <table><thead> <tr> <th rowspan="2">Devices <br>and IPs</th> </tr> <tr> <th>iPhone <br>100.75.71.147<br>- </th> <th>NAS (Routing peer)<br>100.75.15.109<br>192.168.1.50</th> <th>MY NAS (Resource)<br>- <br>192.168.1.50/32</th> </tr></thead> <tbody> <tr> <td>Groups</td> <td>X</td> <td>Secret</td> <td>Secret</td> </tr> </tbody> </table> <table><thead> <tr> <th>Policies</th> <th>Result</th> </tr></thead> <tbody> <tr> <td>X --> Secret (TCP port 9000)</td> <td>iPhone can connect to 192.168.1.50:9000 and 192.168.1.50:82</td> </tr> </tbody> </table> 2. <table><thead> <tr> <th rowspan="2">Devices <br>and IPs</th> </tr> <tr> <th>iPhone <br>100.75.71.147<br>- </th> <th>NAS (Routing peer)<br>100.75.15.109<br>192.168.1.50</th> <th>MY NAS (Resource)<br>- <br>192.168.1.50/32</th> </tr></thead> <tbody> <tr> <td>Groups</td> <td>X</td> <td>Secret</td> <td>Res</td> </tr> </tbody> </table> <table><thead> <tr> <th>Policies</th> <th>Result</th> </tr></thead> <tbody> <tr> <td>X --> Secret (TCP port 9000)</td> <th rowspan="2">iPhone can't connect to 192.168.1.50</th> </tr> <tr> <td>Secret --> Res (TCP port 9000)</td> </tr> </tbody> </table> 3. <table><thead> <tr> <th rowspan="2">Devices <br>and IPs</th> </tr> <tr> <th>iPhone <br>100.75.71.147<br>- </th> <th>NAS (Routing peer)<br>100.75.15.109<br>192.168.1.50</th> <th>MY NAS (Resource)<br>- <br>192.168.1.50/32</th> </tr></thead> <tbody> <tr> <td>Groups</td> <td>X</td> <td>Secret</td> <td>Res</td> </tr> </tbody> </table> <table><thead> <tr> <th>Policies</th> <th>Result</th> </tr></thead> <tbody> <tr> <td>X --> Res (TCP port 9000)</td> <td>iPhone can connect to 192.168.1.50:9000 and 192.168.1.50:82</td> </tr> </tbody> </table>

saavagebueno commented

2026-08-05 00:50:33 -04:00

@Cheekie25 commented on GitHub (Apr 23, 2025):

I tried with a Routing peer on another device than the Resource one (but on the same local network so it could reach the Resource).
In this configuration, the policies behave as expected 👍 .
Any way to make that work when the Routing Peer and the Resource are on the same device ?

@Cheekie25 commented on GitHub (Apr 23, 2025): I tried with a Routing peer on another device than the Resource one (but on the same local network so it could reach the Resource). In this configuration, the policies behave as expected 👍 . Any way to make that work when the Routing Peer and the Resource are on the same device ?

saavagebueno commented

2026-08-05 00:50:33 -04:00

@jkolczasty commented on GitHub (Feb 16, 2026):

Same here. I added e.g. policy to allow Group1 to some resource ICMP only and user can still connect to TCP ports. If I disable policy with ICMP, user no long can connect TCP connections. Looks like policy is working on L3 only.

Client: 0.65.1
Management: v0.65.1

Peer and Resource are NOT in the same network, not even in the same location.

See my comment: https://github.com/netbirdio/netbird/issues/4787#issuecomment-3908066932

@jkolczasty commented on GitHub (Feb 16, 2026): Same here. I added e.g. policy to allow Group1 to some resource ICMP only and user can still connect to TCP ports. If I disable policy with ICMP, user no long can connect TCP connections. Looks like policy is working on L3 only. Client: 0.65.1 Management: v0.65.1 Peer and Resource are NOT in the same network, not even in the same location. See my comment: https://github.com/netbirdio/netbird/issues/4787#issuecomment-3908066932

saavagebueno referenced this issue

2026-08-05 04:06:00 -04:00

[PR #3086] [MERGED] [management] Fix event meta #16334

saavagebueno referenced this issue

2026-08-05 04:06:00 -04:00

[PR #3086] [management] Fix event meta #16342

saavagebueno referenced this issue

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

[PR #3086] [MERGED] [management] Fix event meta #19256

saavagebueno referenced this issue

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

[PR #3086] [management] Fix event meta #19260

saavagebueno referenced this issue

2026-08-05 05:08:33 -04:00

[PR #3086] [MERGED] [management] Fix event meta #21471

saavagebueno referenced this issue

2026-08-05 05:08:34 -04:00

[PR #3086] [management] Fix event meta #21479

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