[GH-ISSUE #4476] Traffic diverting to Relay and intermittent service #8730

New Issue

saavagebueno · 2026-08-05T01:19:19-04:00

saavagebueno commented

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

Originally created by @Josefellype on GitHub (Sep 10, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4476

Scenario

BRIDGE-TO-MGMT
- Router whose backbone routes are behind it, with Netbird running
- Netbird IP: 10.255.255.32
- Agent version: 0.56.1
Zabbix Proxy
- Container with Netbird running
- Netbird IP: 10.255.255.151
- Agent version: 0.55.1
Backbone networks
- 100.76.0.0/16
- 172.16.0.0/12
Zabbix Server address: 100.76.180.207

Objective

Make the host 10.255.255.151 (Zabbix proxy) communicate with all backbone addresses, not just 100.76.0.0/16, including 172.16.0.0/12 and other networks reachable via routing performed by 10.255.255.32.

Example of expected behavior (direct traceroute via BRIDGE-TO-MGMT):

Source: 10.255.255.151

root@b27850a60f04:/var/lib/zabbix# traceroute 100.76.180.207
traceroute to 100.76.180.207 (100.76.180.207), 30 hops max, 60 byte packets
1  [bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br](http://bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br) (10.255.255.32)  0.621 ms  0.607 ms  0.596 ms
2  100.76.180.207 (100.76.180.207)  4.323 ms  4.331 ms  4.334 ms

The goal is for the traffic to go from 10.255.255.151 to 10.255.255.32 over the point-to-point WireGuard connection and then be routed to 100.76.180.207, which is behind 10.255.255.32. As shown in the documentation:

Observed issue

When using the network route 100.76.0.0/16 on the BRIDGE-TO-MGMT peer, the expected behavior described in the objective does not hold; at several moments the traffic goes through the Relay Server.

Creating the 100.76.0.0/16 network route

Traceroute after the change:

root@b27850a60f04:/var/lib/zabbix# traceroute 100.76.180.207
traceroute to 100.76.180.207 (100.76.180.207), 30 hops max, 60 byte packets
1  [bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br](http://bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br) (10.255.255.32)  87.933 ms  89.622 ms  89.954 ms
2  100.76.180.207 (100.76.180.207)  94.145 ms  94.165 ms  94.150 ms

Note: there is no Relay Server address that appears in the traceroutes; latency is the evidence that makes it clear the traffic is going through the Relay Server. The source and destination hosts are within the same ISP, which is why in the earlier traceroute (from the objective) the latency to the destination is 4 ms.

Test with a more specific route for 100.76.180.207

With 100.76.180.207/32: objective achieved
Smallest prefix that worked stably: 100.76.180.192/27
With /26 the problem occurs again

Traceroute after using 100.76.180.192/27:

root@b27850a60f04:/var/lib/zabbix# traceroute 100.76.180.207
traceroute to 100.76.180.207 (100.76.180.207), 30 hops max, 60 byte packets
1  [bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br](http://bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br) (10.255.255.32)  0.626 ms  0.617 ms  0.596 ms
2  100.76.180.207 (100.76.180.207)  4.215 ms  4.200 ms  4.113 ms

Access to other backbone networks (172.16.0.0/12)

The Zabbix proxy also needs to access networks in the 172.16.0.0/12 block. The same problem occurs when a broad route is used.

Test with 172.16.0.0/12

Applied configuration: network 172.16.0.0/12

Traceroute after the configuration:

root@b27850a60f04:/var/lib/zabbix# traceroute 172.16.243.254
traceroute to 172.16.243.254 (172.16.243.254), 30 hops max, 60 byte packets
1  [bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br](http://bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br) (10.255.255.32)  81.935 ms  81.946 ms  81.958 ms
2  100.76.180.193 (100.76.180.193)  82.288 ms  82.286 ms  82.275 ms
3  100.76.1.5 (100.76.1.5)  83.032 ms  83.415 ms  103.106 ms
4  100.76.4.6 (100.76.4.6)  154.128 ms  154.134 ms  154.122 ms
5  172.16.4.30 (172.16.4.30)  124.695 ms 100.76.4.14 (100.76.4.14)  127.622 ms  127.751 ms
6  172.17.14.10 (172.17.14.10)  127.130 ms  85.272 ms  86.105 ms
7  172.17.24.10 (172.17.24.10)  87.614 ms  87.822 ms  87.415 ms
8  100.75.24.49 (100.75.24.49)  88.615 ms  88.013 ms  88.537 ms
9  100.75.24.78 (100.75.24.78)  88.613 ms  89.099 ms  89.211 ms
10  100.75.89.6 (100.75.89.6)  90.430 ms  91.390 ms  90.981 ms
11  100.75.90.14 (100.75.90.14)  96.894 ms  96.888 ms  96.863 ms
12  100.75.90.6 (100.75.90.6)  92.232 ms  92.015 ms  92.197 ms
13  * * *
14  172.16.243.254 (172.16.243.254)  93.251 ms  93.119 ms  92.606 ms

Attempts with prefixes for 172.16.243.254 (unsuccessful)

172.16.243.0/24
172.16.243.192/26
172.16.243.224/27
172.16.243.254/32

Target change: 172.16.9.78

A few minutes earlier, a network for 172.16.9.78/32 had been created and the traceroute came out as expected. The rule was then disabled to test a less specific prefix.

Traceroute with 172.16.9.78/32 (OK result):

root@b27850a60f04:/var/lib/zabbix# traceroute 172.16.9.78
traceroute to 172.16.9.78 (172.16.9.78), 30 hops max, 60 byte packets
1  [bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br](http://bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br) (10.255.255.32)  0.525 ms  0.494 ms  0.504 ms
2  100.76.180.193 (100.76.180.193)  0.660 ms  0.634 ms  0.710 ms
3  172.16.9.78 (172.16.9.78)  0.895 ms  0.951 ms  0.965 ms

Attempt with 172.16.9.0/24:

root@b27850a60f04:/var/lib/zabbix# traceroute 172.16.9.78
traceroute to 172.16.9.78 (172.16.9.78), 30 hops max, 60 byte packets
1  [bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br](http://bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br) (10.255.255.32)  81.460 ms  83.221 ms  83.236 ms
2  100.76.180.193 (100.76.180.193)  93.814 ms  93.817 ms  93.809 ms
3  172.16.9.78 (172.16.9.78)  93.838 ms  93.834 ms  93.826 ms

Upon reverting to 172.16.9.78/32 and restarting the Netbird service on the Zabbix proxy, the traffic started going through the Relay Server:

The same happens with 100.76.180.207 even with 100.76.180.207/32, the packets go through the Relay Server:

Another demonstration of intermittency:

The only change made was the addition of the 100.76.0.0/17 network right before bringing the Netbird service down and up again, which would explain the change in traceroute behavior for 100.76.4.255, but not for the remaining addresses.

Summary of behavior

Very specific prefixes (/32 and, in one case, /27) tend to work initially.
With less specific prefixes (/26, /16, /12), traffic often detours via the Relay Server.
There is intermittency: the same specific prefix can change behavior after route changes, even if the configuration returns to the initial pre-change state.

Originally created by @Josefellype on GitHub (Sep 10, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4476 ## Scenario - BRIDGE-TO-MGMT - Router whose backbone routes are behind it, with Netbird running - Netbird IP: 10.255.255.32 - Agent version: 0.56.1 - Zabbix Proxy - Container with Netbird running - Netbird IP: 10.255.255.151 - Agent version: 0.55.1 - Backbone networks - 100.76.0.0/16 - 172.16.0.0/12 - Zabbix Server address: 100.76.180.207 ## Objective Make the host 10.255.255.151 (Zabbix proxy) communicate with all backbone addresses, not just 100.76.0.0/16, including 172.16.0.0/12 and other networks reachable via routing performed by 10.255.255.32. Example of expected behavior (direct traceroute via BRIDGE-TO-MGMT): Source: 10.255.255.151 ```bash root@b27850a60f04:/var/lib/zabbix# traceroute 100.76.180.207 traceroute to 100.76.180.207 (100.76.180.207), 30 hops max, 60 byte packets 1 [bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br](http://bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br) (10.255.255.32) 0.621 ms 0.607 ms 0.596 ms 2 100.76.180.207 (100.76.180.207) 4.323 ms 4.331 ms 4.334 ms ``` The goal is for the traffic to go from 10.255.255.151 to 10.255.255.32 over the point-to-point WireGuard connection and then be routed to 100.76.180.207, which is behind 10.255.255.32. As shown in the documentation: <img width="775" height="453" alt="Image" src="https://github.com/user-attachments/assets/38561d4f-7664-463a-8431-50fe31c436ff" /> --- ## Observed issue When using the network route 100.76.0.0/16 on the BRIDGE-TO-MGMT peer, the expected behavior described in the objective does not hold; at several moments the traffic goes through the Relay Server. ### Creating the 100.76.0.0/16 network route <img width="1191" height="1043" alt="Image" src="https://github.com/user-attachments/assets/10e8a81a-f206-4474-b58b-5df74b5ee2a6" /> Traceroute after the change: ```bash root@b27850a60f04:/var/lib/zabbix# traceroute 100.76.180.207 traceroute to 100.76.180.207 (100.76.180.207), 30 hops max, 60 byte packets 1 [bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br](http://bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br) (10.255.255.32) 87.933 ms 89.622 ms 89.954 ms 2 100.76.180.207 (100.76.180.207) 94.145 ms 94.165 ms 94.150 ms ``` Note: there is no Relay Server address that appears in the traceroutes; latency is the evidence that makes it clear the traffic is going through the Relay Server. The source and destination hosts are within the same ISP, which is why in the earlier traceroute (from the objective) the latency to the destination is 4 ms. ### Test with a more specific route for 100.76.180.207 - With 100.76.180.207/32: objective achieved - Smallest prefix that worked stably: 100.76.180.192/27 - With /26 the problem occurs again <img width="1271" height="907" alt="Image" src="https://github.com/user-attachments/assets/e4e7f6db-1d7a-44a0-af9f-c908fc43204d" /> Traceroute after using 100.76.180.192/27: ```bash root@b27850a60f04:/var/lib/zabbix# traceroute 100.76.180.207 traceroute to 100.76.180.207 (100.76.180.207), 30 hops max, 60 byte packets 1 [bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br](http://bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br) (10.255.255.32) 0.626 ms 0.617 ms 0.596 ms 2 100.76.180.207 (100.76.180.207) 4.215 ms 4.200 ms 4.113 ms ``` --- ## Access to other backbone networks (172.16.0.0/12) The Zabbix proxy also needs to access networks in the 172.16.0.0/12 block. The same problem occurs when a broad route is used. ### Test with 172.16.0.0/12 Applied configuration: network 172.16.0.0/12 <img width="1188" height="1083" alt="Image" src="https://github.com/user-attachments/assets/d8cfa3dc-586d-4d4a-8220-64e3e3dc49a9" /> Traceroute after the configuration: ```bash root@b27850a60f04:/var/lib/zabbix# traceroute 172.16.243.254 traceroute to 172.16.243.254 (172.16.243.254), 30 hops max, 60 byte packets 1 [bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br](http://bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br) (10.255.255.32) 81.935 ms 81.946 ms 81.958 ms 2 100.76.180.193 (100.76.180.193) 82.288 ms 82.286 ms 82.275 ms 3 100.76.1.5 (100.76.1.5) 83.032 ms 83.415 ms 103.106 ms 4 100.76.4.6 (100.76.4.6) 154.128 ms 154.134 ms 154.122 ms 5 172.16.4.30 (172.16.4.30) 124.695 ms 100.76.4.14 (100.76.4.14) 127.622 ms 127.751 ms 6 172.17.14.10 (172.17.14.10) 127.130 ms 85.272 ms 86.105 ms 7 172.17.24.10 (172.17.24.10) 87.614 ms 87.822 ms 87.415 ms 8 100.75.24.49 (100.75.24.49) 88.615 ms 88.013 ms 88.537 ms 9 100.75.24.78 (100.75.24.78) 88.613 ms 89.099 ms 89.211 ms 10 100.75.89.6 (100.75.89.6) 90.430 ms 91.390 ms 90.981 ms 11 100.75.90.14 (100.75.90.14) 96.894 ms 96.888 ms 96.863 ms 12 100.75.90.6 (100.75.90.6) 92.232 ms 92.015 ms 92.197 ms 13 * * * 14 172.16.243.254 (172.16.243.254) 93.251 ms 93.119 ms 92.606 ms ``` ### Attempts with prefixes for 172.16.243.254 (unsuccessful) - 172.16.243.0/24 <img width="853" height="717" alt="Image" src="https://github.com/user-attachments/assets/42507ddb-86a6-45c4-adce-f939c42dbbb8" /> - 172.16.243.192/26 <img width="851" height="717" alt="Image" src="https://github.com/user-attachments/assets/2bd102d2-fab9-4643-824c-180fe0f0b1ba" /> - 172.16.243.224/27 <img width="854" height="715" alt="Image" src="https://github.com/user-attachments/assets/6b960076-8cee-47c7-8fe7-9d58c658bf06" /> - 172.16.243.254/32 <img width="853" height="716" alt="Image" src="https://github.com/user-attachments/assets/d2f6bc36-a8ee-4f8e-b0a2-01f7620231b2" /> --- ## Target change: 172.16.9.78 A few minutes earlier, a network for 172.16.9.78/32 had been created and the traceroute came out as expected. The rule was then disabled to test a less specific prefix. Traceroute with 172.16.9.78/32 (OK result): ```bash root@b27850a60f04:/var/lib/zabbix# traceroute 172.16.9.78 traceroute to 172.16.9.78 (172.16.9.78), 30 hops max, 60 byte packets 1 [bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br](http://bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br) (10.255.255.32) 0.525 ms 0.494 ms 0.504 ms 2 100.76.180.193 (100.76.180.193) 0.660 ms 0.634 ms 0.710 ms 3 172.16.9.78 (172.16.9.78) 0.895 ms 0.951 ms 0.965 ms ``` Attempt with 172.16.9.0/24: ```bash root@b27850a60f04:/var/lib/zabbix# traceroute 172.16.9.78 traceroute to 172.16.9.78 (172.16.9.78), 30 hops max, 60 byte packets 1 [bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br](http://bridge-to-mgmt-cli-stda-via-linux.vpnnetbird.nortenettelecom.net.br) (10.255.255.32) 81.460 ms 83.221 ms 83.236 ms 2 100.76.180.193 (100.76.180.193) 93.814 ms 93.817 ms 93.809 ms 3 172.16.9.78 (172.16.9.78) 93.838 ms 93.834 ms 93.826 ms ``` Upon reverting to 172.16.9.78/32 and restarting the Netbird service on the Zabbix proxy, the traffic started going through the Relay Server: <img width="849" height="459" alt="Image" src="https://github.com/user-attachments/assets/9951817a-559a-4451-b53f-bebf9b86edc6" /> The same happens with 100.76.180.207 even with 100.76.180.207/32, the packets go through the Relay Server: <img width="849" height="445" alt="Image" src="https://github.com/user-attachments/assets/b1c166e9-4656-490b-a28c-8a8178432584" /> Another demonstration of intermittency: <img width="758" height="866" alt="Image" src="https://github.com/user-attachments/assets/586db098-4548-42c7-8394-d5da5c08081b" /> The only change made was the addition of the 100.76.0.0/17 network right before bringing the Netbird service down and up again, which would explain the change in traceroute behavior for 100.76.4.255, but not for the remaining addresses. --- ## Summary of behavior - Very specific prefixes (/32 and, in one case, /27) tend to work initially. - With less specific prefixes (/26, /16, /12), traffic often detours via the Relay Server. - There is intermittency: the same specific prefix can change behavior after route changes, even if the configuration returns to the initial pre-change state. ---

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

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