SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-05-20 07:02:12 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

New network concept, peers seem to try to connect to themselves #1540

New Issue
Closed
opened 2025-11-20 05:32:29 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:32:29 -05:00
Owner
Copy Link

Originally created by @Gauss23 on GitHub (Jan 2, 2025).

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). **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 2025-11-20 05:32:29 -05:00
saavagebueno commented 2025-11-20 05:32:30 -05:00
Author
Owner
Copy Link

@pascal-fischer commented on GitHub (Jan 3, 2025):

Hi @Gauss23,
thank you for reporting this issue. We are aware and have created a fix with https://github.com/netbirdio/netbird/pull/3142. This fix will be released soon

@pascal-fischer commented on GitHub (Jan 3, 2025): Hi @Gauss23, thank you for reporting this issue. We are aware and have created a fix with https://github.com/netbirdio/netbird/pull/3142. This fix will be released soon
saavagebueno commented 2025-11-20 05:32:30 -05:00
Author
Owner
Copy Link

@v1rusnl commented on GitHub (Jan 8, 2025):

Same here, happy to see already a fix for it!

@v1rusnl commented on GitHub (Jan 8, 2025): Same here, happy to see already a fix for it!
saavagebueno commented 2025-11-20 05:32:30 -05:00
Author
Owner
Copy Link

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

Hello @Gauss23,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

@nazarewk commented on GitHub (Apr 28, 2025): Hello @Gauss23, We're currently reviewing our open issues and would like to verify if this problem still exists in the [latest NetBird version](https://github.com/netbirdio/netbird/releases). Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within **2 weeks**, but feel free to reopen it with updated information. Thanks for your contribution to improving the project!
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 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#1540
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?