[GH-ISSUE #1736] can't access Home network with Network Routes, docker container errors #3127

Closed
opened 2026-08-05 00:50:44 -04:00 by saavagebueno · 7 comments
Owner

Originally created by @Bush-cat on GitHub (Mar 21, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1736

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
Originally created by @Bush-cat on GitHub (Mar 21, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1736 **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 ```yaml 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 ```
saavagebueno added the triage-needed label 2026-08-05 00:50:44 -04:00
Author
Owner

@PatCas71 commented on GitHub (Apr 14, 2024):

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...

<!-- gh-comment-id:2054019553 --> @PatCas71 commented on GitHub (Apr 14, 2024): 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...
Author
Owner

@braginini commented on GitHub (Apr 14, 2024):

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?

<!-- gh-comment-id:2054023179 --> @braginini commented on GitHub (Apr 14, 2024): > 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?
Author
Owner

@nazarewk commented on GitHub (Apr 23, 2025):

@Bush-cat were you able to resolve your problem or is it still an issue for you?

<!-- gh-comment-id:2823817538 --> @nazarewk commented on GitHub (Apr 23, 2025): @Bush-cat were you able to resolve your problem or is it still an issue for you?
Author
Owner

@Bush-cat commented on GitHub (Apr 23, 2025):

@Bush-cat were you able to resolve your problem or is it still an issue for you?

I have stopped using netbird since the issue, I can give it another try when I have time.

<!-- gh-comment-id:2824370868 --> @Bush-cat commented on GitHub (Apr 23, 2025): > [@Bush-cat](https://github.com/Bush-cat) were you able to resolve your problem or is it still an issue for you? I have stopped using netbird since the issue, I can give it another try when I have time.
Author
Owner

@Bush-cat commented on GitHub (Jun 18, 2025):

I have recently setup netbird again and maybe will set this up again. Also looking at the error message again I think it could be fixed by systctl
eg setting
net.ipv4.ip_forward=1

<!-- gh-comment-id:2986003933 --> @Bush-cat commented on GitHub (Jun 18, 2025): I have recently setup netbird again and maybe will set this up again. Also looking at the error message again I think it could be fixed by systctl eg setting net.ipv4.ip_forward=1
Author
Owner

@nazarewk commented on GitHub (Jun 19, 2025):

eg setting
net.ipv4.ip_forward=1

I didn't analyze it in-depth, but I do remember at least a few cases of missing net.ipv4.ip_forward=1 on the host running the container. Running outside the container NetBird will adjust this setting automatically, but it might work inside the container when running as privileged: true.

<!-- gh-comment-id:2987678937 --> @nazarewk commented on GitHub (Jun 19, 2025): > eg setting > net.ipv4.ip_forward=1 I didn't analyze it in-depth, but I do remember at least a few cases of missing `net.ipv4.ip_forward=1` on the host running the container. Running outside the container NetBird will adjust this setting automatically, but it _might_ work inside the container when running as `privileged: true`.
Author
Owner

@PizzaLovingNerd commented on GitHub (Jun 3, 2026):

Closing as stale. This was reported for a very old version of NetBird, and the reported failure appears to be a Docker/host IP forwarding configuration issue, and current docs cover enabling forwarding for routing peers. Cheers!

<!-- gh-comment-id:4618571779 --> @PizzaLovingNerd commented on GitHub (Jun 3, 2026): Closing as stale. This was reported for a very old version of NetBird, and the reported failure appears to be a Docker/host IP forwarding configuration issue, and current docs cover enabling forwarding for routing peers. Cheers!
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#3127