Arch Linux User Repository

FYI: we will make the NB_CONFIG/--config point to the location of the default profile soon, so it will be 100% compatible with pre-0.52.x

nazarewk,

Okay, the next version it is then. I'll use my own relay unit until netbird provides a replacement, or discontinues the relay daemon.

The idea for using templated units was never running several copies of netbird simultaneously (I understand it's not that simple), but to be able to easily switch between several configuration files (e.g. work & home). Since you've now solved it by other means, maybe it makes sense to remove the template altogether.

@tarball Actually with 0.52.0+ the client package does need to be adjusted due to:

• introduction of configuration profiles (they're put inside NB_STATE_DIR or /var/lib/netbird by default)

• we're currently migrating it only from /etc/netbird/config.json directly (ignoring the flag/envvar), I'll see what we can do about it,

• deprecating NB_CONFIG / --config flag

I usually ignore comments like this, but oh well.

This package has shipped systemd units since the beginning (June 2021, when the project was just started and was called "wiretrustee"). These units were written specifically for this package and were then upstreamed with minor changes in November 2023.

These are the OG files, and this configuration/variable names have been used since before upstream had any units at all. I can't just break existing users' configurations for no reason.

netbird-bin has recently been migrated to upstream units, but I can't do this one yet because there's no upstream replacement for the relay service, and they currently refuse to accept one.

This package will be migrated:

1. when they change their mind;
2. OR everything is merged into a single binary (and all subpackages except netbird get deprecated);
3. OR their units diverge even further, introducing more incompatibilities.

Whatever comes first.

Can you please explain the rationale behind changing netbird@.service from the default at: https://github.com/netbirdio/netbird/blob/main/release_files/systemd/netbird%40.service

Specifically:

- The invocation command lacks:
  - Logging to file
  - `--daemon-addr` unix socket
  - (the default environment variable is also renamed)
- Two useful comments are removed
- Whitespace is changed

The netbird doco directs people to look in /var/log/netbird/ for log files.

I can understand wanting to log to console, but please don't disable the default, rather add it additionally if you really must change the default logging behaviour.

Consider adding the flag "-x" to the go mod download. It has the benefit of adding correct logs for future reproducible build. https://reproducible.archlinux.org/

Also tells the user about the downloads.

go mod download -x

I'm not getting any log files in /var/log/netbird after deleting /etc/netbird/main.json, enabling the service, and doing netbird up.

Additionally, netbird up --log-file console does not print any output.

Can you please confirm these (2) both work for you?

edit: delayed because:

1. there's no replacement for the relay systemd unit upstream
2. there's probably more breakage coming in the near future due to everything being merged into a single binary

I intentionally avoided doing that because there was talk of Netbird possibly being accepted into official repositories, which would likely require users to chuck their setups and reconfigure.

Since nothing came of it, we might as well migrate to upstream configs. I'll update the package in the next couple of days.

Hello,

1) Would it be possible for you to track/synchronize with the upstream systemd file, while making changes in drop-in files? Might ease the sync/development effort 2) I have noticed some envvars missing, that prevents us from gathering logs for a debug bundle. If above isn't possible could you adjust those on your side? https://github.com/netbirdio/netbird/pull/4124/files