111 karma · joined July 1, 2021
Connect: @braginini on Github
Thank you for the feedback! Could you please elaborate on the issues that you are facing? We have quite a few multi-user cases both on the managed and self-hosted version with no issues.
Thank you!
NetBird is one of these p2p private networking solutions that is truly open-source. Actually, I haven't seen any comparable yet.
We haven't yet published the Android code simply because we have coding standards to meet before we open the code to the public. This is mainly about the code structure and tests. We are working on it.
We are a tiny team of engineers with a vision to make private networking simple and secure, which is challenging. Therefore, we should prioritize some things over others. But we are getting there! With your support :)
We did a few improvements recently. When did you try netbird for the last time? Happy to follow-up on the DNS issues in our Slack channel https://join.slack.com/t/netbirdio/shared_invite/zt-vrahf41g...
We've developed a one liner script that provisions the whole setup including an IDP integration in just a few minutes.
We use Zitadel IDP for SSO and user management. It is self-hosted and open source too :)
Check it out!
See the documentation for more details: https://netbird.io/docs/how-to-guides/network-routes
Access controls are in progress and will be released in June. We are building a tagging system for peers (endpoints) so that you could create peer groups and assign access rules to them. Check the mockups https://github.com/netbirdio/dashboard/blob/main/media/taggi...
We will reduce ports for Management (merge gRPC with HTTP) so it will be just port 443. AS for TURN and Signal, these are separate components and require open ports. You could also use any public TURN server - your traffic will be p2p encrypted, just the IP of your peer will be exposed to that services. If it is not a concern, then it is a good option :)
FYI: Network still be working in case the management service is down.
See architecture overview: https://netbird.io/docs/overview/architecture
Every component can be self-hosted.
And a separate Thank you for Pion - it is just awesome :)
Disclaimer: I'm author of netbirdio - a similar project.
Using WebRTC makes it possible to have a tunnel from the browser directly. Combined with a virtual terminal it just makes it even cooler!
@pojntfx what do you think about that? Feasible with your implementation?
I've been playing with such functionality in Netbird but since it depends on Wireguard it is a bit tricky :)
Would love to have your feedback as well on our project
There is another way of combining WebRTC and Wireguard.
Netbird uses ICE protocol (used in WebRTC) for NAT traversal and then reuses that punched holes to establish a direct Wireguard tunnel.
https://github.com/netbirdio/netbird
P.S. I'm author of Netbird (formerly know as Wiretrustee)
Give it a shot :)
P.S. Wiretrustee Author
P.S. I'm a Wiretrustee author
There are some caveats though. We use a fixed mtu value of 1280 to be on a safe side while wg-quick dynamically detects the best value. We will improve it.
If the Wireguard kernel module isn't available (true for older Linux, Mac and Windows) then userspace implementation is used (wireguard-go) which is slower.