Address family not supported by protocol

[davinellulinvega]

Describe the problem

After updating the Linux Netbird Client via the AUR repository from version 0.26.3-1 to version 0.26.4-1, the client cannot connect to the network anymore.
Running any netbird related command simply returns the following error message: Error: status failed: init route manager: setup routing: add rule v6 netbird: add routing rule: address family not supported by protocol

To Reproduce

Steps to reproduce the behavior:

1. Update netbird client to version 0.26.4-1 on linux
2. Run sudo netbird service start from command line

Expected behavior

I expected the client to connect to the existing network, but no such luck.

Are you using NetBird Cloud?

I am currently self-hosting the NetBird control panel on an AWS instance.

NetBird version

Installed version is 0.26.4

NetBird status -d output:

As with any other command, at the moment the output is just an error message: Error: status failed: init route manager: setup routing: add rule v6 netbird: add routing rule: address family not supported by protocol

Additional context

In an attempt to make the debugging process easier, I have enabled the debug logs. Here is the file resulting from simply starting the netbird client via systemd: client.log
It should be noted that no messages are being written to either the nebird.out or netbird.err files.

[davinellulinvega]

A few additional pieces of information:

• I have now updated the self-hosted control panel to the latest version as well.
• The issue does not reproduce on armbian, as far as I can tell it is limited to Arch Linux (kernel 6.8.2).
• I tried setting up the binary variant of the netbird package which is available on AUR with similar results.

[lixmal]

Hi @davinellulinvega,

this is an issue that pops up when ipv6 is not supported. I'll work on a fix.
Can you enable IPv6 as a temporary workaround? Basically the inverse of https://wiki.archlinux.org/title/IPv6#Disable_IPv6 (kernel support should suffice)

[davinellulinvega]

@lixmal You are entirely correct, after enabling IPv6 again the client works as expected.
This also means that my previous statement was wrong. It is not linked to the OS.

Regardless, thank you very much for the help.