Anyone Having Issues with Netbird 0.39.2?

Device is a BPI-R4. I had everything configured and working with Netbird 0.36.7 and Release 24.10.0, but after upgrading to 24.10.1 and 0.39.2, luci-proto-wireguard shows no Wireguard interfaces configured, and the netbird service remains disconnected even though the login via setup key was successful. The peers dashboard shows an initial "LAST SEEN" connection when logging in with the setup key, but it's never seen again after that.

I even re-flashed 24.10.0 and tried again, but I can't find the .ipk for netbird 0.36.7 anywhere, so 24.10.0 and 0.39.2 are doing the same thing, which leads me to believe that there might be a problem with 0.39.2. I'm going to re-image the sdcard instead of using a sysupgrade image to rule out some kind of artifact in the file system, but I was just wondering if anyone else is having this same problem.

root@OpenWrt:~# service netbird stop
root@OpenWrt:~# service netbird start     
root@OpenWrt:~# netbird login --setup-key XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Logging successfully
root@OpenWrt:~# netbird status -d
Peers detail:
Events: No events recorded
OS: linux/arm64
Daemon version: 0.39.2
CLI version: 0.39.2
Management: Disconnected
Signal: Disconnected
Relays:
Nameservers:
FQDN:
NetBird IP: N/A
Interface type: N/A
Quantum resistance: false
Networks: -
Forwarding rules: 0
Peers count: 0/0 Connected
root@OpenWrt:~# netbird up
Error: call service up method: rpc error: code = DeadlineExceeded desc = context deadline exceeded
root@OpenWrt:~# netbird down
Disconnected
root@OpenWrt:~# netbird up
Error: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded
root@OpenWrt:~# netbird status -d
Daemon status: LoginFailed

Run UP command to log in with SSO (interactive login):

 netbird up

If you are running a self-hosted version and no SSO provider has been configured in your Management Server,
you can use a setup-key:

 netbird up --management-url <YOUR_MANAGEMENT_URL> --setup-key <YOUR_SETUP_KEY>

More info: https://docs.netbird.io/how-to/register-machines-using-setup-keys

So re-flashing the USB drive image with either 24.10.0 or 24.10.1 and installing/configuring netbird 0.39.2 before doing anything else works without issue.

I've narrowed the culprit down to a list of packages I'm installing after getting netbird up and running again:

attr
bind-host
blkid
blockd
block-mount
curl
ddns-scripts
e4crypt
f2fs-tools
fdisk
gdisk
kmod-crypto-crc32
kmod-crypto-ecb
kmod-crypto-misc
kmod-fs-ext4
kmod-fs-f2fs
kmod-mii
kmod-nvme
kmod-qcom-qmi-helpers
libnvme
lsblk
lscpu
lsd
luci-app-commands
luci-app-ddns
luci-app-mwan3
luci-app-samba4
luci-proto-modemmanager
luci-proto-qmi
luci-proto-wireguard
modemmanager-rpcd
nano-full
nvme-cli
pciutils
usbutils
wget-ssl

Immediately after installing these packages, netbird stops functioning. I don't even need to restart the interface:

root@OpenWrt:~# netbird status -d
Peers detail:
 xxxxxxxxxxxxxx.netbird.cloud:
  NetBird IP: xxxxxxxxxxxxxxxx
  Public key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  Status: Disconnected
  -- detail --
  Connection type:
  ICE candidate (Local/Remote): -/-
  ICE candidate endpoints (Local/Remote): -/-
  Relay server address:
  Last connection update: 8 minutes, 38 seconds ago
  Last WireGuard handshake: -
  Transfer status (received/sent) 0 B/0 B
  Quantum resistance: false
  Networks: -
  Latency: 0s

 xxxxxxxxxx.netbird.cloud:
  NetBird IP: xxxxxxxxxxxx
  Public key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  Status: Disconnected
  -- detail --
  Connection type:
  ICE candidate (Local/Remote): -/-
  ICE candidate endpoints (Local/Remote): -/-
  Relay server address:
  Last connection update: -
  Last WireGuard handshake: -
  Transfer status (received/sent) 0 B/0 B
  Quantum resistance: false
  Networks: -
  Latency: 0s

 xxxxxxxxxxx.netbird.cloud:
  NetBird IP: xxxxxxxxxxxxxx
  Public key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  Status: Disconnected
  -- detail --
  Connection type:
  ICE candidate (Local/Remote): -/-
  ICE candidate endpoints (Local/Remote): -/-
  Relay server address:
  Last connection update: -
  Last WireGuard handshake: -
  Transfer status (received/sent) 0 B/0 B
  Quantum resistance: false
  Networks: -
  Latency: 0s

