Ability to add plain wireguard clients #1195

Closed
opened 2025-11-20 05:25:43 -05:00 by saavagebueno · 5 comments
Owner

Originally created by @Silex on GitHub (Aug 30, 2024).

Is your feature request related to a problem? Please describe.

We have old routers where running netbird is problematic. But wireguard is supported.

Describe the solution you'd like

A way to add a peer using a plain wireguard config. Bonus points if there is QR Code.

Netmaker seems to support it https://www.netmaker.io/resources/wireguard#toc-generating-a-qr-code-for-mobile-client-setup

Describe alternatives you've considered

Having a machine that hosts https://github.com/wg-easy/wg-easy, have the old routers connect there, install netbird on the machine and use it as a network route to the wireguard range.

Additional context

Netbird is awesome and much more mature than Netmaker, it's the only feature missing to make it surpass Netmaker in every area.

Originally created by @Silex on GitHub (Aug 30, 2024). **Is your feature request related to a problem? Please describe.** We have old routers where running netbird is problematic. But wireguard is supported. **Describe the solution you'd like** A way to add a peer using a plain wireguard config. Bonus points if there is QR Code. Netmaker seems to support it https://www.netmaker.io/resources/wireguard#toc-generating-a-qr-code-for-mobile-client-setup **Describe alternatives you've considered** Having a machine that hosts https://github.com/wg-easy/wg-easy, have the old routers connect there, install netbird on the machine and use it as a network route to the wireguard range. **Additional context** Netbird is awesome and much more mature than Netmaker, it's the only feature missing to make it surpass Netmaker in every area.
saavagebueno added the feature-request label 2025-11-20 05:25:43 -05:00
Author
Owner

@PopcornPanda commented on GitHub (Sep 2, 2024):

I see only one problem with plain WireGuard configs. You lose control over actual client configs. Every client can just change their configuration and needs to manually update them with every change on routing.

@PopcornPanda commented on GitHub (Sep 2, 2024): I see only one problem with plain WireGuard configs. You lose control over actual client configs. Every client can just change their configuration and needs to manually update them with every change on routing.
Author
Owner

@nazarewk commented on GitHub (Sep 3, 2024):

I see only one problem with plain WireGuard configs. You lose control over actual client configs. Every client can just change their configuration and needs to manually update them with every change on routing.

I also thought about it after getting burned by netmaker months ago and decided not to even post the feature request back then.
Now that I think about it it might be possible in a limited capacity through using one of Netbird clients as a controller/router for the static raw wireguard connection, but still it seems like a BIG feature to implement as Netbird itself is doing a lot more than just establishing connection.

@nazarewk commented on GitHub (Sep 3, 2024): > I see only one problem with plain WireGuard configs. You lose control over actual client configs. Every client can just change their configuration and needs to manually update them with every change on routing. I also thought about it after getting burned by `netmaker` months ago and decided not to even post the feature request back then. Now that I think about it it might be possible in a limited capacity through using one of Netbird clients as a controller/router for the static raw wireguard connection, but still it seems like a BIG feature to implement as Netbird itself is doing a lot more than just establishing connection.
Author
Owner

@Silex commented on GitHub (Sep 3, 2024):

I was thinking of a workaround like this:

One machine (let's call it config-generator) is dedicated to generating configs. It generates & connects to the netbird network, then its wireguard config is copied over to the other machine with the plain wireguard client. Then you erase the config on config-generator and start over for new machines.

Would that work?

Of course manual configuration is required, just like with netmaker if I'm not mistaken.

That said, in the meantime I managed to run netbird on the very old routers so this issue is not as critical 🥳

@Silex commented on GitHub (Sep 3, 2024): I was thinking of a workaround like this: One machine (let's call it `config-generator`) is dedicated to generating configs. It generates & connects to the netbird network, then its wireguard config is copied over to the other machine with the plain wireguard client. Then you erase the config on `config-generator` and start over for new machines. Would that work? Of course manual configuration is required, just like with netmaker if I'm not mistaken. That said, in the meantime I managed to run netbird on the very old routers so this issue is not as critical 🥳
Author
Owner

@senses3 commented on GitHub (Jan 19, 2025):

Yes, please. This is what originally attracted me to Netmaker years ago. I quit them when they started moving features from the community version to their hosted enterprise version.

Netbird has been a great solution for us but I have been missing the ability to set up plain Wireguard clients that connect to an ingress node.

@senses3 commented on GitHub (Jan 19, 2025): Yes, please. This is what originally attracted me to Netmaker years ago. I quit them when they started moving features from the community version to their hosted enterprise version. Netbird has been a great solution for us but I have been missing the ability to set up plain Wireguard clients that connect to an ingress node.
Author
Owner

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

a short (possibly already outdated/incomplete by the time you are reading) list of feature requests related to implementing a raw wireguard and/or very dumbed down script-style client utilizing it:

@nazarewk commented on GitHub (Apr 17, 2025): a short (possibly already outdated/incomplete by the time you are reading) list of feature requests related to implementing a raw wireguard and/or very dumbed down script-style client utilizing it: - https://github.com/netbirdio/netbird/issues/496 - let's aggregate the discussion there - https://github.com/netbirdio/netbird/issues/2627 - https://github.com/netbirdio/netbird/issues/1000 - https://github.com/netbirdio/netbird/issues/2504
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1195