Add own relay (coturn) server #368

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

@mlsmaycon

This thing is planned?

Now i use Tailscale + own Derper to fastest access to my home network, every scenario. (p2p are priority and derper, if the remote network too restricted)

I would like to switch netbird, mainly because of kernel wireguard.

@vampywiz17 commented on GitHub (Oct 11, 2023): @mlsmaycon This thing is planned? Now i use Tailscale + own Derper to fastest access to my home network, every scenario. (p2p are priority and derper, if the remote network too restricted) I would like to switch netbird, mainly because of kernel wireguard.

saavagebueno commented

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

Hello @vampywiz17 it is planned for 2024, we don't have yet a proper estimation in which quarter we will be working on it, but I will let you know as soon as we plan it.

@mlsmaycon commented on GitHub (Oct 16, 2023): Hello @vampywiz17 it is planned for 2024, we don't have yet a proper estimation in which quarter we will be working on it, but I will let you know as soon as we plan it.

saavagebueno commented

@kuyoeku commented on GitHub (Jan 18, 2024):

@mlsmaycon Is it possible to add a relay mode to the peers? Each peer has its own algorithm to determine which relay peer can achieve the lowest latency to reach the target peer.

@kuyoeku commented on GitHub (Jan 18, 2024): @mlsmaycon Is it possible to add a relay mode to the peers? Each peer has its own algorithm to determine which relay peer can achieve the lowest latency to reach the target peer.

saavagebueno commented

@remann2 commented on GitHub (Aug 6, 2024):

any updates?

@remann2 commented on GitHub (Aug 6, 2024): any updates?

saavagebueno commented

@1nerdyguy commented on GitHub (Sep 18, 2024):

Assume this can be closed out with the new relays?

@1nerdyguy commented on GitHub (Sep 18, 2024): Assume this can be closed out with the new relays?

saavagebueno commented

@vampywiz17 commented on GitHub (Sep 18, 2024):

Assume this can be closed out with the new relays?

You talking about these, right?

Coming Soon
New relay system
We are moving away from the TURN relay (coturn) to our own relay implementation based on WebSocket. This new system will ensure that all relayed connections utilize a single secure port (443), instead of allocating one port per connection as before. The update is expected to enhance performance and ensure faster, more reliable connections, even in stricter network environments. 🚀 That's a wrap for this month's newsletter. Thank you for being part of our community. We appreciate your support and feedback. Until next time!

But it mean that your provided relay will change working method, not self hosted relay. If i understand it correctly. Anyway, it sound good, nof i finally able to replace my tailscale network (now netbird not work some cases, for example some heavy firewalled public networks...)

@vampywiz17 commented on GitHub (Sep 18, 2024): > Assume this can be closed out with the new relays? You talking about these, right? > Coming Soon New relay system We are moving away from the TURN relay (coturn) to our own relay implementation based on WebSocket. This new system will ensure that all relayed connections utilize a single secure port (443), instead of allocating one port per connection as before. The update is expected to enhance performance and ensure faster, more reliable connections, even in stricter network environments. 🚀 That's a wrap for this month's newsletter. Thank you for being part of our community. We appreciate your support and feedback. Until next time! But it mean that your provided relay will change working method, not self hosted relay. If i understand it correctly. Anyway, it sound good, nof i finally able to replace my tailscale network (now netbird not work some cases, for example some heavy firewalled public networks...)

saavagebueno commented

@1nerdyguy commented on GitHub (Sep 18, 2024):

The new method allows you to deploy the relays independently of the management service, as it's now a stand alone docker instance. You can also add them to the management.json file, and have multiple, self-hosted relays.

I've tested this myself due to similar issues. Hosting 5x relays by just spinning up the docker container on a host by each heavily firewallwed area, forwarding 1 port, and updating the management.json.

Works great!

@1nerdyguy commented on GitHub (Sep 18, 2024): The new method allows you to deploy the relays independently of the management service, as it's now a stand alone docker instance. You can also add them to the management.json file, and have multiple, self-hosted relays. I've tested this myself due to similar issues. Hosting 5x relays by just spinning up the docker container on a host by each heavily firewallwed area, forwarding 1 port, and updating the management.json. Works great!

saavagebueno commented

@vampywiz17 commented on GitHub (Sep 18, 2024):

@1nerdyguy

One question left :)

If i do a cloud service (free tier, enought to me) and also install a new relay on my infra, it possible to add it to my cloud settting?

(i not want to provide a full netbird, only relay)

@vampywiz17 commented on GitHub (Sep 18, 2024): @1nerdyguy One question left :) If i do a cloud service (free tier, enought to me) and also install a new relay on my infra, it possible to add it to my cloud settting? (i not want to provide a full netbird, only relay)

saavagebueno commented

@1nerdyguy commented on GitHub (Sep 18, 2024):

No clue on that, but in this case you shouldn't need to, as you're able to use the relays of the cloud environment.

Are you stating you'd like to use the free-tier of Netbird, you're getting Managed netbird there. That includes, according to their docs: https://docs.netbird.io/selfhosted/self-hosted-vs-cloud-netbird, geo-distributed relays.

@1nerdyguy commented on GitHub (Sep 18, 2024): No clue on that, but in this case you shouldn't need to, as you're able to use the relays of the cloud environment. Are you stating you'd like to use the free-tier of Netbird, you're getting Managed netbird there. That includes, according to their docs: https://docs.netbird.io/selfhosted/self-hosted-vs-cloud-netbird, geo-distributed relays.

saavagebueno commented

@vampywiz17 commented on GitHub (Sep 18, 2024):

No clue on that, but in this case you shouldn't need to, as you're able to use the relays of the cloud environment.

