[GH-ISSUE #4616] [Bug] [Access Control] Peers Within the Same Group Are Reachable #9882

New Issue

saavagebueno · 2026-08-05T01:23:51-04:00

saavagebueno commented

2026-08-05 01:23:51 -04:00

Originally created by @carefreecaribou on GitHub (Oct 9, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4616

Describe the problem

peers within the same group can always reach each other directly. Access control policies only control traffic between different groups, not within a group. When you configure policies allowing Group1 to communicate with Group2 and Group1 to communicate with Group3, and remove the default policy, Group1 members can still ping, scan, and SSH to each other. We do not have peers within the same group advertised. So peers in Group1 cannot see each-other (not including administrator privileged users), but can perform network discovery to determine which peers exist.

To Reproduce

Create two groups in NetBird: Group1, Group2
Add 2-3 peers to Group1
Add 1-2 peers to Group2
Create an access control policy: Allow Group1 → Group2
Remove the default access control policy
Confirm no other policies exist that would allow Group1 → Group1
Test from a regular user peer in Group1: Ping another peer in Group1
All connections within Group1 succeed

Expected behavior

With the default Access Control Policy removed, it is expected that only rules explicitly defined should grant access to groups, peers, and resources.

Are you using NetBird Cloud?

No, Selfhosted.

NetBird version

Netbird Client: v0.59.5
Netbird Server: v0.59.5

Is any other VPN software installed?

Yes. Wireguard, ProtonVPN, but these are disabled during testing.

Debug output

netbirdStatus_dA.txt

Create and upload a debug bundle, and share the returned file key:

9a2544acba54ee76273b90851f8577f72ebad9d0547399a91af5952a5264fafa/d80e6674-afe1-43cd-9e29-2e3882847b4a

Screenshots

Have you tried these troubleshooting steps?

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

Originally created by @carefreecaribou on GitHub (Oct 9, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4616 **Describe the problem** peers within the same group can always reach each other directly. Access control policies only control traffic between different groups, not within a group. When you configure policies allowing Group1 to communicate with Group2 and Group1 to communicate with Group3, and remove the default policy, Group1 members can still ping, scan, and SSH to each other. We do not have peers within the same group advertised. So peers in Group1 cannot see each-other (not including administrator privileged users), but can perform network discovery to determine which peers exist. **To Reproduce** 1. Create two groups in NetBird: Group1, Group2 2. Add 2-3 peers to Group1 3. Add 1-2 peers to Group2 4. Create an access control policy: Allow Group1 → Group2 5. Remove the default access control policy 6. Confirm no other policies exist that would allow Group1 → Group1 7. Test from a regular user peer in Group1: Ping another peer in Group1 8. All connections within Group1 succeed **Expected behavior** With the default Access Control Policy removed, it is expected that only rules explicitly defined should grant access to groups, peers, and resources. **Are you using NetBird Cloud?** No, Selfhosted. **NetBird version** Netbird Client: v0.59.5 Netbird Server: v0.59.5 **Is any other VPN software installed?** Yes. Wireguard, ProtonVPN, but these are disabled during testing. **Debug output** [netbirdStatus_dA.txt](https://github.com/user-attachments/files/22805122/netbirdStatus_dA.txt) Create and upload a debug bundle, and share the returned file key: 9a2544acba54ee76273b90851f8577f72ebad9d0547399a91af5952a5264fafa/d80e6674-afe1-43cd-9e29-2e3882847b4a **Screenshots** <img width="1239" height="443" alt="Image" src="https://github.com/user-attachments/assets/dcf5b27a-6d60-4e5c-9e87-1d1b1812cdf6" /> **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:23:51 -04:00

saavagebueno commented

2026-08-05 01:23:51 -04:00

@lixmal commented on GitHub (Oct 10, 2025):

@carefreecaribou what is the group membership of the peers?

@lixmal commented on GitHub (Oct 10, 2025): @carefreecaribou what is the group membership of the peers?

saavagebueno commented

2026-08-05 01:23:51 -04:00

@Blackclaws commented on GitHub (Oct 10, 2025):

If you check with the new dashboard and select one of your peers it should show you which other peers it is connected to by which policies. We cannot reproduce this with our setups. I'd usually also say that bidirectional policies are mostly a trap because there is seldom a need for the target to contact back, only exceptions are when you want to build a full mesh between nodes.

@Blackclaws commented on GitHub (Oct 10, 2025): If you check with the new dashboard and select one of your peers it should show you which other peers it is connected to by which policies. We cannot reproduce this with our setups. I'd usually also say that bidirectional policies are mostly a trap because there is seldom a need for the target to contact back, only exceptions are when you want to build a full mesh between nodes.

saavagebueno commented

2026-08-05 01:23:51 -04:00

@Blackclaws commented on GitHub (Oct 10, 2025):

I think ping could also be a somewhat special case, I'd have to check but you shouldn't even be peering with those from your own group unless there was an access policy governing that or the node was also part of one of the other groups that you have access to.

@Blackclaws commented on GitHub (Oct 10, 2025): I think ping could also be a somewhat special case, I'd have to check but you shouldn't even be peering with those from your own group unless there was an access policy governing that _or_ the node was also part of one of the other groups that you have access to.

saavagebueno commented

2026-08-05 01:23:51 -04:00

@carefreecaribou commented on GitHub (Oct 10, 2025):

@carefreecaribou what is the group membership of the peers?

@lixmal Both peers during testing are a part of the same group "Tester Group" and the default "All" group:

For testing each user in this group gets access to two other groups "VPN" and "INT". For the initial testing, bidirectional access policies from "Tester" to each of these other two groups were created (But tested with one way policies later on in this post). The VPN group gives you access to network routes. Each "VPN" node is on a certain exit route and is of the type routing Peers. When we disable each of these exit routes, pings are still possible to the peers within my same group. There are currently no other rules affecting INT or any online peers in this group to affect meshing.

If you check with the new dashboard and select one of your peers it should show you which other peers it is connected to by which policies. We cannot reproduce this with our setups.

@Blackclaws The peers within the same group are not showing up as an accessible peer

I think ping could also be a somewhat special case, I'd have to check but you shouldn't even be peering with those from your own group unless there was an access policy governing that or the node was also part of one of the other groups that you have access to.

When we create an explicit one way policy between users within the same group allowing only doom on udp.

Connections are restricted as expected. I cannot reach the host except on the explicitly defined policy, even with ping; however, ping still discloses the presence of this host:

I'd usually also say that bidirectional policies are mostly a trap because there is seldom a need for the target to contact back, only exceptions are when you want to build a full mesh between nodes.

Finally, changing the existing routes to one way policies as you hinted at and disabling the "doom" rule for now, ~~still allows that ping connection (will be checking other access methods soon).~~ (see posts below for correction). We do have a use case for these nodes to have bidirectional communications though, which is why we initially had it as such.

I will be testing other access methods besides just ping shortly to verify whether its "ALL" traffic or only ping traffic.

@carefreecaribou commented on GitHub (Oct 10, 2025): > [@carefreecaribou](https://github.com/carefreecaribou) what is the group membership of the peers? @lixmal Both peers during testing are a part of the same group "Tester Group" and the default "All" group: <img width="1355" height="249" alt="Image" src="https://github.com/user-attachments/assets/02b3ad87-916b-46d4-9860-2fa5c58ebe77" /> For testing each user in this group gets access to two other groups "VPN" and "INT". For the initial testing, bidirectional access policies from "Tester" to each of these other two groups were created (But tested with one way policies later on in this post). The VPN group gives you access to network routes. Each "VPN" node is on a certain exit route and is of the type routing Peers. When we disable each of these exit routes, pings are still possible to the peers within my same group. There are currently no other rules affecting INT or any online peers in this group to affect meshing. <img width="1815" height="688" alt="Image" src="https://github.com/user-attachments/assets/d8d9f778-cfab-41a2-9a02-078abb021308" /> > If you check with the new dashboard and select one of your peers it should show you which other peers it is connected to by which policies. We cannot reproduce this with our setups. <img width="1183" height="1275" alt="Image" src="https://github.com/user-attachments/assets/cd8cbc5d-f786-4f00-aeb2-00ff9f1b75e1" /> @Blackclaws The peers within the same group are not showing up as an accessible peer > I think ping could also be a somewhat special case, I'd have to check but you shouldn't even be peering with those from your own group unless there was an access policy governing that _or_ the node was also part of one of the other groups that you have access to. When we create an explicit one way policy between users within the same group allowing only doom on udp. <img width="916" height="68" alt="Image" src="https://github.com/user-attachments/assets/d36ae88e-dbb2-4f47-a37d-ddb3a423c1b9" /> <img width="1957" height="71" alt="Image" src="https://github.com/user-attachments/assets/43d83f14-b304-467b-b53f-2af82ac1a4f9" /> Connections are restricted as expected. I cannot reach the host except on the explicitly defined policy, even with ping; however, ping still discloses the presence of this host: <img width="593" height="295" alt="Image" src="https://github.com/user-attachments/assets/df605978-bcc6-48d6-9779-2210adee9a72" /> >I'd usually also say that bidirectional policies are mostly a trap because there is seldom a need for the target to contact back, only exceptions are when you want to build a full mesh between nodes. Finally, changing the existing routes to one way policies as you hinted at and disabling the "doom" rule for now, ~~still allows that ping connection (will be checking other access methods soon).~~ (see posts below for correction). We do have a use case for these nodes to have bidirectional communications though, which is why we initially had it as such. <img width="1163" height="1093" alt="Image" src="https://github.com/user-attachments/assets/138c8369-c2da-4697-9b4f-ba6d4ebc97f9" /> I will be testing other access methods besides just ping shortly to verify whether its "ALL" traffic or only ping traffic.

saavagebueno commented

2026-08-05 01:23:52 -04:00

@carefreecaribou commented on GitHub (Oct 10, 2025):

@Blackclaws

I'd usually also say that bidirectional policies are mostly a trap because there is seldom a need for the target to contact back, only exceptions are when you want to build a full mesh between nodes.

You might be right here. I failed to relaunch my netbird client after attempting one way traffic policies only. After changing the VPN policy to one way, and rebringing netbird down/up, I can no longer seem to access the peers. I will try to look into this further, but it now seems that testers within a group can reach one another if there is a bidirectional policy in place to routing peers /exit nodes.

This issue is only caused when using a bidirectional (or two unidirectional policies) to a Routing Peer Exit node and not bidirectional policies to other groups that are not exit nodes. Here is a trace route showing my connection to the second node is going through an exit node (Routing Peer) we had configured.

The routing peer functions as the exit node for the Internet traffic. Once configured, it automatically handles traffic it receives from connected peers, applying masquerading to ensure traffic appears to originate from the routing peer's public IP address.

Acting as a router seems to make Routing Peers ignore not-explicitly defined access control policies if some other limiting policy does not exist for peers within a group.

So
GroupA <-> Exit(routing Peer)

Will allow GroupA->Exit(routing Peer)->GroupA
for all traffic without the default rule unless a specific policy exists for GroupA->GroupA

@carefreecaribou commented on GitHub (Oct 10, 2025): @Blackclaws > I'd usually also say that bidirectional policies are mostly a trap because there is seldom a need for the target to contact back, only exceptions are when you want to build a full mesh between nodes. You might be right here. I failed to relaunch my netbird client after attempting one way traffic policies only. After changing the VPN policy to one way, and rebringing netbird down/up, I can no longer seem to access the peers. I will try to look into this further, but it now seems that testers within a group can reach one another if there is a bidirectional policy in place to routing peers /exit nodes. This issue is only caused when using a bidirectional (or two unidirectional policies) to a Routing Peer Exit node and not bidirectional policies to other groups that are not exit nodes. Here is a trace route showing my connection to the second node is going through an exit node (Routing Peer) we had configured. <img width="567" height="73" alt="Image" src="https://github.com/user-attachments/assets/255a3e9a-bcb2-45a0-9047-7e9ccf362830" /> > The routing peer functions as the exit node for the Internet traffic. Once configured, it automatically handles traffic it receives from connected peers, applying masquerading to ensure traffic appears to originate from the routing peer's public IP address. Acting as a router seems to make Routing Peers ignore not-explicitly defined access control policies if some other limiting policy does not exist for peers within a group. So GroupA <-> Exit(routing Peer) Will allow GroupA->Exit(routing Peer)->GroupA for all traffic without the default rule unless a specific policy exists for GroupA->GroupA

saavagebueno commented

2026-08-05 01:23:52 -04:00

@carefreecaribou commented on GitHub (Oct 10, 2025):

For now, I don't think this is a bug, rather just unexpected behavior caused by the routing function of the routing peers.
We were intending on having outside traffic being able to communicate with nodes in this test group (the second direction) and were not expecting the test group intra-communication to succeed due to the routing peer directing the traffic back since we did not explicitly allow a test->test policy. It could be good to list this on the Exit Node/Routing Peer documentation if that's the case. Creating an explicit intra-peer rule restricting everything (but a single port such as our doom rule above) restricts this routing unless its the explicitly allowed traffic, but still discloses the presence of the host due to the differing returned responses.

I would expect this traffic to be blocked since it's not explicitly allowed in the access control policy (with the "default" rule removed). Routing peers should respect access control policies and not facilitate intra- and inter-network communications solely based on their own connectivity—an explicit rule should be required to allow traffic within and between the networks.

Feel free to close this if you also believe this is bug, but part of the Exit Node/Routing peer mesh design. Still might be useful to have a note about this either on the Exit Node/Routing Peer page, or within the Access control Page about bidirectional policies and routing peers.

@carefreecaribou commented on GitHub (Oct 10, 2025): For now, I don't think this is a bug, rather just unexpected behavior caused by the routing function of the routing peers. We were intending on having outside traffic being able to communicate with nodes in this test group (the second direction) and were not expecting the test group intra-communication to succeed due to the routing peer directing the traffic back since we did not explicitly allow a test->test policy. It could be good to list this on the Exit Node/Routing Peer documentation if that's the case. Creating an explicit intra-peer rule restricting everything (but a single port such as our doom rule above) restricts this routing unless its the explicitly allowed traffic, but still discloses the presence of the host due to the differing returned responses. I would expect this traffic to be blocked since it's not explicitly allowed in the access control policy (with the "default" rule removed). Routing peers should respect access control policies and not facilitate intra- and inter-network communications solely based on their own connectivity—an explicit rule should be required to allow traffic within and between the networks. Feel free to close this if you also believe this is bug, but part of the Exit Node/Routing peer mesh design. Still might be useful to have a note about this either on the Exit Node/Routing Peer page, or within the Access control Page about bidirectional policies and routing peers.

Sign in to join this conversation.

Branches Tags

main

add-management-ent-dashboard

fix/migrate-enterprise-ghcr-image

disambiguate_p2p_metrics

embedded-vnc

feat-post_quantum_ml_kem

mdm_integration

affected-peer-jwt-sync

debug-ui-memprofile-lazy-windows

refactor/ui-lazy-windows

add-atomic-cache-ops

debug-ui-memprofile

feat/agent-network-per-account-serving

fix_wg_watcher_cleanup

fix/wails-go-vendor

relay_transport_down_no_offer_storm

revert/component-types

wins_nrpt_dns_delegation

dependabot/github_actions/actions-a940c7c866

fix/quickstart-subnet-and-domain-alias

notification-localization

ssh-settings-elevation

refactor/peer-event-bus

fix/relay-proxy-redirect-when-ice-active

claude/agent-network-test-cases-p743vw

android/gui-integration

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/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

revert/component-types-hookup

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

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

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

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