[GH-ISSUE #1202] Features Request: Peer Approval, Client Logout, Simplified DNS Resolution, Remote Management, Resources Tab #1859

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

Originally created by @hotline007 on GitHub (Oct 8, 2023).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1202

Hi Team,
Thank you for your exceptional contributions to this project. Your unique efforts are greatly appreciated.
I've been diving deep into NetBird over the past few months, and there are a few features I feel might be great additions. I hope you'll consider them for future updates.

1- Enhance network security by introducing a peer approval process.

  • Introduce an approval mechanism for new peers trying to join the Netbird network.
  • Upon attempting to connect, new devices, whether via SSO login or access keys, should be notified that their connection is pending approval.
  • Devices in the approval queue should be restricted from sending or receiving traffic.
    This ensures that only trusted devices, like servers, workstations, laptops, or phones, access the secure network.

2- Enhance user flexibility by allowing multiple account logins.

  • Currently, the NetBird client supports only one active user login.
  • For practical purposes, users may need to connect to different NetBird networks.
  • While deleting the client config file prompts reauthentication, a seamless multi-account login feature would be more efficient.
    This feature would eliminate the need to delete any files for account switches.

3- Enhance usability by allowing the resolution of peer names without requiring the full FQDN.

  • Currently, the NetBird client resolves the full FQDN of peers.
  • Given that each NetBird client possesses an integrated DNS server, enabling resolution using only the peer name would streamline the process. This adjustment could lead to a more user-friendly experience.

4- Streamline the update process for large-scale deployments.

  • Currently, updating the NetBird desktop client requires uninstalling the old version and installing the new one.
  • While feasible for a few clients, this method becomes a pain for larger deployments (e.g., 100-200 users).
    Implementing a remote update management system would address this challenge, ensuring smooth transitions to newer versions.

5- Dedicated 'Resources Tab' for Service Management.

  • The 'Resources Tab' should consolidate and display company-specific private services (e.g., web, SSH, RDP, and so on).
  • Rather than showing all peers to every user, allow administrators to define and assign user or group-specific visibility.
    This structure would provide more control, preventing users from accessing or even seeing non-relevant peers, such as routing peers.

I hope these suggestions are helpful. Looking forward to an ETA for these features.
Regards

Originally created by @hotline007 on GitHub (Oct 8, 2023). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1202 **Hi Team, Thank you for your exceptional contributions to this project. Your unique efforts are greatly appreciated. I've been diving deep into NetBird over the past few months, and there are a few features I feel might be great additions. I hope you'll consider them for future updates.** **1- Enhance network security by introducing a peer approval process.** - Introduce an approval mechanism for new peers trying to join the Netbird network. - Upon attempting to connect, new devices, whether via SSO login or access keys, should be notified that their connection is pending approval. - Devices in the approval queue should be restricted from sending or receiving traffic. This ensures that only trusted devices, like servers, workstations, laptops, or phones, access the secure network. **2- Enhance user flexibility by allowing multiple account logins.** - Currently, the NetBird client supports only one active user login. - For practical purposes, users may need to connect to different NetBird networks. - While deleting the client config file prompts reauthentication, a seamless multi-account login feature would be more efficient. This feature would eliminate the need to delete any files for account switches. **3- Enhance usability by allowing the resolution of peer names without requiring the full FQDN.** - Currently, the NetBird client resolves the full FQDN of peers. - Given that each NetBird client possesses an integrated DNS server, enabling resolution using only the peer name would streamline the process. This adjustment could lead to a more user-friendly experience. **4- Streamline the update process for large-scale deployments.** - Currently, updating the NetBird desktop client requires uninstalling the old version and installing the new one. - While feasible for a few clients, this method becomes a pain for larger deployments (e.g., 100-200 users). Implementing a remote update management system would address this challenge, ensuring smooth transitions to newer versions. **5- Dedicated 'Resources Tab' for Service Management.** - The 'Resources Tab' should consolidate and display company-specific private services (e.g., web, SSH, RDP, and so on). - Rather than showing all peers to every user, allow administrators to define and assign user or group-specific visibility. This structure would provide more control, preventing users from accessing or even seeing non-relevant peers, such as routing peers. I hope these suggestions are helpful. Looking forward to an ETA for these features. Regards
saavagebueno added the enhancementfeature-request labels 2026-08-05 00:44:15 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#1859