SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-29 17:32:35 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Unable to connect to netbird peer on differnt LAN with the same public IP #1813

New Issue
Open
opened 2025-11-20 06:07:15 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 06:07:15 -05:00
Owner
Copy Link

Originally created by @bpnevells on GitHub (Apr 14, 2025).

Hello,

Hugh fan of the Netbird project.

I have all of my internal services running in a dedicated network, let's call it LAN.
I have other Netbird peers running on a different separated network, let's call it IOT-LAN. Both networks share the same WAN. Running a OPNsence instance, and is behind CG-NAT.

Some of my NetBird agents located in the IOT-LAN are unable to connect the the Netbird peers located in the LAN. All peers from outside the network, such as on the internet are able to connect to the peers in the LAN with no problems.

I suspect this is an issue with the relay service. " [rels://relay.netbird.io:443] is Unavailable, reason: relay client not connected"

Expected behavior

Are you using NetBird Cloud? - Yes

NetBird version - V0.41.0

Is any other VPN software installed? - No

Debug output

"Peers detail:
iphone-nevellsb.netbird.cloud:
NetBird IP: 100.72.5.10
Public key: q4jsleN8mYGANXW+KP+7XDQoA+6Hz34ZaX70Dc/fzWI=
Status: Connected
-- detail --
Connection type: Relayed
ICE candidate (Local/Remote): host/relay
ICE candidate endpoints (Local/Remote): 127.0.0.1:51820/198.51.100.0:12132
Relay server address:
Last connection update: 14 minutes, 16 seconds ago
Last WireGuard handshake: 1 minute, 43 seconds ago
Transfer status (received/sent) 900 B/2.3 KiB
Quantum resistance: false
Networks: -
Latency: 242.2069ms

birdcon-1.netbird.cloud:
NetBird IP: 100.72.105.244
Public key: LglatLZGN0L2YyrpwgvoCjiBSg0xojq4zBHfx4imzwU=
Status: Connected
-- detail --
Connection type: Relayed
ICE candidate (Local/Remote): srflx/relay
ICE candidate endpoints (Local/Remote): 198.51.100.1:11666/198.51.100.2:32911
Relay server address:
Last connection update: 14 minutes, 16 seconds ago
Last WireGuard handshake: 1 minute, 44 seconds ago
Transfer status (received/sent) 644 B/2.3 KiB
Quantum resistance: false
Networks: 192.168.6.0/24
Latency: 206.321ms

web-03-clone.netbird.cloud:
NetBird IP: 100.72.111.7
Public key: IAJShlSwmqhb/Bg/P5gBqc5Q/YIZLTKrKcsfVRAYlBE=
Status: Connected
-- detail --
Connection type: Relayed
ICE candidate (Local/Remote): host/relay
ICE candidate endpoints (Local/Remote): 127.0.0.1:51820/198.51.100.3:50323
Relay server address:
Last connection update: 14 minutes, 15 seconds ago
Last WireGuard handshake: 1 minute, 43 seconds ago
Transfer status (received/sent) 644 B/2.3 KiB
Quantum resistance: false
Networks: -
Latency: 376.556ms

lab-birdconnect.netbird.cloud:
NetBird IP: 100.72.124.247
Public key: 3ExFJeUc9Wxk9vNOmzIHr0YAR9+7CTDEqJirN8YORTk=
Status: Disconnected
-- detail --
Connection type:
ICE candidate (Local/Remote): -/-
ICE candidate endpoints (Local/Remote): -/-
Relay server address:
Last connection update: -
Last WireGuard handshake: -
Transfer status (received/sent) 0 B/0 B
Quantum resistance: false
Networks: -
Latency: 0s