Events:
  [WARNING] DNS (d8d8486a-c5f6-40d9-84fd-b5c0458f7592)
    Message: The host dns manager does not support match domains
    Time: 8 minutes, 38 seconds ago
    Metadata: manager: file
  [INFO] SYSTEM (e356582c-8d5d-4ac6-a456-ab7fc578ff00)
    Message: Network map updated
    Time: 8 minutes, 38 seconds ago
OS: linux/arm64
Daemon version: 0.39.2
CLI version: 0.39.2
Management: Disconnected, reason: rpc error: code = Unavailable desc = keepalive ping failed to receive ACK within timeout
Signal: Disconnected, reason: rpc error: code = Unavailable desc = keepalive ping failed to receive ACK within timeout
Relays:
  [stun:stun.netbird.io:5555] is Unavailable, reason: dial: failed to listen: d.Dialer.DialContext: dial udp 209.94.63.37:5555: connect: invalid argument
  [turns:turn.netbird.io:443?transport=tcp] is Unavailable, reason: dial: d.Dialer.DialContext: dial tcp 209.94.61.253:443: connect: invalid argument
  [rels://relay.netbird.io:443] is Unavailable, reason: relay connection is not established
Nameservers:
FQDN: xxxxxxxxx.netbird.cloud
NetBird IP: xxxxxxxxxxxxxxxxx
Interface type: Kernel
Quantum resistance: false
Networks: -
Forwarding rules: 0
Peers count: 0/3 Connected
root@OpenWrt:~# netbird down
Disconnected
root@OpenWrt:~# netbird up
Error: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded
root@OpenWrt:~#

After restarting the interface and service:

root@OpenWrt:~# netbird down
Disconnected
root@OpenWrt:~# netbird up
Error: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded
root@OpenWrt:~# service netbird stop
root@OpenWrt:~# service netbird start
root@OpenWrt:~# netbird status -d
Peers detail:
Events: No events recorded
OS: linux/arm64
Daemon version: 0.39.2
CLI version: 0.39.2
Management: Disconnected
Signal: Disconnected
Relays:
Nameservers:
FQDN:
NetBird IP: N/A
Interface type: N/A
Quantum resistance: false
Networks: -
Forwarding rules: 0
Peers count: 0/0 Connected
root@OpenWrt:~# netbird up
Error: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded
root@OpenWrt:~#

I'll keep whittling at it, but if anyone has an idea why one of these packages would be borking netbird, please tell. I had all of these packages installed prior to upgrading to 24.10.1, and everything was working just fine before I did, so I'm currently at a loss to explain this.

So, looks like it's mwan3 causing it, or some interaction between it and netbird, or one of their dependencies.

If I install just mwan3 and its dependencies before or after installing netbird, it will result in a previously or future functioning netbird implementation to break.

The primary errors are:

Management: Disconnected, reason: rpc error: code = Unavailable desc = keepalive ping failed to receive ACK within timeout
Signal: Disconnected, reason: rpc error: code = Unavailable desc = keepalive ping failed to receive ACK within timeout
Relays:
  [stun:stun.netbird.io:5555] is Unavailable, reason: dial: failed to listen: d.Dialer.DialContext: dial udp 209.94.63.37:5555: connect: invalid argument
  [turns:turn.netbird.io:443?transport=tcp] is Unavailable, reason: dial: d.Dialer.DialContext: dial tcp 209.94.61.253:443: connect: invalid argument
  [rels://relay.netbird.io:443] is Unavailable, reason: relay connection is not established
Error: call service up method: rpc error: code = DeadlineExceeded desc = context deadline exceeded
Error: login backoff cycle failed: rpc error: code = Unknown desc = getting device authorization flow info failed with error: context deadline exceeded

Issue created:

Someone mentioned this issue to me a few months ago. For more context, see: netbirdio/netbird#3363 (comment).

Quoted from the opened issue above, this is my response.

Opened an issue at netbirdio/netbird#3736 in the upstream.