[GH-ISSUE #4879] Feature Request: Tunnel-aware relay/transport mode to Netbird #9485

New Issue

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

saavagebueno commented

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

Originally created by @YourSandwich on GitHub (Nov 30, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4879

Summary

I want to run Netbird traffic through existing HTTPS/WebSocket tunnels and reverse-proxy style setups (for example via a trusted IP/hostname exposed by Tailscale Funnel or Cloudflare Tunnel). The idea is that Netbird’s tunnel packets should be relayable via a single entrypoint.

Right now I can approximate this using a complex combination of wstunnel, TProxy, nftables and custom routing. I’d like a much simpler, officially supported way to either:

Use a simple WG-style local UDP frontend that I can tunnel through tools like wstunnel / Tailscale Funnel / Cloudflare Tunnel, or
Allow native WireGuard clients to connect directly to netbird-manager, so Netbird can handle routing/peering while I reuse my existing WG-over-HTTPS/WebSocket setups.

Current working solution with WireGuard + wstunnel

For WireGuard I use wstunnel like this:

ExecStart=/usr/bin/wstunnel client \
  --http-headers-file /etc/wstunnel/headers \
  --connection-retry-max-backoff 120s \
  --websocket-ping-frequency 60s \
  --dns-resolver dns+https://1.1.1.1?sni=cloudflare-dns.com \
  -P v1/specialpath \
  -L udp://8080:targetvg_server:51822?timeout_sec=0 \
  -R socks5://127.0.0.1:8822 \
  wss://trustedserver:443

WireGuard config:

[connection]
id=SomeID
type=wireguard
autoconnect=false

[wireguard]
mtu=1200
private-key=xxx=

[wireguard-peer.xxx=]
endpoint=127.0.0.1:8080
preshared-key=xxxx=
preshared-key-flags=0
persistent-keepalive=20
allowed-ips=x.x.x.x/24;

[ipv4]
address1=x.x.x.x/32
gateway=x.x.x.x
method=manual

So WG just talks to 127.0.0.1:8080 over UDP; wstunnel then forwards that over WebSocket (wss://trustedserver:443).

Current workaround for Netbird + wstunnel TProxy

After a lot of pain I replicated this with Netbird using wstunnel’s TPROXY mode:

ExecStart=/usr/bin/wstunnel client \
  --http-headers-file /etc/wstunnel/headers \
  --connection-retry-max-backoff 5m \
  --websocket-ping-frequency 30s \
  --connection-min-idle 2 \
  --dns-resolver dns+https://1.1.1.1?sni=cloudflare-dns.com \
  -P v1/a9f0b1c2d3e4f5 \
  -L 'tproxy+tcp://15001' \
  -L 'tproxy+udp://15001?timeout_sec=3600' \
  wss://trustedserver:443

I run Netbird as a dedicated netbird user. Using nftables (firewalld frontend) I fwmark all traffic from that user and send it to a custom routing table.

/etc/firewalld/direct.xml:

<?xml version="1.0" encoding="utf-8"?>
<direct>
  <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="0">-o lo -j RETURN</rule>
  <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="1">-m owner --uid-owner wstunnel -j RETURN</rule>

  <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="2">-m owner --uid-owner netbird -d <netbird_iprange> -j RETURN</rule>
  <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="2">-m owner --uid-owner netbird -d 100.100.100.200/32 -j RETURN</rule>
  <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="2">-m owner --uid-owner netbird -d 169.254.169.254/32 -j RETURN</rule>
  <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="2">-m owner --uid-owner netbird -p udp --dport 53 -j RETURN</rule>
  <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="2">-m owner --uid-owner netbird -p tcp --dport 53 -j RETURN</rule>

  <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="3">-m owner --uid-owner netbird -j MARK --set-mark 0x66</rule>

  <rule ipv="ipv4" table="mangle" chain="PREROUTING" priority="0">-d <network_ip_relay> -m mark --mark 0x66 -j RETURN</rule>
  <rule ipv="ipv4" table="mangle" chain="PREROUTING" priority="0">-d 100.100.100.200/32 -m mark --mark 0x66 -j RETURN</rule>
  <rule ipv="ipv4" table="mangle" chain="PREROUTING" priority="0">-d 169.254.169.254/32 -m mark --mark 0x66 -j RETURN</rule>

  <rule ipv="ipv4" table="mangle" chain="PREROUTING" priority="1">-p udp -m mark --mark 0x66 -j TPROXY --on-port 15001 --on-ip 127.0.0.1</rule>
  <rule ipv="ipv4" table="mangle" chain="PREROUTING" priority="2">-p tcp -m mark --mark 0x66 -j TPROXY --on-port 15001 --on-ip 127.0.0.1</rule>

  <rule ipv="ipv4" table="nat" chain="POSTROUTING" priority="0">-s <network_ip_relay> -o ens192 -j MASQUERADE</rule>
  <rule ipv="ipv4" table="nat" chain="OUTPUT" priority="0">-m owner --uid-owner netbird -p udp --dport 53 -j DNAT --to-destination 1.1.1.1:53</rule>
  <rule ipv="ipv4" table="nat" chain="OUTPUT" priority="1">-m owner --uid-owner netbird -p tcp --dport 53 -j DNAT --to-destination 1.1.1.1:53</rule>
</direct>

/etc/systemd/system/wstunnel-tproxy-routing.service:

[Unit]
Description=policy routing for netbird→wstunnel
After=network.target

[Service]
Type=oneshot
ExecStart=/usr/bin/ip rule add pref 98 fwmark 0x66 lookup 101
ExecStart=/usr/bin/ip route replace local 0.0.0.0/0 dev lo table 101
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

This works but is very complex, interferes with Netbird’s own routing table, and is fragile.

Problems with the current workaround

Issues I see with this setup:

After ~6h (key exchange) Netbird loses its TProxy port mapping and fails to reconnect → needs service restart.
P2P not working because of ICE, even with UDP TProxy set.
TURN proxy not working (only rels:// works).
Every internal IP that should be relayed has to be added to nftables manually.

Proposed solutions

1. Minimal requirement: simple “WG-style” UDP frontend

I don’t need a full, deeply integrated WebSocket transport in the Netbird client.

A minimal but very useful feature would be:

Let Netbird send its tunnel traffic to a single local UDP endpoint, similar to how WG works with wstunnel:
```
-L udp://8080:targetvg_server:51822?timeout_sec=0 \
```

Concretely:

Allow configuring the Netbird client so that all WG-like traffic destined to the relay/manager goes to e.g. 127.0.0.1:8080.
A local wstunnel instance then listens on udp://127.0.0.1:8080 and forwards that over wss://trustedserver:443 to the real Netbird/relay endpoint.
From Netbird’s point of view this is just a normal UDP endpoint; all WebSocket/HTTPS magic is handled by wstunnel.
This would eliminate:
- TProxy,
- fwmarks,
- extra routing tables,
- and most of the nftables complexity on the client.

2. Alternative: allow native WireGuard clients to connect to `netbird-manager`

A different simple approach that would also solve my use case:

Allow native WireGuard clients (standard wg/wg-quick) to connect directly to netbird-manager as first-class peers.
netbird-manager would:
- Issue proper WG configs for those peers.
- Make sure Netbird clients treat those WG peers as regular Netbird peers and route traffic accordingly.

That how I could keep using the well-tested wg + wstunnel combo on restricted networks, while still leveraging Netbird’s:

control plane,
ACLs,
mesh logic.

3. Nice to have: tunnel-aware manager / obfuscation

Not strictly required, but would improve tunnel setups further:

Make netbird-manager tunnel-aware:
- When a peer is known to be behind a tunnel/WebSocket, prefer serving a local tunnel/relay address instead of public relay information.
- Avoid handing out unreachable public relay IPs to peers that can only reach each other via the tunnel.

Optionally, provide a native obfuscation / pluggable transport mode that:

Wraps Netbird traffic in something HTTP(S)/WebSocket-like.
Can be forwarded via generic tunnel providers such as Tailscale Funnel, Cloudflare Tunnel, etc.
Eliminates the need for the TProxy + nftables hacking I’m doing now.

Closing

In short, I’d already be very happy with one of these minimal options:

Netbird being able to use a simple local UDP frontend (WG-style) that I can tunnel with wstunnel, or
Allowing native WireGuard clients to connect to netbird-manager.

Everything else (tunnel-awareness / obfuscation) would be a big bonus, but these two would already make Netbird much easier and more robust to deploy on locked-down networks that require WebSocket/HTTPS tunneling.

Disclaimer: this issue (structure/formatting) was prepared with the help of an LLM.

Originally created by @YourSandwich on GitHub (Nov 30, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4879 ## Summary I want to run Netbird traffic through existing HTTPS/WebSocket tunnels and reverse-proxy style setups (for example via a trusted IP/hostname exposed by Tailscale Funnel or Cloudflare Tunnel). The idea is that Netbird’s tunnel packets should be relayable via a single entrypoint. Right now I can approximate this using a complex combination of wstunnel, TProxy, nftables and custom routing. I’d like a much simpler, officially supported way to either: * Use a **simple WG-style local UDP frontend** that I can tunnel through tools like wstunnel / Tailscale Funnel / Cloudflare Tunnel, **or** * Allow **native WireGuard clients** to connect directly to `netbird-manager`, so Netbird can handle routing/peering while I reuse my existing WG-over-HTTPS/WebSocket setups. ## Current working solution with WireGuard + wstunnel For WireGuard I use wstunnel like this: ```ini ExecStart=/usr/bin/wstunnel client \ --http-headers-file /etc/wstunnel/headers \ --connection-retry-max-backoff 120s \ --websocket-ping-frequency 60s \ --dns-resolver dns+https://1.1.1.1?sni=cloudflare-dns.com \ -P v1/specialpath \ -L udp://8080:targetvg_server:51822?timeout_sec=0 \ -R socks5://127.0.0.1:8822 \ wss://trustedserver:443 ``` WireGuard config: ```ini [connection] id=SomeID type=wireguard autoconnect=false [wireguard] mtu=1200 private-key=xxx= [wireguard-peer.xxx=] endpoint=127.0.0.1:8080 preshared-key=xxxx= preshared-key-flags=0 persistent-keepalive=20 allowed-ips=x.x.x.x/24; [ipv4] address1=x.x.x.x/32 gateway=x.x.x.x method=manual ``` So WG just talks to `127.0.0.1:8080` over UDP; wstunnel then forwards that over WebSocket (`wss://trustedserver:443`). ## Current workaround for Netbird + wstunnel TProxy After a lot of pain I replicated this with Netbird using wstunnel’s **TPROXY** mode: ```ini ExecStart=/usr/bin/wstunnel client \ --http-headers-file /etc/wstunnel/headers \ --connection-retry-max-backoff 5m \ --websocket-ping-frequency 30s \ --connection-min-idle 2 \ --dns-resolver dns+https://1.1.1.1?sni=cloudflare-dns.com \ -P v1/a9f0b1c2d3e4f5 \ -L 'tproxy+tcp://15001' \ -L 'tproxy+udp://15001?timeout_sec=3600' \ wss://trustedserver:443 ``` I run Netbird as a dedicated `netbird` user. Using nftables (firewalld frontend) I fwmark all traffic from that user and send it to a custom routing table. `/etc/firewalld/direct.xml`: ```xml <?xml version="1.0" encoding="utf-8"?> <direct> <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="0">-o lo -j RETURN</rule> <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="1">-m owner --uid-owner wstunnel -j RETURN</rule> <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="2">-m owner --uid-owner netbird -d <netbird_iprange> -j RETURN</rule> <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="2">-m owner --uid-owner netbird -d 100.100.100.200/32 -j RETURN</rule> <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="2">-m owner --uid-owner netbird -d 169.254.169.254/32 -j RETURN</rule> <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="2">-m owner --uid-owner netbird -p udp --dport 53 -j RETURN</rule> <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="2">-m owner --uid-owner netbird -p tcp --dport 53 -j RETURN</rule> <rule ipv="ipv4" table="mangle" chain="OUTPUT" priority="3">-m owner --uid-owner netbird -j MARK --set-mark 0x66</rule> <rule ipv="ipv4" table="mangle" chain="PREROUTING" priority="0">-d <network_ip_relay> -m mark --mark 0x66 -j RETURN</rule> <rule ipv="ipv4" table="mangle" chain="PREROUTING" priority="0">-d 100.100.100.200/32 -m mark --mark 0x66 -j RETURN</rule> <rule ipv="ipv4" table="mangle" chain="PREROUTING" priority="0">-d 169.254.169.254/32 -m mark --mark 0x66 -j RETURN</rule> <rule ipv="ipv4" table="mangle" chain="PREROUTING" priority="1">-p udp -m mark --mark 0x66 -j TPROXY --on-port 15001 --on-ip 127.0.0.1</rule> <rule ipv="ipv4" table="mangle" chain="PREROUTING" priority="2">-p tcp -m mark --mark 0x66 -j TPROXY --on-port 15001 --on-ip 127.0.0.1</rule> <rule ipv="ipv4" table="nat" chain="POSTROUTING" priority="0">-s <network_ip_relay> -o ens192 -j MASQUERADE</rule> <rule ipv="ipv4" table="nat" chain="OUTPUT" priority="0">-m owner --uid-owner netbird -p udp --dport 53 -j DNAT --to-destination 1.1.1.1:53</rule> <rule ipv="ipv4" table="nat" chain="OUTPUT" priority="1">-m owner --uid-owner netbird -p tcp --dport 53 -j DNAT --to-destination 1.1.1.1:53</rule> </direct> ``` `/etc/systemd/system/wstunnel-tproxy-routing.service`: ```ini [Unit] Description=policy routing for netbird→wstunnel After=network.target [Service] Type=oneshot ExecStart=/usr/bin/ip rule add pref 98 fwmark 0x66 lookup 101 ExecStart=/usr/bin/ip route replace local 0.0.0.0/0 dev lo table 101 RemainAfterExit=yes [Install] WantedBy=multi-user.target ``` This works but is **very complex**, interferes with Netbird’s own routing table, and is **fragile**. ## Problems with the current workaround Issues I see with this setup: * After ~6h (key exchange) Netbird loses its TProxy port mapping and fails to reconnect → needs service restart. * P2P not working because of ICE, even with UDP TProxy set. * TURN proxy not working (**only `rels://` works**). * Every internal IP that should be relayed has to be added to nftables manually. ## Proposed solutions ### 1. Minimal requirement: simple “WG-style” UDP frontend I **don’t** need a full, deeply integrated WebSocket transport in the Netbird client. A minimal but very useful feature would be: * Let Netbird send its **tunnel traffic** to a **single local UDP endpoint**, similar to how WG works with wstunnel: ```ini -L udp://8080:targetvg_server:51822?timeout_sec=0 \ ``` Concretely: * Allow configuring the Netbird client so that all WG-like traffic destined to the relay/manager goes to e.g. `127.0.0.1:8080`. * A local wstunnel instance then listens on `udp://127.0.0.1:8080` and forwards that over `wss://trustedserver:443` to the real Netbird/relay endpoint. * From Netbird’s point of view this is just a normal UDP endpoint; all WebSocket/HTTPS magic is handled by wstunnel. * This would eliminate: * TProxy, * fwmarks, * extra routing tables, * and most of the nftables complexity on the client. ### 2. Alternative: allow native WireGuard clients to connect to `netbird-manager` A different simple approach that would also solve my use case: * Allow **native WireGuard clients** (standard `wg`/`wg-quick`) to connect directly to `netbird-manager` as first-class peers. * `netbird-manager` would: * Issue proper WG configs for those peers. * Make sure Netbird clients treat those WG peers as regular Netbird peers and route traffic accordingly. That how I could keep using the well-tested `wg + wstunnel` combo on restricted networks, while still leveraging Netbird’s: * control plane, * ACLs, * mesh logic. ### 3. Nice to have: tunnel-aware manager / obfuscation Not strictly required, but would improve tunnel setups further: * Make `netbird-manager` **tunnel-aware**: * When a peer is known to be behind a tunnel/WebSocket, prefer serving a **local tunnel/relay address** instead of public relay information. * Avoid handing out unreachable public relay IPs to peers that can only reach each other via the tunnel. Optionally, provide a **native obfuscation / pluggable transport** mode that: * Wraps Netbird traffic in something HTTP(S)/WebSocket-like. * Can be forwarded via generic tunnel providers such as **Tailscale Funnel**, **Cloudflare Tunnel**, etc. * Eliminates the need for the TProxy + nftables hacking I’m doing now. ## Closing In short, I’d already be very happy with one of these minimal options: * Netbird being able to use a **simple local UDP frontend** (WG-style) that I can tunnel with wstunnel, **or** * Allowing **native WireGuard clients** to connect to `netbird-manager`. Everything else (tunnel-awareness / obfuscation) would be a big bonus, but these two would already make Netbird much easier and more robust to deploy on locked-down networks that require WebSocket/HTTPS tunneling. **Disclaimer: this issue (structure/formatting) was prepared with the help of an LLM.**

saavagebueno added the feature-request label 2026-08-05 01:22:19 -04:00

saavagebueno commented

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

@RainyPixel commented on GitHub (Jan 14, 2026):

+1 same problem

@RainyPixel commented on GitHub (Jan 14, 2026): +1 same problem

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

[GH-ISSUE #4879] Feature Request: Tunnel-aware relay/transport mode to Netbird #9485