[GH-ISSUE #2563] Unable to connect via P2P even public IPv4 is available #5444

Open
opened 2026-08-05 01:03:15 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @Integral-Tech on GitHub (Sep 9, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2563

Describe the problem

I am pretty sure that one of my peers has public IPv4 address, however I fail to connect two peers via P2P.

  • Peer 1: Arch Linux (without public IPv4)
  • Peer 2: OpenWrt (with public IPv4)

To Reproduce

Steps to reproduce the behavior:

  1. Start Netbird service on two peers (one of them has public IPv4 address)
  2. Run netbird status -d

Expected behavior

  Status: Connected
  -- detail --
  Connection type: P2P
  Direct: true

Are you using NetBird Cloud?

Yes

NetBird version

0.28.9

NetBird status -dA output:

Peers detail:
 *.netbird.cloud:
  NetBird IP: *
  Public key: *
  Status: Connected
  -- detail --
  Connection type: Relayed
  Direct: true
  ICE candidate (Local/Remote): host/relay
  ICE candidate endpoints (Local/Remote): *
  Last connection update: 14 seconds ago
  Last WireGuard handshake: -
  Transfer status (received/sent) 444 B/424 B
  Quantum resistance: false
  Routes: 192.168.0.0/16
  Latency: 426.126669ms

OS: linux/amd64
Daemon version: 0.28.9
CLI version: 0.28.9
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: *.netbird.cloud
NetBird IP: *
Interface type: Kernel
Quantum resistance: false
Routes: -
Peers count: 1/1 Connected
Originally created by @Integral-Tech on GitHub (Sep 9, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2563 **Describe the problem** I am pretty sure that one of my peers has public IPv4 address, however I fail to connect two peers via P2P. - Peer 1: Arch Linux (without public IPv4) - Peer 2: OpenWrt (with public IPv4) **To Reproduce** Steps to reproduce the behavior: 1. Start Netbird service on two peers (one of them has public IPv4 address) 2. Run ```netbird status -d``` **Expected behavior** ``` Status: Connected -- detail -- Connection type: P2P Direct: true ``` **Are you using NetBird Cloud?** Yes **NetBird version** 0.28.9 **NetBird status -dA output:** ``` Peers detail: *.netbird.cloud: NetBird IP: * Public key: * Status: Connected -- detail -- Connection type: Relayed Direct: true ICE candidate (Local/Remote): host/relay ICE candidate endpoints (Local/Remote): * Last connection update: 14 seconds ago Last WireGuard handshake: - Transfer status (received/sent) 444 B/424 B Quantum resistance: false Routes: 192.168.0.0/16 Latency: 426.126669ms OS: linux/amd64 Daemon version: 0.28.9 CLI version: 0.28.9 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: *.netbird.cloud NetBird IP: * Interface type: Kernel Quantum resistance: false Routes: - Peers count: 1/1 Connected ```
saavagebueno added the bugtriage-needed labels 2026-08-05 01:03:15 -04:00
Sign in to join this conversation.
No Label bug triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#5444