Are you stating you'd like to use the free-tier of Netbird, you're getting Managed netbird there. That includes, according to their docs: https://docs.netbird.io/selfhosted/self-hosted-vs-cloud-netbird, geo-distributed relays.

Yes, i know, that i able to use cloud based relays. but some cases (for example speed ) it better to use own relay.

For example:

Current way:

Client 1 (at home) -----> Cloud Relay (for example a different country, it use other people, etc...) -----> Client 2 (a different place)

Preferred way:

Client 1 (at home) -----> my own hosted Relay (same network that my client 1 , essentially a "other" client with TLS and https that accept all firewall ) -----> Client 2 (a different place)

Tailscale are support the second way, named "custom DERP Server". You able to add it to your cloud config.

@vampywiz17 commented on GitHub (Sep 18, 2024): > No clue on that, but in this case you shouldn't need to, as you're able to use the relays of the cloud environment. > > Are you stating you'd like to use the free-tier of Netbird, you're getting Managed netbird there. That includes, according to their docs: https://docs.netbird.io/selfhosted/self-hosted-vs-cloud-netbird, geo-distributed relays. Yes, i know, that i able to use cloud based relays. but some cases (for example speed ) it better to use own relay. For example: Current way: `Client 1 (at home) -----> Cloud Relay (for example a different country, it use other people, etc...) -----> Client 2 (a different place)` Preferred way: `Client 1 (at home) -----> my own hosted Relay (same network that my client 1 , essentially a "other" client with TLS and https that accept all firewall ) -----> Client 2 (a different place)` Tailscale are support the second way, named "custom DERP Server". You able to add it to your cloud config.

saavagebueno commented

@1nerdyguy commented on GitHub (Sep 18, 2024):

Nope, I get what you're saying.

I'm saying that, to my knowledge, that's not an option. So guess you're right, it's still a thing, but you we need to tweak it to include the new relays

That being said, it's no longer a issue, as much as a feature request.

@1nerdyguy commented on GitHub (Sep 18, 2024): Nope, I get what you're saying. I'm saying that, to my knowledge, that's not an option. So guess you're right, it's still a thing, but you we need to tweak it to include the new relays That being said, it's no longer a issue, as much as a feature request.

saavagebueno commented

@vampywiz17 commented on GitHub (Sep 18, 2024):

these topic start with " feature request" not issue.

the original post:

it would be good that use a own coturn/relay server. It contain the self-hosted bundle, but somtime enought the free plan, but would be good a fast/self-hosted relay.

But i found these in release note on v0.29.0

Cloud support for the new relay feature is coming soon*.

Not clear to me that mean:

Cloud relays will update new relay type
Cloud will able to configure your own relay server

Of course that 2. are the best to me. (and the answer these feature request)

@vampywiz17 commented on GitHub (Sep 18, 2024): these topic start with " feature request" not issue. the original post: > it would be good that use a own coturn/relay server. It contain the self-hosted bundle, but **somtime enought the free plan**, but would be good a fast/self-hosted relay. But i found these in release note on v0.29.0 > Cloud support for the new relay feature is coming soon*. Not clear to me that mean: 1. Cloud relays will update new relay type 2. Cloud will able to configure your own relay server Of course that 2. are the best to me. (and the answer these feature request)

saavagebueno commented

@jesvinjoachim commented on GitHub (Oct 15, 2024):

The new method allows you to deploy the relays independently of the management service, as it's now a stand alone docker instance. You can also add them to the management.json file, and have multiple, self-hosted relays.

I've tested this myself due to similar issues. Hosting 5x relays by just spinning up the docker container on a host by each heavily firewallwed area, forwarding 1 port, and updating the management.json.

Works great!

can you help me how to do that? the steps, (please note i am not an advanced sysadmin or anyting like that)

thank you in advance

@jesvinjoachim commented on GitHub (Oct 15, 2024): > The new method allows you to deploy the relays independently of the management service, as it's now a stand alone docker instance. You can also add them to the management.json file, and have multiple, self-hosted relays. > > I've tested this myself due to similar issues. Hosting 5x relays by just spinning up the docker container on a host by each heavily firewallwed area, forwarding 1 port, and updating the management.json. > > Works great! can you help me how to do that? the steps, (please note i am not an advanced sysadmin or anyting like that) thank you in advance

saavagebueno commented

@kmahyyg commented on GitHub (Oct 22, 2024):

Same problem here on my side, since Netbird managed cloud relay is blocked/very slow on my side, I'd like to add a self-hosted relay server in my managed netbird instance, feature request +1

@kmahyyg commented on GitHub (Oct 22, 2024): Same problem here on my side, since Netbird managed cloud relay is blocked/very slow on my side, I'd like to add a self-hosted relay server in my managed netbird instance, feature request +1

saavagebueno commented

@lonnietc commented on GitHub (Feb 22, 2025):

Hi All,

I also want to add relays, but outside of Docker and have compiled the netbird relay Golang code into binaries for Windows, Linux, and MacOS, but just cannot seem to find any documentation on how to run it, or also how to get a list of active network relays from the command line. As a node, I have also set up the self-hosting netbird for testing all of this, and it runs nicely with the basic install.

Any thoughts on running and listing these non-docker relays would be truly appreciated.

@lonnietc commented on GitHub (Feb 22, 2025): Hi All, I also want to add relays, but outside of Docker and have compiled the netbird relay Golang code into binaries for Windows, Linux, and MacOS, but just cannot seem to find any documentation on how to run it, or also how to get a list of active network relays from the command line. As a node, I have also set up the self-hosting netbird for testing all of this, and it runs nicely with the basic install. Any thoughts on running and listing these non-docker relays would be truly appreciated.

saavagebueno commented