[GH-ISSUE #3145] New network concept, peers seem to try to connect to themselves #6475

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

Originally created by @Gauss23 on GitHub (Jan 2, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3145

Describe the problem

When trying to migrate from Network Routes to Networks, I see that the nodes involved are trying to connect to themselves as loopback

To Reproduce

Steps to reproduce the behavior:

  1. Go to 'Networks'
  2. Create a new network
  3. Create a CIDR resource
  4. add a policy, where the source is a peer or a group of peers (not including the routing peer) and the destination is just an empty group
  5. check the connected peers, the routing peer will have itself as a peer it wants to connect to

Expected behavior

Peers should not do loopback to themself

Are you using NetBird Cloud?

Self-hosted

NetBird version

0.35.2

NetBird status -dA output:

netbird status -dA
Peers detail:
test.nb.anon-iahJA.domain:
NetBird IP: 100.65.50.222
Public key: KLPf1TNWZmXdsuh/COLtja0kcHL8s86rVfYA38pHLg8=
Status: Connected
-- detail --
Connection type: Relayed
ICE candidate (Local/Remote): -/-
ICE candidate endpoints (Local/Remote): -/-
Relay server address: rels://nb-hub.anon-BT4rV.domain:443
Last connection update: 34 seconds ago
Last WireGuard handshake: -
Transfer status (received/sent) 0 B/0 B
Quantum resistance: true
Routes: -
Networks: -
Latency: 0s

opn-test.nb.anon-iahJA.domain:
NetBird IP: 100.65.185.200
Public key: ulZHQG4FWQ8cBIq84XYTC3vKIZ2oO200l4R9ncR9EEU=
Status: Connected
-- detail --
Connection type: P2P
ICE candidate (Local/Remote): srflx/host
ICE candidate endpoints (Local/Remote): 198.51.100.0:23944/10.1.1.178:51820
Relay server address: rels://nb-hub.anon-BT4rV.domain:443
Last connection update: 45 seconds ago
Last WireGuard handshake: 40 seconds ago
Transfer status (received/sent) 53.6 KiB/21.0 KiB
Quantum resistance: true
Routes: -
Networks: -
Latency: 17.987698ms

OS: linux/amd64
Daemon version: 0.35.2
CLI version: 0.35.2
Management: Connected to https://nb-hub.anon-BT4rV.domain:443
Signal: Connected to https://nb-hub.anon-BT4rV.domain:443
Relays:
[stun:nb-hub.anon-BT4rV.domain:3478] is Available
[turn:nb-hub.anon-BT4rV.domain:3478?transport=udp] is Available
[rels://nb-hub.anon-BT4rV.domain:443] is Available
Nameservers:
FQDN: test.nb.anon-iahJA.domain
NetBird IP: 100.65.50.222/16
Interface type: Kernel
Quantum resistance: true (permissive)
Routes: 192.168.1.0/24
Networks: 192.168.1.0/24
Peers count: 2/2 Connected

Originally created by @Gauss23 on GitHub (Jan 2, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3145 **Describe the problem** When trying to migrate from Network Routes to Networks, I see that the nodes involved are trying to connect to themselves as loopback **To Reproduce** Steps to reproduce the behavior: 1. Go to 'Networks' 2. Create a new network 3. Create a CIDR resource 4. add a policy, where the source is a peer or a group of peers (not including the routing peer) and the destination is just an empty group 5. check the connected peers, the routing peer will have itself as a peer it wants to connect to **Expected behavior** Peers should not do loopback to themself **Are you using NetBird Cloud?** Self-hosted **NetBird version** `0.35.2` **NetBird status -dA output:** netbird status -dA Peers detail: test.nb.anon-iahJA.domain: NetBird IP: 100.65.50.222 Public key: KLPf1TNWZmXdsuh/COLtja0kcHL8s86rVfYA38pHLg8= Status: Connected -- detail -- Connection type: Relayed ICE candidate (Local/Remote): -/- ICE candidate endpoints (Local/Remote): -/- Relay server address: rels://nb-hub.anon-BT4rV.domain:443 Last connection update: 34 seconds ago Last WireGuard handshake: - Transfer status (received/sent) 0 B/0 B Quantum resistance: true Routes: - Networks: - Latency: 0s opn-test.nb.anon-iahJA.domain: NetBird IP: 100.65.185.200 Public key: ulZHQG4FWQ8cBIq84XYTC3vKIZ2oO200l4R9ncR9EEU= Status: Connected -- detail -- Connection type: P2P ICE candidate (Local/Remote): srflx/host ICE candidate endpoints (Local/Remote): 198.51.100.0:23944/10.1.1.178:51820 Relay server address: rels://nb-hub.anon-BT4rV.domain:443 Last connection update: 45 seconds ago Last WireGuard handshake: 40 seconds ago Transfer status (received/sent) 53.6 KiB/21.0 KiB Quantum resistance: true Routes: - Networks: - Latency: 17.987698ms OS: linux/amd64 Daemon version: 0.35.2 CLI version: 0.35.2 Management: Connected to https://nb-hub.anon-BT4rV.domain:443 Signal: Connected to https://nb-hub.anon-BT4rV.domain:443 Relays: [stun:nb-hub.anon-BT4rV.domain:3478] is Available [turn:nb-hub.anon-BT4rV.domain:3478?transport=udp] is Available [rels://nb-hub.anon-BT4rV.domain:443] is Available Nameservers: FQDN: test.nb.anon-iahJA.domain NetBird IP: 100.65.50.222/16 Interface type: Kernel Quantum resistance: true (permissive) Routes: 192.168.1.0/24 Networks: 192.168.1.0/24 Peers count: 2/2 Connected
saavagebueno added the waiting-feedbacktriage-needed labels 2026-08-05 01:08:31 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#6475