we're gonna overhaul the ID stuff for v0.2

And I was gonna use node name as the ID, so it would just need to be unique

yes, would have to do a unique test on server side. If not unique add an number i.e. if you try to create client on two machines both of which have hostname of my_machine, the first one gets my_machine as its node name and the second one get my_machine_1

I think I'm gonna open source the repo today. Just gonna clean up the docs and let 'er loose. Post on Reddit to follow

woot

Repository now public. Now I gotta figure out the right way to do this branching stuff

"Multi-cluster management with multi-cloud federation"

that's a feature of calico enteprise, I wonder if this type of setup is something they're offering but doing a shit job of marketing

Oh man, some other guys just released pretty much the same project as this last night. Pretty good timing lol. https://www.reddit.com/r/WireGuard/comments/mg8ifs/introducing_innernet_tailscalelike_open_source/

I need to look into their stuff today

Yeah, similar scope and mission. I think it's good for the community to have multiple options. Let's see how we compare!

Probably need to take this into account when we figure out how we implement DNS. https://github.com/tonarino/innernet/issues/6

I think it's still a good "quick fix" thing that we can implement fast. We can make it an optional feature that is off by default. Then in a future version we can replace it with a more robust option

post is up! Check it out: https://www.reddit.com/r/selfhosted/comments/mgfep1/netmaker_a_new_wireguardbased_virtual_networking/

Also let me know if there's any other communities you think this might be a good fit for.

r/wireguard ?

yup! i posted a demo video there. By the way, here's the video, though you're already an expert Matt 😃

Hi, How's everyone doing? I'm wondering if you guys have plans on adding a feature similar to NHRP (https://tools.ietf.org/html/rfc2332) for NetMaker? This is to reduce the burden on the Central Server if the spokes/clients needs to heavily/constantly communicate with each other (scaling issue)

Hi! Thanks for joining @User. Maybe I'm misreading your question, but the central server is not acting like a relay. It's not a hub and spoke model, it's a full mesh. the clients are all set up with direct tunnels to each other. The central server just holds and modifies configs so that the clients know how to find each other. Even if the server goes down, all the clients still have functional tunnels to one another, they just don't get updated (so if clients are added/removed/modified, this will not be recognized by the network). That said, it's bad to have one point of failure, and long term we would like a good solution to this. We would like to add the option for something like Kademlia, but likely would need funding for a developer, unless someone from the community is willing to take it on, as it would be a pretty big overhaul. In the near term, our solution is just going to be adding some form of load balancing for the server, and allowing clients to become failover servers.

Hello, I'm Paul

invited here by afeiszli - thank you

welcome @User

@User Thank you

Poor afeiszli got sucked into a long voice call - he handled it well (haha)

@User Good talking to you! You're super knowledgeable

Thank you for the kind words, always something new to learn (and share) 🙇

Hi All, here is the plan for the next sprint (v0.2), to take place over the next two weeks. I have rearranged some priorities to make room for "Gateway Mode." I was going to have this in a later iteration (v0.6), but the community seems to really want this, and some of the other features aren't really going to effect usability short term. I've added all of the "punted" features under "nice to have." They'll be mandatory for v0.3, but hopefully we can get to a couple.

Sprint - v0.2 Bugfix List - https://github.com/gravitl/netmaker/issues/8 - https://github.com/gravitl/netmaker/issues/16 - https://github.com/gravitl/netmaker/issues/26 - https://github.com/gravitl/netmaker/issues/27 - https://github.com/gravitl/netmaker/issues/30 - https://github.com/gravitl/netmaker/issues/29 - https://github.com/gravitl/netmaker/issues/31 - https://github.com/gravitl/netmaker/issues/32 - https://github.com/gravitl/netmaker/issues/42 - https://github.com/gravitl/netmaker/issues/53 - https://github.com/gravitl/netmaker-ui/issues/5

Documentation: - [ ] Enhance Documentation - [ ] Enhance API Docs - [ ] Enhance Getting Started - [ ] Create Advanced Usage Docs: Include non-docker instructions - [ ] Enhance Contributing Docs - [ ] Update Roadmap Docs - [ ] Create Troubleshooting Docs - [ ] Create "deep dive" tutorial video

Features - [ ] Expiring peer timeout: Admin should be able to set a "datetime" at which nodes will expire - https://github.com/gravitl/netmaker/issues/47 - [ ] Encode Server, Port, and Group into Key - https://github.com/gravitl/netmaker/projects/1#card-58137613 - [ ] Public Key refresh - https://github.com/gravitl/netmaker/projects/1#card-58137706 - [ ] Have a "default" network created at startup - https://github.com/gravitl/netmaker/projects/1#card-58137807 - [ ] Make server a node (in default network) startup - https://github.com/gravitl/netmaker/projects/1#card-58138072 - [ ] Set private DNS via etc hosts (node name + ip). Make it optional flag on agent. - https://github.com/gravitl/netmaker/projects/1#card-58138176 - [ ] Gateway Server Mode: Enable converting any given node into a gateway server for a specified network - https://github.com/gravitl/netmaker/projects/1#card-58138246