SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-06-10 09:22:09 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Features Request: Peer Approval, Client Logout, Simplified DNS Resolution, Remote Management, Resources Tab #464

New Issue
Open
opened 2025-11-20 05:11:50 -05:00 by saavagebueno · 6 comments
saavagebueno commented 2025-11-20 05:11:50 -05:00
Owner
Copy Link

Originally created by @hotline007 on GitHub (Oct 8, 2023).

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

@braginini commented on GitHub (Oct 9, 2023):

Hey @hotline007
Thank you very much for submitting this request. The features are definitely something that we should implement. We will review it.

FYI: Also responded on Slack to you.

@braginini commented on GitHub (Oct 9, 2023): Hey @hotline007 Thank you very much for submitting this request. The features are definitely something that we should implement. We will review it. FYI: Also responded on Slack to you.
saavagebueno commented 2025-11-20 05:11:51 -05:00
Author
Owner
Copy Link

@hotline007 commented on GitHub (Oct 11, 2023):

@braginini You are welcome, and looking forward

@hotline007 commented on GitHub (Oct 11, 2023): @braginini You are welcome, and looking forward
saavagebueno commented 2025-11-20 05:11:51 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Oct 15, 2023):

Hello @hotline007, thanks for submitting this request. We are looking into our roadmap and should have an ETA for you in the coming weeks.

We do have some questions and notes about the point; please see below:

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

How do you see the approval process once the peer is added to the queue? Would it be easier to have a Dashboard (API) option for it?

We've seen other solutions approving new clients via management consoles or via other existing clients.

2- Enhance user flexibility by allowing multiple account logins.

We are looking into adding multiple login profiles in our UI and CLI clients, making it easier to switch accounts.

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

This is already part of our DNS feature for peer domain names. If it fails for you, please open another issue for us to check if it is a bug.

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

We will take a few steps to integrate this into our NetBird management system. Now, we are working on an upgrade notification feature for Windows and MacOS clients. Once this is available, we will evaluate the best option for triggering the deployment from the dashboard or making it fully automated on the client side.

In any case, currently, we are relying on a few things to make the upgrade easier for large-scale deployments:

  1. For Windows, we have MSI that can be easily integrated with RMM/MDM tools
  2. MacOS offers installation packages (.pkg) and homebrew options as well that can facilitate
  3. On Linux, we have Debian and RedHat packages that already offer some form of automated updates depending on the package manager settings.

5- Dedicated 'Resources Tab' for Service Management.

How do you see service + domain names for this feature?

We would love to discuss this in detail; if you have the time, please reach out in slack.

@mlsmaycon commented on GitHub (Oct 15, 2023): Hello @hotline007, thanks for submitting this request. We are looking into our roadmap and should have an ETA for you in the coming weeks. We do have some questions and notes about the point; please see below: > 1- Enhance network security by introducing a peer approval process. How do you see the approval process once the peer is added to the queue? Would it be easier to have a Dashboard (API) option for it? We've seen other solutions approving new clients via management consoles or via other existing clients. > 2- Enhance user flexibility by allowing multiple account logins. We are looking into adding multiple login profiles in our UI and CLI clients, making it easier to switch accounts. > 3- Enhance usability by allowing the resolution of peer names without requiring the full FQDN. This is already part of our DNS feature for peer domain names. If it fails for you, please open another issue for us to check if it is a bug. > 4- Streamline the update process for large-scale deployments. We will take a few steps to integrate this into our NetBird management system. Now, we are working on an upgrade notification feature for Windows and MacOS clients. Once this is available, we will evaluate the best option for triggering the deployment from the dashboard or making it fully automated on the client side. In any case, currently, we are relying on a few things to make the upgrade easier for large-scale deployments: 1. For Windows, we have MSI that can be easily integrated with RMM/MDM tools 2. MacOS offers installation packages (.pkg) and homebrew options as well that can facilitate 3. On Linux, we have Debian and RedHat packages that already offer some form of automated updates depending on the package manager settings. > 5- Dedicated 'Resources Tab' for Service Management. How do you see service + domain names for this feature? We would love to discuss this in detail; if you have the time, please reach out in slack.
saavagebueno commented 2025-11-20 05:11:51 -05:00
Author
Owner
Copy Link

@hotline007 commented on GitHub (Oct 21, 2023):

Hi @mlsmaycon

Please check my answers below:

How do you see the approval process once the peer is added to the queue? Would it be easier to have a Dashboard (API) option for it?

Admins should approve peers via the NetBird Dashboard. Let's add MFA for extra security during approvals. Admins get email alerts and real-time portal notifications for new requests

How do you see service + domain names for this feature?

Can you explain more about this?

Thanks

@hotline007 commented on GitHub (Oct 21, 2023): Hi @mlsmaycon Please check my answers below: > How do you see the approval process once the peer is added to the queue? Would it be easier to have a Dashboard (API) option for it? Admins should approve peers via the NetBird Dashboard. Let's add MFA for extra security during approvals. Admins get email alerts and real-time portal notifications for new requests > How do you see service + domain names for this feature? Can you explain more about this? Thanks
saavagebueno commented 2025-11-20 05:11:52 -05:00
Author
Owner
Copy Link

@mlsmaycon commented on GitHub (Oct 21, 2023):

Thanks for the feedback @hotline007

Regarding the service + domains. As we would expose an internal resource, we are thinking how the end user would access a particular service like a database or web service. The initial thought is to use a domain for it, which potentially is managed by NetBird as well, similar to peers domains but more flexible.

@mlsmaycon commented on GitHub (Oct 21, 2023): Thanks for the feedback @hotline007 Regarding the service + domains. As we would expose an internal resource, we are thinking how the end user would access a particular service like a database or web service. The initial thought is to use a domain for it, which potentially is managed by NetBird as well, similar to peers domains but more flexible.
saavagebueno commented 2025-11-20 05:11:52 -05:00
Author
Owner
Copy Link

@gabriel-henriq commented on GitHub (Apr 18, 2024):

@mlsmaycon , when I attempt to Netbird at first, I thought that I could achieve the "Resource" functionality like that one that exists on Twingate.

image

I think that the @hotline007 said that when he said about the:

Dedicated 'Resources Tab' for Service Management.

If the Netbird could resolve Resources like the Twingate does, it would be a great feature for everyone.

There an thread opened on Slack also here and here.

@gabriel-henriq commented on GitHub (Apr 18, 2024): @mlsmaycon , when I attempt to Netbird at first, I thought that I could achieve the "[Resource](https://www.twingate.com/docs/resources)" functionality like that one that exists on Twingate. ![image](https://github.com/netbirdio/netbird/assets/67342474/2b7ed04b-263a-42a9-b82f-b1dfb50951f4) I think that the @hotline007 said that when he said about the: > Dedicated 'Resources Tab' for Service Management. If the Netbird could resolve Resources like the Twingate does, it would be a great feature for everyone. There an thread opened on Slack also [here](https://netbirdio.slack.com/archives/C05T5K65X7U/p1711663349104359) and [here](https://netbirdio.slack.com/archives/C05T5K65X7U/p1712172649087079).
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 enhancement feature-request
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#464
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?