Events:
[INFO] SYSTEM (18e75b94-707d-4853-bec8-2b8da58497b9)
Message: Network map updated
Time: 2 hours, 8 minutes ago
[INFO] SYSTEM (5e2a503a-10f8-4e9f-89b1-dc88924ba92b)
Message: Network map updated
Time: 1 hour, 59 minutes ago
[INFO] SYSTEM (e078dde9-be79-44b5-9b02-cfa6bcac6696)
Message: Network map updated
Time: 1 hour, 32 minutes ago
[INFO] SYSTEM (06c74158-794b-4477-87b9-84603a03d8cd)
Message: Network map updated
Time: 1 hour, 28 minutes ago
[INFO] SYSTEM (634a310f-c235-494b-ab09-83cc5dfa6294)
Message: Network map updated
Time: 1 hour, 21 minutes ago
[INFO] SYSTEM (b9996879-7ed7-41e0-8102-088c07a28e54)
Message: Network map updated
Time: 1 hour, 20 minutes ago
[INFO] SYSTEM (2d465aa0-c2f9-48b6-b07f-ffa366bef611)
Message: Network map updated
Time: 1 hour, 18 minutes ago
[INFO] SYSTEM (49e41599-0bb0-4c14-bacc-1059cfcb789f)
Message: Network map updated
Time: 1 hour, 18 minutes ago
[INFO] SYSTEM (ca271077-f423-4ccd-be7c-012428b53ef7)
Message: Network map updated
Time: 52 minutes, 47 seconds ago
[INFO] SYSTEM (7819bb89-1ef6-4736-8dd5-489018e66830)
Message: Network map updated
Time: 14 minutes, 19 seconds ago
OS: windows/amd64
Daemon version: 0.41.0
CLI version: 0.41.0
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
[rels://relay.netbird.io:443] is Unavailable, reason: relay client not connected
Nameservers:
FQDN: laptop-hoeekb4b.netbird.cloud
NetBird IP: 100.72.155.197/16
Interface type: Userspace
Quantum resistance: false
Networks: -
Forwarding rules: 0
Peers count: 3/4 Connected"

netbird.debug.3916181182 (2).zip

Originally created by @bpnevells on GitHub (Apr 14, 2025). Hello, Hugh fan of the Netbird project. I have all of my internal services running in a dedicated network, let's call it LAN. I have other Netbird peers running on a different separated network, let's call it IOT-LAN. Both networks share the same WAN. Running a OPNsence instance, and is behind CG-NAT. Some of my NetBird agents located in the IOT-LAN are unable to connect the the Netbird peers located in the LAN. All peers from outside the network, such as on the internet are able to connect to the peers in the LAN with no problems. I suspect this is an issue with the relay service. " [rels://relay.netbird.io:443] is Unavailable, reason: relay client not connected" **Expected behavior** Are you using NetBird Cloud? - Yes NetBird version - V0.41.0 Is any other VPN software installed? - No **Debug output** "Peers detail: iphone-nevellsb.netbird.cloud: NetBird IP: 100.72.5.10 Public key: q4jsleN8mYGANXW+KP+7XDQoA+6Hz34ZaX70Dc/fzWI= Status: Connected -- detail -- Connection type: Relayed ICE candidate (Local/Remote): host/relay ICE candidate endpoints (Local/Remote): 127.0.0.1:51820/198.51.100.0:12132 Relay server address: Last connection update: 14 minutes, 16 seconds ago Last WireGuard handshake: 1 minute, 43 seconds ago Transfer status (received/sent) 900 B/2.3 KiB Quantum resistance: false Networks: - Latency: 242.2069ms birdcon-1.netbird.cloud: NetBird IP: 100.72.105.244 Public key: LglatLZGN0L2YyrpwgvoCjiBSg0xojq4zBHfx4imzwU= Status: Connected -- detail -- Connection type: Relayed ICE candidate (Local/Remote): srflx/relay ICE candidate endpoints (Local/Remote): 198.51.100.1:11666/198.51.100.2:32911 Relay server address: Last connection update: 14 minutes, 16 seconds ago Last WireGuard handshake: 1 minute, 44 seconds ago Transfer status (received/sent) 644 B/2.3 KiB Quantum resistance: false Networks: 192.168.6.0/24 Latency: 206.321ms web-03-clone.netbird.cloud: NetBird IP: 100.72.111.7 Public key: IAJShlSwmqhb/Bg/P5gBqc5Q/YIZLTKrKcsfVRAYlBE= Status: Connected -- detail -- Connection type: Relayed ICE candidate (Local/Remote): host/relay ICE candidate endpoints (Local/Remote): 127.0.0.1:51820/198.51.100.3:50323 Relay server address: Last connection update: 14 minutes, 15 seconds ago Last WireGuard handshake: 1 minute, 43 seconds ago Transfer status (received/sent) 644 B/2.3 KiB Quantum resistance: false Networks: - Latency: 376.556ms lab-birdconnect.netbird.cloud: NetBird IP: 100.72.124.247 Public key: 3ExFJeUc9Wxk9vNOmzIHr0YAR9+7CTDEqJirN8YORTk= Status: Disconnected -- detail -- Connection type: ICE candidate (Local/Remote): -/- ICE candidate endpoints (Local/Remote): -/- Relay server address: Last connection update: - Last WireGuard handshake: - Transfer status (received/sent) 0 B/0 B Quantum resistance: false Networks: - Latency: 0s Events: [INFO] SYSTEM (18e75b94-707d-4853-bec8-2b8da58497b9) Message: Network map updated Time: 2 hours, 8 minutes ago [INFO] SYSTEM (5e2a503a-10f8-4e9f-89b1-dc88924ba92b) Message: Network map updated Time: 1 hour, 59 minutes ago [INFO] SYSTEM (e078dde9-be79-44b5-9b02-cfa6bcac6696) Message: Network map updated Time: 1 hour, 32 minutes ago [INFO] SYSTEM (06c74158-794b-4477-87b9-84603a03d8cd) Message: Network map updated Time: 1 hour, 28 minutes ago [INFO] SYSTEM (634a310f-c235-494b-ab09-83cc5dfa6294) Message: Network map updated Time: 1 hour, 21 minutes ago [INFO] SYSTEM (b9996879-7ed7-41e0-8102-088c07a28e54) Message: Network map updated Time: 1 hour, 20 minutes ago [INFO] SYSTEM (2d465aa0-c2f9-48b6-b07f-ffa366bef611) Message: Network map updated Time: 1 hour, 18 minutes ago [INFO] SYSTEM (49e41599-0bb0-4c14-bacc-1059cfcb789f) Message: Network map updated Time: 1 hour, 18 minutes ago [INFO] SYSTEM (ca271077-f423-4ccd-be7c-012428b53ef7) Message: Network map updated Time: 52 minutes, 47 seconds ago [INFO] SYSTEM (7819bb89-1ef6-4736-8dd5-489018e66830) Message: Network map updated Time: 14 minutes, 19 seconds ago OS: windows/amd64 Daemon version: 0.41.0 CLI version: 0.41.0 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 [rels://relay.netbird.io:443] is Unavailable, reason: relay client not connected Nameservers: FQDN: laptop-hoeekb4b.netbird.cloud NetBird IP: 100.72.155.197/16 Interface type: Userspace Quantum resistance: false Networks: - Forwarding rules: 0 Peers count: 3/4 Connected" [netbird.debug.3916181182 (2).zip](https://github.com/user-attachments/files/19729859/netbird.debug.3916181182.2.zip)
saavagebueno added the triage-needed label 2025-11-20 06:07:15 -05:00
saavagebueno commented 2025-11-20 06:07:16 -05:00
Author
Owner
Copy Link

@lixmal commented on GitHub (Apr 14, 2025):

Hi @bpnevells,

You are right about this:

I suspect this is an issue with the relay service. " [rels://relay.netbird.io:443] is Unavailable, reason: relay client not connected"

According to the log, the client times out when connecting.
Is there a firewall that could block it? The relay uses websocket as protocol

@lixmal commented on GitHub (Apr 14, 2025): Hi @bpnevells, You are right about this: >I suspect this is an issue with the relay service. " [rels://relay.netbird.io:443] is Unavailable, reason: relay client not connected" According to the log, the client times out when connecting. Is there a firewall that could block it? The relay uses websocket as protocol
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 triage-needed
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#1813
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?