Docker client not updating routes ? other client types fine #1535

Closed
opened 2025-11-20 05:32:23 -05:00 by saavagebueno · 2 comments
Owner

Originally created by @ecwio on GitHub (Jan 1, 2025).

Describe the problem

docker client seem not to update route correctly

To Reproduce

Steps to reproduce the behavior:
create network routes
iphone client can connect
mac os client can connect
linux client can connect
docker clients cannot connect (running on raspberry pi all of them)

Expected behavior

all clients can talk to each other

Are you using NetBird Cloud?

no

NetBird version

0.35.2

Additional context

Here is how I came to this conclusion:
new day, new test , so I wiped everything on the server and started from scratch. currently on 0.35.2 on all peers except iphone on the latest dev
created two Network Routes (the legacy) for my 2 static networks:
network route 1: 192.168.1.0/24 routed through group of peers on same physical location and distributed to iphone and peer in network 2
network route 2: 192.168.8.0/24 routed through group of peers on same physical location and distributed to iphone and peer in network 1
one dns 192.168.8.1 with 17 hostnames to resolve that is distributed to iphone and network 1
result:
iphone can reach both networks on ip and domain
network 1 and network 2 cannot reach each other.
then I go on my mac client that is on network 2 and see that under network my new route setting to network 1 was deactivated.. I activate it and surely got a successful ping to network 2.
then I go to my pi5 running in the same network as the macbook and I cannot ping network 1….
So I go to my pi2 that is too old to run docker and is running the debian client and I can ping network 1 !!
since I am fine on iphone and macbook and pi2 then the only ones left are my machines running the docker client that ALL have the same issue so Im thinking it has to do with the docker client.
BUT it has been two days Im trying to find a way to access the docker client status and see if the route is correctly enabled. What would be the correct way to go about that ? Ping me Im available for debug info if you find this interesting.

Originally created by @ecwio on GitHub (Jan 1, 2025). **Describe the problem** docker client seem not to update route correctly **To Reproduce** Steps to reproduce the behavior: create network routes iphone client can connect mac os client can connect linux client can connect docker clients cannot connect (running on raspberry pi all of them) **Expected behavior** all clients can talk to each other **Are you using NetBird Cloud?** no **NetBird version** 0.35.2 **Additional context** Here is how I came to this conclusion: new day, new test , so I wiped everything on the server and started from scratch. currently on 0.35.2 on all peers except iphone on the latest dev created two Network Routes (the legacy) for my 2 static networks: network route 1: 192.168.1.0/24 routed through group of peers on same physical location and distributed to iphone and peer in network 2 network route 2: 192.168.8.0/24 routed through group of peers on same physical location and distributed to iphone and peer in network 1 one dns 192.168.8.1 with 17 hostnames to resolve that is distributed to iphone and network 1 result: iphone can reach both networks on ip and domain network 1 and network 2 cannot reach each other. then I go on my mac client that is on network 2 and see that under network my new route setting to network 1 was deactivated.. I activate it and surely got a successful ping to network 2. then I go to my pi5 running in the same network as the macbook and I cannot ping network 1…. So I go to my pi2 that is too old to run docker and is running the debian client and I can ping network 1 !! since I am fine on iphone and macbook and pi2 then the only ones left are my machines running the docker client that ALL have the same issue so Im thinking it has to do with the docker client. BUT it has been two days Im trying to find a way to access the docker client status and see if the route is correctly enabled. What would be the correct way to go about that ? Ping me Im available for debug info if you find this interesting.
saavagebueno added the waiting-feedbacktriage-needed labels 2025-11-20 05:32:24 -05:00
Author
Owner

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

Hello @ecwio,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

@nazarewk commented on GitHub (Apr 28, 2025): Hello @ecwio, We're currently reviewing our open issues and would like to verify if this problem still exists in the [latest NetBird version](https://github.com/netbirdio/netbird/releases). Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within **2 weeks**, but feel free to reopen it with updated information. Thanks for your contribution to improving the project!
Author
Owner

@mlsmaycon commented on GitHub (Jun 1, 2025):

closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.

@mlsmaycon commented on GitHub (Jun 1, 2025): closing issue due to no recent feedback. Feel free to open a new one if the issue persist or reopen if this was a feature request.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1535