[GH-ISSUE #4079] Open 'discussions tab' #8481

New Issue

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

saavagebueno commented

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

Originally created by @sandstrom on GitHub (Jul 1, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4079

I'd suggest enabling the 'discussions' tab on this repo (Github feature).

There is a built-in button in Github issues, where you can 1-click to move an issue into discussions.

For everything that isn't a bug report or request, like a question, just move them to discussions. For example this one: https://github.com/netbirdio/netbird/issues/4035

I'd also move everything that's an uncomplete bug report, for example no steps to reproduce or decent explanation of the issue.

You don't have to ever check the discussions, just treat it as a forum and dumping group. Anything that's a big problem will accrue many comments, so you can check discussion topics with say >20 comments.

You could probably clean out 30-50% of issues this way.

Originally created by @sandstrom on GitHub (Jul 1, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4079 I'd suggest enabling the 'discussions' tab on this repo (Github feature). There is a built-in button in Github issues, where you can 1-click to move an issue into discussions. For everything that isn't a bug report or request, like a question, just move them to discussions. For example this one: https://github.com/netbirdio/netbird/issues/4035 I'd also move everything that's an uncomplete bug report, for example no steps to reproduce or decent explanation of the issue. You don't have to ever check the discussions, just treat it as a forum and dumping group. Anything that's a big problem will accrue many comments, so you can check discussion topics with say >20 comments. You could probably clean out 30-50% of issues this way.

saavagebueno added the feature-request community labels 2026-08-05 01:18:12 -04:00

saavagebueno commented

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

@HammyHavoc commented on GitHub (Jul 3, 2025):

Yes, this is desperately needed and would hugely improve the signal-to-noise ratio.

@HammyHavoc commented on GitHub (Jul 3, 2025): Yes, this is desperately needed and would hugely improve the signal-to-noise ratio.

saavagebueno commented

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

@mlsmaycon commented on GitHub (Jul 3, 2025):

Hey folks, we just launched the https://forum.netbird.io to help with that. What do you guys think?

@mlsmaycon commented on GitHub (Jul 3, 2025): Hey folks, we just launched the https://forum.netbird.io to help with that. What do you guys think?

saavagebueno commented

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

@sandstrom commented on GitHub (Jul 3, 2025):

@mlsmaycon Should work, just close issues with a 'saved reply' on Github saying something like "Sorry, this is a question and not an actionable bug, please ask on our community forum instead …"

EDIT: (I also agree with what Hammy wrote below, was about to add something along those lines)

@sandstrom commented on GitHub (Jul 3, 2025): @mlsmaycon Should work, just close issues with a 'saved reply' on Github saying something like "Sorry, this is a question and not an actionable bug, please ask on our community forum instead …" EDIT: (I also agree with what Hammy wrote below, was about to add something along those lines)

saavagebueno commented

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

@HammyHavoc commented on GitHub (Jul 3, 2025):

Hey folks, we just launched the https://forum.netbird.io to help with that. What do you guys think?

Registered on it! Discourse is a great choice for a forum. :- )

Re this issue, I do think @sandstrom has a valid point about being able to one-click an issue into a discussion, that's a nice feature to have. Likewise, I do think that having a proper discussion system on the Git repo itself will go a long way to reducing workload in that regard long-term as it's an expectation that it'll be available.

If it were up to me, I'd have both as I feel both are equally valid and important for different reasons, particularly that GitHub discussions are not a part of the Git repository itself that I am aware of (i.e., what you clone to your local machine), so if Microsoft/GitHub ever canned the feature or started billing for use over x then it might be nice to also have the forum to fall back on as well. The danger of this kind of feature along with Discord-based communities is the potential for sudden major knowledge loss at the whim of a third-party.

I also think you'll get a different demographic audience-wise with who is likely to be lurking the discussions on GitHub (i.e., people who do or can contribute to the dev itself), and that's a demographic worth fostering directly on the repo as context-switching to separate forums can be grating at times.

https://meta.discourse.org/t/discourse-github/99895 may offer some value to tie Discourse and GitHub together.

@HammyHavoc commented on GitHub (Jul 3, 2025): > Hey folks, we just launched the https://forum.netbird.io to help with that. What do you guys think? Registered on it! Discourse is a great choice for a forum. :- ) Re this issue, I do think @sandstrom has a valid point about being able to one-click an `issue` into a `discussion`, that's a nice feature to have. Likewise, I do think that having a proper discussion system on the Git repo itself will go a long way to reducing workload in that regard long-term as it's an expectation that it'll be available. If it were up to me, I'd have both as I feel both are equally valid and important for different reasons, particularly that GitHub discussions are not a part of the Git repository itself that I am aware of (i.e., what you clone to your local machine), so if Microsoft/GitHub ever canned the feature or started billing for use over `x` then it might be nice to also have the forum to fall back on as well. The danger of this kind of feature along with Discord-based communities is the potential for sudden major knowledge loss at the whim of a third-party. I also think you'll get a different demographic audience-wise with who is likely to be lurking the discussions on GitHub (i.e., people who do or can contribute to the dev itself), and that's a demographic worth fostering directly on the repo as context-switching to separate forums can be grating at times. https://meta.discourse.org/t/discourse-github/99895 may offer some value to tie Discourse and GitHub together.

saavagebueno commented

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

@Xeravax commented on GitHub (Jul 7, 2025):

Hi, I'm the administrator with the forum at this moment. We have that plugin installed, but I'm still checking how it syncs across. As I can see, it tells people to check the forum if any issue is mentioned in there. Rather then syncing it 2way.

@Xeravax commented on GitHub (Jul 7, 2025): Hi, I'm the administrator with the forum at this moment. We have that plugin installed, but I'm still checking how it syncs across. As I can see, it tells people to check the forum if any issue is mentioned in there. Rather then syncing it 2way. ![Image](https://github.com/user-attachments/assets/6788fbe7-d720-4e99-817f-f4d0fa24be4c)

saavagebueno commented

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

@HammyHavoc commented on GitHub (Jul 7, 2025):

Hi, I'm the administrator with the forum at this moment. We have that plugin installed, but I'm still checking how it syncs across. As I can see, it tells people to check the forum if any issue is mentioned in there. Rather then syncing it 2way.

One-way better than no-way, I suppose. If someone figured out bidirectional sync then that would be really very cool.

@HammyHavoc commented on GitHub (Jul 7, 2025): > Hi, I'm the administrator with the forum at this moment. We have that plugin installed, but I'm still checking how it syncs across. As I can see, it tells people to check the forum if any issue is mentioned in there. Rather then syncing it 2way. > > ![Image](https://github.com/user-attachments/assets/6788fbe7-d720-4e99-817f-f4d0fa24be4c) One-way better than no-way, I suppose. If someone figured out bidirectional sync then that would be really very cool.

saavagebueno commented

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

@cameronj86 commented on GitHub (Jul 15, 2025):

Currently the only options available require that you tie your netbird forum account to one of the (popular) 3rd party options, which seems counter to many people's main use for VPNs.

Can it be configured to sign up w/ just plain email?

@cameronj86 commented on GitHub (Jul 15, 2025): Currently the only options available require that you tie your netbird forum account to one of the (popular) 3rd party options, which seems counter to many people's main use for VPNs. Can it be configured to sign up w/ just plain email?

saavagebueno commented

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

@HammyHavoc commented on GitHub (Jul 15, 2025):

Currently the only options available require that you tie your netbird forum account to one of the (popular) 3rd party options, which seems counter to many people's main use for VPNs.

Can it be configured to sign up w/ just plain email?

I get the impression you're confused about threat models.

The main appeal of NetBird is the tunnel capabilities. If someone just wants a privacy-preserving or anonymous way of using the net, there's plenty of options.

@HammyHavoc commented on GitHub (Jul 15, 2025): > Currently the only options available require that you tie your netbird forum account to one of the (popular) 3rd party options, which seems counter to many people's main use for VPNs. > > Can it be configured to sign up w/ just plain email? I get the impression you're confused about threat models. The main appeal of NetBird is the tunnel capabilities. If someone just wants a privacy-preserving or anonymous way of using the net, there's plenty of options.

saavagebueno commented

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

@Xeravax commented on GitHub (Jul 16, 2025):

Currently the only options available require that you tie your netbird forum account to one of the (popular) 3rd party options, which seems counter to many people's main use for VPNs.

Can it be configured to sign up w/ just plain email?

I discussed this with NetBird staff, however they want to avoid storing passwords/email addresses on the forum. Maybe in the future when it's more established. But can't make that promise yet at the moment. If you have an alternative option, or want additional login methods. Do tell me, and I'll see what I can do.

(Keep in mind GitHub is availible as a login option. Considering almost everyone will have an GitHub account).

@Xeravax commented on GitHub (Jul 16, 2025): > Currently the only options available require that you tie your netbird forum account to one of the (popular) 3rd party options, which seems counter to many people's main use for VPNs. > > Can it be configured to sign up w/ just plain email? I discussed this with NetBird staff, however they want to avoid storing passwords/email addresses on the forum. Maybe in the future when it's more established. But can't make that promise yet at the moment. If you have an alternative option, or want additional login methods. Do tell me, and I'll see what I can do. (Keep in mind GitHub **is availible as a login option**. Considering almost everyone will have an GitHub account).

saavagebueno commented

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

@cameronj86 commented on GitHub (Jul 16, 2025):

I get the impression you're confused about threat models.
The main appeal of NetBird is the tunnel capabilities. If someone just wants a privacy-preserving or anonymous way of using the net, there's plenty of options.

Privacy and mesh VPNs are not mutually exclusive. I am currently using Tailscale but due to zero-trust/excessive logging, I am switching to self-hosting netbird for its mesh VPN. The goal is to access my LAN w/o opening any ports, and also, hosting netbird on a VPS, as an exit node to obfuscate my traffic from my ISP.

My overarching goal is to minimize interactions w/ companies whose main (sole?) business model is harvesting my user data for profit, especially for something as innocuous as asking a question on a forum. All of the current log-in options do this, altho after browsing the privacy policy, I am now under the impression that netbird does it as well to varying degrees, so I can understand the pushback.

If you have an alternative option, or want additional login methods.

Codeberg would be ideal, since they are a NFP and do not sell data for a living. If that's not possible, then basically any company whose business model doesn't revolve around harvesting user data for profit.

@cameronj86 commented on GitHub (Jul 16, 2025): > I get the impression you're confused about threat models. The main appeal of NetBird is the tunnel capabilities. If someone just wants a privacy-preserving or anonymous way of using the net, there's plenty of options. Privacy and mesh VPNs are not mutually exclusive. I am currently using Tailscale but due to zero-trust/excessive logging, I am switching to self-hosting netbird for its mesh VPN. The goal is to access my LAN w/o opening any ports, and also, hosting netbird on a VPS, as an exit node to obfuscate my traffic from my ISP. My overarching goal is to minimize interactions w/ companies whose main (sole?) business model is harvesting my user data for profit, especially for something as innocuous as asking a question on a forum. All of the current log-in options do this, altho after browsing the [privacy policy](https://netbird.io/privacy), I am now under the impression that netbird does it as well to varying degrees, so I can understand the pushback. > If you have an alternative option, or want additional login methods. Codeberg would be ideal, since they are a NFP and do not sell data for a living. If that's not possible, then basically _any_ company whose business model doesn't revolve around harvesting user data for profit.

saavagebueno commented

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

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

Privacy is a very blurred line:

you are right that you could improve it, by using a machine running in another location/country as an Exit Node to:
- hide your real IP address
- prevent your ISP from snooping on (most) of your traffic
still Wireguard protocol does not have a goal of concealing it's presence, so it's relatively easy to identify and block such traffic, even if there is no way to read what was sent
still NetBird is not (currently at least) designed to act as an always-on-VPN to actively intercept and prevent internet traffic leaking outside of it/before it starts up.

You should be fine running NetBird for your purpose as long as you accept that some of the traffic will leak around it and that ISP can block it (I very much doubt it, but it can happen).

@nazarewk commented on GitHub (Jul 17, 2025): Privacy is a very blurred line: - you are right that you could improve it, by using a machine running in another location/country as an Exit Node to: - hide your real IP address - prevent your ISP from snooping on (most) of your traffic - still Wireguard protocol does not have a goal of concealing it's presence, so it's relatively easy to identify and block such traffic, even if there is no way to read what was sent - still NetBird is not (currently at least) designed to act as an always-on-VPN to actively intercept and prevent internet traffic leaking outside of it/before it starts up. You should be fine running NetBird for your purpose as long as you accept that some of the traffic will leak around it and that ISP can block it (I very much doubt it, but it can happen).

saavagebueno commented

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

@mlsmaycon commented on GitHub (Jul 22, 2025):

Hello @cameronj86, we will check the integration with Codeberg. In general, we don't want to store anyone's password, and using OIDC logins will be the preferred way.

We offer lots of options, including Github, and we will add more if they become available.

@mlsmaycon commented on GitHub (Jul 22, 2025): Hello @cameronj86, we will check the integration with Codeberg. In general, we don't want to store anyone's password, and using OIDC logins will be the preferred way. We offer lots of options, including Github, and we will add more if they become available.

Sign in to join this conversation.

Branches Tags

main

fix/wails-go-vendor

fix/update-wails-fork-ref

add-atomic-cache-ops

feat/agent-network-per-account-serving

feat-post_quantum_ml_kem

revert/component-types

wins_nrpt_dns_delegation

embedded-vnc

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

disambiguate_p2p_metrics

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

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

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