SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-09 17:51:57 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Issues accessing a peer. 'No Connection to Host and route not allowed' #911

New Issue
Closed
opened 2025-11-20 05:19:45 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:19:45 -05:00
Owner
Copy Link

Originally created by @cmjdev on GitHub (May 20, 2024).

Describe the problem

I'm having an issue with communicating to a peer. All others are fine and pick up a direct p2p connection. This one shows relayed and active but I cannot access it. The logs show the following. Is there any indication to what the problem is? Is it a UDP firewall issue for this specific peer?

2024-05-20T10:04:20-04:00 ERRO util/net/dialer_nonios.go:64: Failed to call dialer hooks: failed to resolve address :51820: lookup : no such host
2024-05-20T10:04:20-04:00 DEBG client/internal/peer/conn.go:439: Conn resolved IP for 127.0.0.1:59933: 127.0.0.1
2024-05-20T10:04:20-04:00 DEBG client/internal/routemanager/routemanager.go:52: Increasing route ref count 0 for prefix 127.0.0.1/32
2024-05-20T10:04:20-04:00 DEBG client/internal/routemanager/routemanager.go:56: Adding route for prefix 127.0.0.1/32
2024-05-20T10:04:20-04:00 DEBG client/internal/routemanager/routemanager.go:62: Adding route for prefix 127.0.0.1/32: route not allowed
2024-05-20T10:04:20-04:00 ERRO client/internal/peer/conn.go:444: Before add peer hook failed: adding route reference: failed to add route for prefix 127.0.0.1/32: route not allowed

Expected behavior
We should have access to the peer but do not

Are you using NetBird Cloud?
Yes.

NetBird version
0.27.2

NetBird status -d output:

If applicable, add the `netbird status -d' command output.

Peers detail:
 cmj-niagara.netbird.cloud:
  NetBird IP: 100.109.53.41/32
  Public key: 76bCZH3kSjn2IghqWgb1ESFmYRVeLFST6Xz1ImkdlXs=
  Status: Disconnected
  -- detail --
  Connection type: Relayed
  Direct: false
  ICE candidate (Local/Remote): relay/srflx
  ICE candidate endpoints (Local/Remote): 3.130.8.114:49623/207.67.95.82:51820
  Last connection update: 18 minutes, 39 seconds ago
  Last WireGuard handshake: -
  Transfer status (received/sent) 0 B/17.3 KiB
  Quantum resistance: false
  Routes: -
  Latency: 0s

 alpine.netbird.cloud:
  NetBird IP: 100.109.252.84
  Public key: KzZWp1z0B10y8GFy1FNNaWL3HckDvIAXWX+smHMKoX8=
  Status: Connected
  -- detail --
  Connection type: Relayed
  Direct: false
  ICE candidate (Local/Remote): relay/srflx
  ICE candidate endpoints (Local/Remote): 3.130.8.114:49623/207.67.95.82:51820
  Last connection update: 11 minutes, 55 seconds ago
  Last WireGuard handshake: -
  Transfer status (received/sent) 0 B/17.3 KiB
  Quantum resistance: false
  Routes: -
  Latency: 46.7991ms

OS: windows/amd64
Daemon version: 0.27.7
CLI version: 0.27.7
Management: Connected to https://api.netbird.io:443
Signal: Connected to https://signal.netbird.io:443
Relays:
  [stun:stun.netbird.io:5555] is Available
  [turns:turn.netbird.io:443?transport=tcp] is Available
Nameservers:
FQDN: western.netbird.cloud
NetBird IP: 100.109.193.203/16
Interface type: Userspace
Quantum resistance: false
Routes: -
Peers count: 1/2 Connected

Additional context
All other peers set up exactly the same are working as intended

Originally created by @cmjdev on GitHub (May 20, 2024). **Describe the problem** I'm having an issue with communicating to a peer. All others are fine and pick up a direct p2p connection. This one shows relayed and active but I cannot access it. The logs show the following. Is there any indication to what the problem is? Is it a UDP firewall issue for this specific peer? ``` 2024-05-20T10:04:20-04:00 ERRO util/net/dialer_nonios.go:64: Failed to call dialer hooks: failed to resolve address :51820: lookup : no such host 2024-05-20T10:04:20-04:00 DEBG client/internal/peer/conn.go:439: Conn resolved IP for 127.0.0.1:59933: 127.0.0.1 2024-05-20T10:04:20-04:00 DEBG client/internal/routemanager/routemanager.go:52: Increasing route ref count 0 for prefix 127.0.0.1/32 2024-05-20T10:04:20-04:00 DEBG client/internal/routemanager/routemanager.go:56: Adding route for prefix 127.0.0.1/32 2024-05-20T10:04:20-04:00 DEBG client/internal/routemanager/routemanager.go:62: Adding route for prefix 127.0.0.1/32: route not allowed 2024-05-20T10:04:20-04:00 ERRO client/internal/peer/conn.go:444: Before add peer hook failed: adding route reference: failed to add route for prefix 127.0.0.1/32: route not allowed ``` **Expected behavior** We should have access to the peer but do not **Are you using NetBird Cloud?** Yes. **NetBird version** `0.27.2` **NetBird status -d output:** If applicable, add the `netbird status -d' command output. ``` Peers detail: cmj-niagara.netbird.cloud: NetBird IP: 100.109.53.41/32 Public key: 76bCZH3kSjn2IghqWgb1ESFmYRVeLFST6Xz1ImkdlXs= Status: Disconnected -- detail -- Connection type: Relayed Direct: false ICE candidate (Local/Remote): relay/srflx ICE candidate endpoints (Local/Remote): 3.130.8.114:49623/207.67.95.82:51820 Last connection update: 18 minutes, 39 seconds ago Last WireGuard handshake: - Transfer status (received/sent) 0 B/17.3 KiB Quantum resistance: false Routes: - Latency: 0s alpine.netbird.cloud: NetBird IP: 100.109.252.84 Public key: KzZWp1z0B10y8GFy1FNNaWL3HckDvIAXWX+smHMKoX8= Status: Connected -- detail -- Connection type: Relayed Direct: false ICE candidate (Local/Remote): relay/srflx ICE candidate endpoints (Local/Remote): 3.130.8.114:49623/207.67.95.82:51820 Last connection update: 11 minutes, 55 seconds ago Last WireGuard handshake: - Transfer status (received/sent) 0 B/17.3 KiB Quantum resistance: false Routes: - Latency: 46.7991ms OS: windows/amd64 Daemon version: 0.27.7 CLI version: 0.27.7 Management: Connected to https://api.netbird.io:443 Signal: Connected to https://signal.netbird.io:443 Relays: [stun:stun.netbird.io:5555] is Available [turns:turn.netbird.io:443?transport=tcp] is Available Nameservers: FQDN: western.netbird.cloud NetBird IP: 100.109.193.203/16 Interface type: Userspace Quantum resistance: false Routes: - Peers count: 1/2 Connected ``` **Additional context** All other peers set up exactly the same are working as intended
saavagebueno added the waiting-feedback label 2025-11-20 05:19:45 -05:00
saavagebueno commented 2025-11-20 05:19:46 -05:00
Author
Owner
Copy Link

