network routing no longer works after upgrade to 0.27.0 #777

Closed
opened 2025-11-20 05:17:19 -05:00 by saavagebueno · 2 comments
Owner

Originally created by @lfarkas on GitHub (Apr 4, 2024).

after upgrading to 0.27.0 the only routing line on all peers are:
100.76.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wt0
this was works before updating to this version.
even though it seems to working from the logfile:

2024-04-04T22:49:01+02:00 WARN client/internal/routemanager/client.go:134: the network 10.20.0.0/24 has not been assigned a routing peer as no peers from the list [1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE=] are currently connected
2024-04-04T22:49:01+02:00 WARN client/internal/routemanager/client.go:134: the network 10.30.0.0/24 has not been assigned a routing peer as no peers from the list [1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE=] are currently connected
2024-04-04T22:49:04+02:00 INFO client/internal/routemanager/client.go:137: new chosen route is co1kuj3l0ubs739dg11g with peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= with score 2 for network 10.30.0.0/24
2024-04-04T22:49:04+02:00 INFO client/internal/routemanager/client.go:137: new chosen route is co1kv3bl0ubs739dg130 with peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= with score 2 for network 10.20.0.0/24
2024-04-04T22:49:04+02:00 INFO client/internal/peer/conn.go:387: connected to peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE=, endpoint address: 145.236.15.52:51820

but no such route added.

Originally created by @lfarkas on GitHub (Apr 4, 2024). after upgrading to 0.27.0 the only routing line on all peers are: `100.76.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wt0` this was works before updating to this version. even though it seems to working from the logfile: ``` 2024-04-04T22:49:01+02:00 WARN client/internal/routemanager/client.go:134: the network 10.20.0.0/24 has not been assigned a routing peer as no peers from the list [1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE=] are currently connected 2024-04-04T22:49:01+02:00 WARN client/internal/routemanager/client.go:134: the network 10.30.0.0/24 has not been assigned a routing peer as no peers from the list [1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE=] are currently connected 2024-04-04T22:49:04+02:00 INFO client/internal/routemanager/client.go:137: new chosen route is co1kuj3l0ubs739dg11g with peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= with score 2 for network 10.30.0.0/24 2024-04-04T22:49:04+02:00 INFO client/internal/routemanager/client.go:137: new chosen route is co1kv3bl0ubs739dg130 with peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= with score 2 for network 10.20.0.0/24 2024-04-04T22:49:04+02:00 INFO client/internal/peer/conn.go:387: connected to peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE=, endpoint address: 145.236.15.52:51820 ``` but no such route added.
saavagebueno added the clientroutes labels 2025-11-20 05:17:19 -05:00
Author
Owner

@lixmal commented on GitHub (Apr 4, 2024):

Can you please tell us the OS and netbird status -d?
If this is a linux box, the routes are now in the netbird routing table: ip route show table netbird

@lixmal commented on GitHub (Apr 4, 2024): Can you please tell us the OS and `netbird status -d`? If this is a linux box, the routes are now in the `netbird` routing table: `ip route show table netbird`
Author
Owner

@lfarkas commented on GitHub (Apr 4, 2024):

ok than the route is that table... and routing not working only from one machine may be another problem...

@lfarkas commented on GitHub (Apr 4, 2024): ok than the route is that table... and routing not working only from one machine may be another problem...
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#777