netbird VS webrtc

Netmaker (https://www.netmaker.io/) Netbird (https://netbird.io/)

NetBird is a configuration-free, peer-to-peer private network combined with a centralized access control system. Utilizing a WireGuard-based overlay network, it ensures encrypted connections between machines without the need for complex configurations such as port openings, intricate firewall rules, or VPN gateways. Prioritizes security with intuitive management of granular access policies for secure remote access, applicable universally across any infrastructure. petr205 explains, "Their SaaS version is free up to 100 machines and 5 users, but the self-hosted version is exactly the same and has very low requirements."

It is always great to see another solution using Wireguard, which is a great technology for modern private connectivity.

I built https://github.com/netbirdio/netbird, which can be self-hosted and offers an option to run Wireguard without managing firewalls for P2P connectivity.

https://github.com/netbirdio/netbird/issues/1081#issuecommen...

It seems that they plan on open sourcing the app.

https://github.com/netbirdio/netbird#quickstart-with-netbird...

I'd add to that list Netbird, which is the one I ended up using after trying all of the above.

https://netbird.io/

I am really excited about https://github.com/sepfy/libpeer. It has examples ready for ESP32 etc....

When working on KVS I wasn't familiar with the embedded space at all. I saw 'heavyweight' embedded where you were running on Linux. Then you had RTOS/No OS at all. I wasn't prepared for these devices at all. If we can make WebRTC work in the embedded space I think it will really accelerate what developers are able to build!

Remotely driven cars, security cameras, robots in hospitals that bring iPads to infectious patients etc... Creative people are building amazing things. The WebRTC/video space needs to work harder and support them :)

-----

I love how diverse the WebRTC space is now. Outside of this implementation you have plenty of other options!

* https://github.com/shinyoshiaki/werift-webrtc (Typescript)

* https://github.com/pion/webrtc (Golang)

* https://github.com/webrtc-rs/webrtc (Rust)

* https://github.com/algesten/str0m (Rust)

* hhttps://github.com/sepfy/libpeer (C/Embedded)

* https://webrtc.googlesource.com/src/ (C++)

* https://github.com/sipsorcery-org/sipsorcery (C#)

* https://github.com/paullouisageneau/libdatachannel (C++)

* https://github.com/elixir-webrtc (Elixir)

* https://github.com/aiortc/aiortc (Python)

* GStreamer’s webrtcbin (C)

See https://github.com/sipsorcery/webrtc-echoes for examples of some running against each other.

This is not true, there are actually multiple WebRTC implementations in different languages besides the reference library: aiortc (python), libdatachannel (C++), sipsorcery (C#),webrtc-rs (rust), werift (Typescript), and Amazon Kinesis (C)

I have opened an issue on GitHub [1], we can continue there.

[1] https://github.com/webrtc-rs/webrtc/issues/426

webrtc

webrtc.rs is a port of Pion (which we also use). It's a better fit for server-side use

I want to use peer-to-peer communication and data transfer for my next side project (client-server web app). I've been doing some research and WebRTC seems to be the only option for this on the client. There are a ton of libraries and product offering for facilitating STUN/TURN servers as a service, but I'm quite interested in learning more about these protocols. That being said, I'm not the best rust programmer (part of the reason of using Rust as the server is so that I can learn more), and the signalling protocols seem rather complicated. I've looked at https://github.com/webrtc-rs/webrtc and it seems promising.

Regarding webrtc-rs. I'm a contributor to that project. The future of str0m could very well be to roll it in under that umbrella. However in these early days, I think it's better to keep str0m separate, until such time that it covers most of webrtc-rs functionality. Discussion here: https://github.com/webrtc-rs/webrtc/issues/230

This project was really fun for me is that I got to use https://webrtc.rs webrtc.rs Rust implementation of WebRTC that is based on Pion. The performance is fantastic and it is so easy to fetch + build. I had a great experience with it. It is really impressive how far the project has come!

I'm confused, you're saying as far as you can tell webrtc-rs does everything pion can do, but also saying "when the project is ready"? Can you explain what you mean? Also it seems webrtc.rs website says it's not production ready yet? How true is that?