@pascal-fischer commented on GitHub (May 21, 2024):

Hi @cmjdev,
the route errors are unrelated and will be hidden in a next PR. The issue seems to be wireguard. The peer is missing the handshake. We had a similar issue before. Can you make sure both peers are running netbird version 0.27.7? If it is still not working there might be a firewall issue blocking the handshake on either of the peers.

@pascal-fischer commented on GitHub (May 21, 2024): Hi @cmjdev, the route errors are unrelated and will be hidden in a next PR. The issue seems to be wireguard. The peer is missing the handshake. We had a similar issue before. Can you make sure both peers are running netbird version 0.27.7? If it is still not working there might be a firewall issue blocking the handshake on either of the peers.
saavagebueno commented 2025-11-20 05:19:46 -05:00
Author
Owner
Copy Link

@cmjdev commented on GitHub (Jun 13, 2024):

Hi @cmjdev, the route errors are unrelated and will be hidden in a next PR. The issue seems to be wireguard. The peer is missing the handshake. We had a similar issue before. Can you make sure both peers are running netbird version 0.27.7? If it is still not working there might be a firewall issue blocking the handshake on either of the peers.

Where is the handshake taking place? Port? This peer shows as connected locally and also shows in the dashboard. I'm trying to single this down so I can request firewall rules from the Customer.

The 'Last WireGuard handshake' is null so the connections are 'relayed' but no traffic is transferring. So is the wiregurad handshake happening over the UDP port range in the documentation? And furthermore if we're using CoTURN because we can't make the direct connection what firewall rules should I request be opened for that?

Thanks in advance!

@cmjdev commented on GitHub (Jun 13, 2024): > Hi @cmjdev, the route errors are unrelated and will be hidden in a next PR. The issue seems to be wireguard. The peer is missing the handshake. We had a similar issue before. Can you make sure both peers are running netbird version 0.27.7? If it is still not working there might be a firewall issue blocking the handshake on either of the peers. Where is the handshake taking place? Port? This peer shows as connected locally and also shows in the dashboard. I'm trying to single this down so I can request firewall rules from the Customer. The 'Last WireGuard handshake' is null so the connections are 'relayed' but no traffic is transferring. So is the wiregurad handshake happening over the UDP port range in the documentation? And furthermore if we're using CoTURN because we can't make the direct connection what firewall rules should I request be opened for that? Thanks in advance!
saavagebueno commented 2025-11-20 05:19:46 -05:00
Author
Owner
Copy Link

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

@cmjdev were you able to resolve your issue or is it still happening on latest Netbird version?

@nazarewk commented on GitHub (Apr 23, 2025): @cmjdev were you able to resolve your issue or is it still happening on latest Netbird version?
saavagebueno commented 2025-11-20 05:19:46 -05:00
Author
Owner
Copy Link

@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.
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 waiting-feedback
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#911
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?