[GH-ISSUE #2124] Option to Mark Peers as Ineligible for Routing #4364

Open
opened 2026-08-05 00:57:18 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @marcportabellaclotet-mt on GitHub (Jun 13, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2124

Description:

I would like to request an enhancement that allows marking a peer as ineligible to be used as a routing peer. This feature would improve security by ensuring that certain peers cannot be used to route traffic, thereby preventing unauthorized network exploration.

Use Case:
Currently, all peers connected to NetBird can potentially be used as routing peers. This poses a security risk where an administrator might intentionally add a route to connect and explore another peer's network, which may not be desirable for some users.

Proposed Solution:
Introduce an option in the peer configuration settings that allows administrators to mark a peer as "ineligible for routing". When this option is enabled for a peer:

  • The peer cannot be used as an intermediary to route traffic for other peers.
  • This setting should be configurable at the time of peer creation and not adjustable later by administrators.

Benefits:

  • Enhances security by providing control over which peers can be used for routing.
  • Protects sensitive networks from unauthorized access and exploration.
Originally created by @marcportabellaclotet-mt on GitHub (Jun 13, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2124 **Description:** I would like to request an enhancement that allows marking a peer as ineligible to be used as a routing peer. This feature would improve security by ensuring that certain peers cannot be used to route traffic, thereby preventing unauthorized network exploration. **Use Case:** Currently, all peers connected to NetBird can potentially be used as routing peers. This poses a security risk where an administrator might intentionally add a route to connect and explore another peer's network, which may not be desirable for some users. **Proposed Solution:** Introduce an option in the peer configuration settings that allows administrators to mark a peer as "ineligible for routing". When this option is enabled for a peer: - The peer cannot be used as an intermediary to route traffic for other peers. - This setting should be configurable at the time of peer creation and not adjustable later by administrators. **Benefits:** - Enhances security by providing control over which peers can be used for routing. - Protects sensitive networks from unauthorized access and exploration.
saavagebueno added the feature-request label 2026-08-05 00:57:18 -04:00
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#4364