SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-06-30 19:22:07 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

linux routing is not working agian #882

New Issue
Open
opened 2025-11-20 05:19:11 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:19:11 -05:00
Owner
Copy Link

Originally created by @lfarkas on GitHub (May 13, 2024).

even after restart my client i can see this is in the log:

2024-05-13T12:47:11+02:00 WARN client/internal/routemanager/client.go:154: the network 192.168.0.0/16 has not been assigned a routing peer as no peers from the list [FfiyZKMquYILabBxOquw/jXEuTjhBq6tUvBEPdV3ckY= hCDjKQBW9TBwsZigTRXxvVzpAYE+ZqDHBol4sOSUMl0=] are currently connected
2024-05-13T12:47:11+02:00 WARN client/internal/routemanager/client.go:154: 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-05-13T12:47:11+02:00 WARN client/internal/routemanager/client.go:154: 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-05-13T12:47:11+02:00 INFO client/internal/dns/systemd_linux.go:144: adding 4 search domains and 0 match domains. Search list: [int.vidux.hu vidux.internal szeged.vidux.hu netbird.cloud] , Match list: []
2024-05-13T12:47:11+02:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 3.021225ms, total rules count: 2
2024-05-13T12:47:13+02:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 10.30.0.1:53: read udp 10.1.251.86:53348->10.30.0.1:53: i/o timeout
2024-05-13T12:47:13+02:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 192.168.208.1:53: read udp 10.6.6.2:59381->192.168.208.1:53: i/o timeout
2024-05-13T12:47:13+02:00 WARN client/internal/dns/upstream.go:265: Upstream resolving is Disabled for 30s
2024-05-13T12:47:13+02:00 INFO [nameservers: [{192.168.208.1 udp 53}]] client/internal/dns/server.go:504: Temporarily deactivating nameservers group due to timeout
2024-05-13T12:47:13+02:00 WARN client/internal/dns/upstream.go:265: Upstream resolving is Disabled for 30s
2024-05-13T12:47:13+02:00 INFO client/internal/dns/systemd_linux.go:144: adding 2 search domains and 0 match domains. Search list: [szeged.vidux.hu netbird.cloud] , Match list: []
2024-05-13T12:47:13+02:00 INFO [nameservers: [{10.30.0.1 udp 53}]] client/internal/dns/server.go:504: Temporarily deactivating nameservers group due to timeout
2024-05-13T12:47:13+02:00 INFO client/internal/dns/systemd_linux.go:144: adding 1 search domains and 0 match domains. Search list: [netbird.cloud] , Match list: []
2024-05-13T12:47:15+02:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 192.168.208.1:53: read udp 10.6.6.2:39320->192.168.208.1:53: i/o timeout
2024-05-13T12:47:16+02:00 INFO client/internal/routemanager/client.go:165: new chosen route is co1dqj3l0ubs739dfnsg with peer hCDjKQBW9TBwsZigTRXxvVzpAYE+ZqDHBol4sOSUMl0= with score 2.966603 for network 192.168.0.0/16
2024-05-13T12:47:16+02:00 INFO client/internal/peer/conn.go:388: connected to peer hCDjKQBW9TBwsZigTRXxvVzpAYE+ZqDHBol4sOSUMl0=, endpoint address: 185.199.30.141:9133
2024-05-13T12:47:17+02:00 INFO client/internal/peer/conn.go:388: connected to peer FfiyZKMquYILabBxOquw/jXEuTjhBq6tUvBEPdV3ckY=, endpoint address: 185.199.30.141:16269
2024-05-13T12:47:17+02:00 WARN client/internal/routemanager/client.go:120: peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= has 0 latency
2024-05-13T12:47:17+02:00 INFO client/internal/routemanager/client.go:165: new chosen route is co1kv3bl0ubs739dg130 with peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= with score 2.000000 for network 10.20.0.0/24
2024-05-13T12:47:17+02:00 WARN client/internal/routemanager/client.go:120: peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= has 0 latency
2024-05-13T12:47:17+02:00 INFO client/internal/routemanager/client.go:165: new chosen route is co1kuj3l0ubs739dg11g with peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= with score 2.000000 for network 10.30.0.0/24
2024-05-13T12:47:17+02:00 WARN client/internal/routemanager/client.go:120: peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= has 0 latency
2024-05-13T12:47:17+02:00 WARN client/internal/routemanager/client.go:120: peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= has 0 latency
2024-05-13T12:47:17+02:00 WARN client/internal/routemanager/client.go:120: peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= has 0 latency
2024-05-13T12:47:17+02:00 INFO client/internal/peer/conn.go:388: connected to peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE=, endpoint address: 145.236.15.52:51820
2024-05-13T12:47:18+02:00 INFO client/internal/peer/conn.go:388: connected to peer +i/q6dNa3AeF/iNJMH9+CbnsTLmFPfN+/K0KUPJI5wI=, endpoint address: 3.73.3.142:37959
2024-05-13T12:47:21+02:00 INFO client/internal/dns/upstream.go:241: upstreams [192.168.208.1:53] are responsive again. Adding them back to system
2024-05-13T12:47:21+02:00 INFO client/internal/dns/systemd_linux.go:144: adding 3 search domains and 0 match domains. Search list: [int.vidux.hu vidux.internal netbird.cloud] , Match list: []

