Unable to use network routes

[CommanderRedYT]

Problem/Motivation

I have a pv installation somewhere with a device that tracks solar production. I need netbird to be able to forward the ip range to my server network so that I can collect the data.

Expected behavior

After configuring network routes, I should be able to access devices from the remote network.

Actual behavior

I am unable to debug if

Steps to reproduce

1. Create network route
2. Try to ping the device in the forwarded network from a peer where the route gets distributed.
3. Ping fails
4. Ping from inside the netbird docker container on the hassio host that forwards it
5. Ping works

[CommanderRedYT]

Here are my logs (removed identifying information):

-----------------------------------------------------------
 Add-on: NetBird-Client
 Connect your devices into a single secure private WireGuard®-based mesh network with SSO/MFA and simple access controls.
-----------------------------------------------------------
 Add-on version: 1.29.4
 You are running the latest version of this add-on.
 System: Home Assistant OS 14.0  (aarch64 / odroid-m1)
 Home Assistant Core: 2024.11.3
 Home Assistant Supervisor: 2024.11.4
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[11:29:09] INFO: Configuring timezone (Europe/Vienna)...
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun netbird (no readiness notification)
s6-rc: info: service legacy-services successfully started
[11:29:11] INFO: No Setup Key Set
[11:29:11] INFO: This client will only show up in dashboards it's already registered with.
[11:29:11] INFO: Using Default Admin URL
[11:29:11] INFO: Using Default Management URL
[11:29:11] INFO: Starting NetBird Client...
2024-12-09T11:29:13+01:00 INFO client/internal/connect.go:117: starting NetBird client version 0.29.4 on linux/arm64
2024-12-09T11:29:14+01:00 INFO client/internal/connect.go:252: connecting to the Relay service(s): rels://relay.netbird.io:443
2024-12-09T11:29:14+01:00 INFO relay/client/picker.go:66: try to connecting to relay server: rels://relay.netbird.io:443
2024-12-09T11:29:14+01:00 INFO [relay: rels://relay.netbird.io:443] relay/client/client.go:165: create new relay connection: local peerID: peer1, local peer hashedID: peer1hash
2024-12-09T11:29:14+01:00 INFO [relay: rels://relay.netbird.io:443] relay/client/client.go:171: connecting to relay server
2024-12-09T11:29:14+01:00 INFO [relay: rels://relay.netbird.io:443] relay/client/client.go:192: relay connection established
2024-12-09T11:29:14+01:00 INFO relay/client/picker.go:84: connected to Relay server: rels://relay.netbird.io:443
2024-12-09T11:29:14+01:00 INFO relay/client/picker.go:58: chosen home Relay server: rels://relay.netbird.io:443
2024-12-09T11:29:14+01:00 INFO client/internal/connect.go:405: using 36235 as wireguard port: 51820 is in use
2024-12-09T11:29:14+01:00 INFO client/internal/wgproxy/proxy_ebpf.go:89: local wg proxy listening on: 3128
2024-12-09T11:29:14+01:00 ERRO client/internal/routemanager/systemops/systemops_linux.go:100: Error setting up sysctl: 1 errors occurred:
	* write sysctl net.ipv4.conf.all.src_valid_mark: open /proc/sys/net/ipv4/conf/all/src_valid_mark: read-only file system
2024-12-09T11:29:14+01:00 INFO client/internal/routemanager/manager.go:142: Routing setup complete
2024-12-09T11:29:15+01:00 INFO client/firewall/create_linux.go:51: creating an nftables firewall manager
2024-12-09T11:29:15+01:00 INFO client/internal/dns/host_unix.go:68: System DNS manager discovered: file
2024-12-09T11:29:15+01:00 INFO signal/client/grpc.go:147: connected to the Signal Service stream
2024-12-09T11:29:15+01:00 INFO client/internal/engine.go:1374: Network monitor is disabled, not starting
2024-12-09T11:29:15+01:00 INFO client/internal/connect.go:286: Netbird engine started, the IP is: 100.107.96.232/16
2024-12-09T11:29:15+01:00 INFO management/client/grpc.go:155: connected to the Management Service stream
2024-12-09T11:29:15+01:00 WARN client/internal/engine.go:554: running SSH server is not permitted
2024-12-09T11:29:15+01:00 WARN client/internal/dns/server.go:316: the DNS manager of this peer doesn't support custom port. Disabling primary DNS setup. Learn more at: https://docs.netbird.io/how-to/manage-dns-in-your-network#local-resolver
2024-12-09T11:29:15+01:00 ERRO client/internal/dns/server.go:322: unable to configure DNS for this peer using file manager without a nameserver group with all domains configured
2024-12-09T11:29:15+01:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 48.3474ms, total rules count: 56
2024-12-09T11:29:16+01:00 INFO [peer: peer2] client/internal/peer/worker_relay.go:59: Relay is not supported by remote peer
2024-12-09T11:29:16+01:00 INFO [peer: peer3] client/internal/peer/worker_relay.go:59: Relay is not supported by remote peer
2024-12-09T11:29:16+01:00 INFO [relay: rels://relay.netbird.io:443] relay/client/client.go:214: open connection to peer: sha-foo
2024-12-09T11:29:16+01:00 INFO client/internal/wgproxy/proxy_ebpf.go:101: turn conn added to wg proxy store: rels://streamline-de-fra1-0.relay.netbird.io:443, endpoint port: :1
2024-12-09T11:29:16+01:00 INFO [peer: peer4] client/internal/peer/conn.go:536: created new wgProxy for relay connection: 127.0.0.1:1
2024-12-09T11:29:16+01:00 INFO [relay: rels://streamline-de-fra1-2.relay.netbird.io:443] relay/client/client.go:165: create new relay connection: local peerID: peer1, local peer hashedID: peer1hash
2024-12-09T11:29:16+01:00 INFO [relay: rels://streamline-de-fra1-2.relay.netbird.io:443] relay/client/client.go:171: connecting to relay server
2024-12-09T11:29:16+01:00 INFO [peer: peer4] client/internal/peer/conn.go:577: start to communicate with peer via relay
2024-12-09T11:29:16+01:00 INFO [peer: peer5] client/internal/peer/worker_relay.go:59: Relay is not supported by remote peer
2024-12-09T11:29:16+01:00 INFO [peer: peer2] client/internal/peer/conn.go:430: set ICE to active connection
2024-12-09T11:29:16+01:00 INFO [relay: rels://relay.netbird.io:443] relay/client/client.go:214: open connection to peer: sha-foo
2024-12-09T11:29:16+01:00 INFO client/internal/wgproxy/proxy_ebpf.go:101: turn conn added to wg proxy store: rels://streamline-de-fra1-0.relay.netbird.io:443, endpoint port: :2
2024-12-09T11:29:16+01:00 INFO [peer: peer6] client/internal/peer/conn.go:536: created new wgProxy for relay connection: 127.0.0.1:2
2024-12-09T11:29:16+01:00 INFO [relay: rels://streamline-de-fra1-1.relay.netbird.io:443] relay/client/client.go:165: create new relay connection: local peerID: peer1, local peer hashedID: peer1hash
2024-12-09T11:29:16+01:00 INFO [relay: rels://streamline-de-fra1-1.relay.netbird.io:443] relay/client/client.go:171: connecting to relay server
2024-12-09T11:29:16+01:00 INFO [peer: peer6] client/internal/peer/conn.go:577: start to communicate with peer via relay
2024-12-09T11:29:16+01:00 INFO [peer: peer3] client/internal/peer/conn.go:430: set ICE to active connection
2024-12-09T11:29:16+01:00 INFO [relay: rels://streamline-de-fra1-2.relay.netbird.io:443] relay/client/client.go:192: relay connection established
2024-12-09T11:29:16+01:00 INFO [relay: rels://streamline-de-fra1-2.relay.netbird.io:443] relay/client/client.go:214: open connection to peer: sha-foo
2024-12-09T11:29:16+01:00 INFO client/internal/wgproxy/proxy_ebpf.go:101: turn conn added to wg proxy store: rels://streamline-de-fra1-2.relay.netbird.io:443, endpoint port: :3
2024-12-09T11:29:16+01:00 INFO [peer: peer7] client/internal/peer/conn.go:536: created new wgProxy for relay connection: 127.0.0.1:3
2024-12-09T11:29:16+01:00 INFO [relay: rels://streamline-de-fra1-1.relay.netbird.io:443] relay/client/client.go:192: relay connection established
2024-12-09T11:29:16+01:00 INFO [relay: rels://streamline-de-fra1-1.relay.netbird.io:443] relay/client/client.go:214: open connection to peer: sha-foo
2024-12-09T11:29:16+01:00 INFO client/internal/wgproxy/proxy_ebpf.go:101: turn conn added to wg proxy store: rels://streamline-de-fra1-1.relay.netbird.io:443, endpoint port: :4
2024-12-09T11:29:16+01:00 INFO [peer: peer8] client/internal/peer/conn.go:536: created new wgProxy for relay connection: 127.0.0.1:4
2024-12-09T11:29:16+01:00 INFO [peer: peer7] client/internal/peer/conn.go:577: start to communicate with peer via relay
2024-12-09T11:29:16+01:00 INFO [peer: peer8] client/internal/peer/conn.go:577: start to communicate with peer via relay
2024-12-09T11:29:16+01:00 INFO [peer: peer7] client/internal/peer/conn.go:430: set ICE to active connection
2024-12-09T11:29:16+01:00 INFO [peer: peer5] client/internal/peer/conn.go:430: set ICE to active connection
2024-12-09T11:29:17+01:00 INFO [peer: peer6] client/internal/peer/conn.go:430: set ICE to active connection
2024-12-09T11:29:17+01:00 INFO [peer: peer8] client/internal/peer/conn.go:430: set ICE to active connection
2024-12-09T11:29:17+01:00 INFO [peer: peer4] client/internal/peer/conn.go:430: set ICE to active connection

[CommanderRedYT]

Possibly related to netbirdio/netbird#2290