can't access Home network with Network Routes, docker container errors

[Bush-cat]

Describe the problem Network Routes don't work, probably because of the two Errors in the Log below. I can ping the peer Netbird IP 100.105.x.x but can't ping/access my Home Network 192.168.x.x, the Errors were there even before I created the Network Routes.

I wanted to use Netbird to get away from DS-Lite and be able to access my Network from IPv4 only Networks Used Tailscale Years ago but now chose netbird because of the Network Route, DNS Options (I want to use my adguard home + nginx reverse proxy) and better Documentation.

To Reproduce

Steps to reproduce the behavior:

1. New Account on NetBird
2. Added a Docker Peer and my android Tablet using the Netbird App
3. add my home Network to Network Routes
4. reconnect and ping an adress from my home Network
5. Add home Network Router as DNS in Netbird Cloud
6. reconnect and ping again

Expected behavior Access my other Services not running Netbird in my home Network by their IP

Are you using NetBird Cloud? Yes

NetBird version netbirdclient version 0.26.3

Logs

2024-03-21T08:54:57Z INFO client/internal/connect.go:96: starting NetBird client version 0.26.3
2024-03-21T08:54:57Z WARN client/internal/wgproxy/factory_linux.go:15: failed to initialize ebpf proxy, fallback to user space proxy: failed to set memlock rlimit: operation not permitted
2024-03-21T08:54:57Z WARN client/firewall/nftables/route_linux.go:69: table 'filter' not found for forward rules
2024-03-21T08:54:57Z INFO client/internal/dns/host_linux.go:68: System DNS manager discovered: file
2024-03-21T08:54:58Z INFO signal/client/grpc.go:156: connected to the Signal Service stream
2024-03-21T08:54:58Z INFO client/internal/connect.go:239: Netbird engine started, my IP is: 100.105.REDACTED
2024-03-21T08:54:58Z INFO management/client/grpc.go:145: connected to the Management Service stream
2024-03-21T08:54:58Z WARN client/internal/engine.go:495: running SSH server is not permitted
2024-03-21T08:54:58Z ERRO client/internal/engine.go:688: failed to update routes, err: open /proc/sys/net/ipv4/ip_forward: read-only file system
2024-03-21T08:54:58Z ERRO client/internal/dns/server.go:317: unable to configure DNS for this peer using file manager without a nameserver group with all domains configured
2024-03-21T08:54:58Z INFO client/internal/acl/manager.go:52: ACL rules processed in: 5.493565ms, total rules count: 2

Additional context My Docker Compose, I run the container inside Portainer

version: "3"
services:
    netbird:
        container_name: netbird
        hostname: netbird
        cap_add:
            - NET_ADMIN
            - SYS_ADMIN
            - SYS_RESOURCE
        environment:
            - NB_SETUP_KEY="REDACTED"
        volumes:
            - /volume1/misc/configs/netbird:/etc/netbird
        image: netbirdio/netbird:latest

[PatCas71]

Selfhost seem to have the same behaviour.

WARN client/internal/routemanager/client.go:153: the network 10.20.0.0/24 has not been assigned a routing peer as no peers from the list [EwmCuJlXrjQ2nmqTVRrh2DgnMGzIQMU1j8UjSPhSu0I=] are currently connected

The peer is connected...

[braginini]

Selfhost seem to have the same behaviour.

WARN client/internal/routemanager/client.go:153: the network 10.20.0.0/24 has not been assigned a routing peer as no peers from the list [EwmCuJlXrjQ2nmqTVRrh2DgnMGzIQMU1j8UjSPhSu0I=] are currently connected

The peer is connected...

@PatCas71 is it displayed as connected when running the netbird status -d command?