at 12:47:11: "network 10.30.0.0/24 has not been assigned a routing peer" is vaild
but at 12:47:17 while listed:

2024-05-13T12:47:17+02:00 WARN client/internal/routemanager/client.go:120: peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= has 0 latency
2024-05-13T12:47:17+02:00 INFO client/internal/routemanager/client.go:165: new chosen route is co1kuj3l0ubs739dg11g with peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= with score 2.000000 for network 10.30.0.0/24

the routing rule never added....

Originally created by @lfarkas on GitHub (May 13, 2024). even after restart my client i can see this is in the log: ``` 2024-05-13T12:47:11+02:00 WARN client/internal/routemanager/client.go:154: the network 192.168.0.0/16 has not been assigned a routing peer as no peers from the list [FfiyZKMquYILabBxOquw/jXEuTjhBq6tUvBEPdV3ckY= hCDjKQBW9TBwsZigTRXxvVzpAYE+ZqDHBol4sOSUMl0=] are currently connected 2024-05-13T12:47:11+02:00 WARN client/internal/routemanager/client.go:154: 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-05-13T12:47:11+02:00 WARN client/internal/routemanager/client.go:154: 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-05-13T12:47:11+02:00 INFO client/internal/dns/systemd_linux.go:144: adding 4 search domains and 0 match domains. Search list: [int.vidux.hu vidux.internal szeged.vidux.hu netbird.cloud] , Match list: [] 2024-05-13T12:47:11+02:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 3.021225ms, total rules count: 2 2024-05-13T12:47:13+02:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 10.30.0.1:53: read udp 10.1.251.86:53348->10.30.0.1:53: i/o timeout 2024-05-13T12:47:13+02:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 192.168.208.1:53: read udp 10.6.6.2:59381->192.168.208.1:53: i/o timeout 2024-05-13T12:47:13+02:00 WARN client/internal/dns/upstream.go:265: Upstream resolving is Disabled for 30s 2024-05-13T12:47:13+02:00 INFO [nameservers: [{192.168.208.1 udp 53}]] client/internal/dns/server.go:504: Temporarily deactivating nameservers group due to timeout 2024-05-13T12:47:13+02:00 WARN client/internal/dns/upstream.go:265: Upstream resolving is Disabled for 30s 2024-05-13T12:47:13+02:00 INFO client/internal/dns/systemd_linux.go:144: adding 2 search domains and 0 match domains. Search list: [szeged.vidux.hu netbird.cloud] , Match list: [] 2024-05-13T12:47:13+02:00 INFO [nameservers: [{10.30.0.1 udp 53}]] client/internal/dns/server.go:504: Temporarily deactivating nameservers group due to timeout 2024-05-13T12:47:13+02:00 INFO client/internal/dns/systemd_linux.go:144: adding 1 search domains and 0 match domains. Search list: [netbird.cloud] , Match list: [] 2024-05-13T12:47:15+02:00 WARN client/internal/dns/upstream.go:185: probing upstream nameserver 192.168.208.1:53: read udp 10.6.6.2:39320->192.168.208.1:53: i/o timeout 2024-05-13T12:47:16+02:00 INFO client/internal/routemanager/client.go:165: new chosen route is co1dqj3l0ubs739dfnsg with peer hCDjKQBW9TBwsZigTRXxvVzpAYE+ZqDHBol4sOSUMl0= with score 2.966603 for network 192.168.0.0/16 2024-05-13T12:47:16+02:00 INFO client/internal/peer/conn.go:388: connected to peer hCDjKQBW9TBwsZigTRXxvVzpAYE+ZqDHBol4sOSUMl0=, endpoint address: 185.199.30.141:9133 2024-05-13T12:47:17+02:00 INFO client/internal/peer/conn.go:388: connected to peer FfiyZKMquYILabBxOquw/jXEuTjhBq6tUvBEPdV3ckY=, endpoint address: 185.199.30.141:16269 2024-05-13T12:47:17+02:00 WARN client/internal/routemanager/client.go:120: peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= has 0 latency 2024-05-13T12:47:17+02:00 INFO client/internal/routemanager/client.go:165: new chosen route is co1kv3bl0ubs739dg130 with peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= with score 2.000000 for network 10.20.0.0/24 2024-05-13T12:47:17+02:00 WARN client/internal/routemanager/client.go:120: peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= has 0 latency 2024-05-13T12:47:17+02:00 INFO client/internal/routemanager/client.go:165: new chosen route is co1kuj3l0ubs739dg11g with peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= with score 2.000000 for network 10.30.0.0/24 2024-05-13T12:47:17+02:00 WARN client/internal/routemanager/client.go:120: peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= has 0 latency 2024-05-13T12:47:17+02:00 WARN client/internal/routemanager/client.go:120: peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= has 0 latency 2024-05-13T12:47:17+02:00 WARN client/internal/routemanager/client.go:120: peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= has 0 latency 2024-05-13T12:47:17+02:00 INFO client/internal/peer/conn.go:388: connected to peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE=, endpoint address: 145.236.15.52:51820 2024-05-13T12:47:18+02:00 INFO client/internal/peer/conn.go:388: connected to peer +i/q6dNa3AeF/iNJMH9+CbnsTLmFPfN+/K0KUPJI5wI=, endpoint address: 3.73.3.142:37959 2024-05-13T12:47:21+02:00 INFO client/internal/dns/upstream.go:241: upstreams [192.168.208.1:53] are responsive again. Adding them back to system 2024-05-13T12:47:21+02:00 INFO client/internal/dns/systemd_linux.go:144: adding 3 search domains and 0 match domains. Search list: [int.vidux.hu vidux.internal netbird.cloud] , Match list: [] ``` at 12:47:11: "network 10.30.0.0/24 has not been assigned a routing peer" is vaild but at 12:47:17 while listed: ``` 2024-05-13T12:47:17+02:00 WARN client/internal/routemanager/client.go:120: peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= has 0 latency 2024-05-13T12:47:17+02:00 INFO client/internal/routemanager/client.go:165: new chosen route is co1kuj3l0ubs739dg11g with peer 1u25Mrocd2aMv88fUgRnKmM1caynzX+bGTzThCZ3CnE= with score 2.000000 for network 10.30.0.0/24 ``` the routing rule never added....
saavagebueno added the clientroutes labels 2025-11-20 05:19:11 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label client routes
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#882
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?