I'm gonna repeat afeiszli's question, what are you trying to achieve here that isn't solved with the wireguard app?

Nothing much, WireGuard client is great for techies but for general users it can get complicated (even with QR code and all). A simpler app that rely on WG component in the background can ease the job. I also believe that there could be a chance to bring additional benefits/features handled by netclient.

I'm not an authority on this, but I'll play devil's advocate a little bit. I don't believe there's a way to make it easier for end users on an iPhone than just scanning the QR code. Not without having full mdm control over their device. I'm also not sure what benefit you're going to get from it beyond, at bare minimum, not having to relay through a gateway, which is fair. I've used nebula for things like that, but it really hasn't gotten me much functionality beyond the ability to mesh a DNS sec server over that network... which is about the opposite direction you'd want to go for non-techies.

You are absolutely right on WireGuard QR simplicity, but thing get a little complicated when you have large network spread across different data centers on 3 continents and you have to juggle external devices in between. We are looking at netmaker as a way that could simplify current setup. Today we combine Anycast, WG, BGP, and iptables. Anycast to route the user to nearest WG Server. BGP on the server to route traffic, and iptables to enforce policy. (I left aside data sync and database which are similar to your netmaker design). While pushing the whole route tables to each client is definitely a bad idea, I think a netclient implementation for mobile can at least push all internal routes. Plus maybe the benefit of modifying node config remotely without sending new config and periodic cycling of the keys.

@User Marcuss-iMac-5:~ marcus$ uname -a Darwin Marcuss-iMac-5.fritz.box 18.7.0 Darwin Kernel Version 18.7.0: Mon May 3 20:41:19 PDT 2021; root:xnu-4903.278.68~1/RELEASE_X86_64 x86_64 Marcuss-iMac-5:~ marcus$ uname Darwin MacOS Mojave. netclient-install.sh only checks for "darwin" but not "Darwin".

Okay, created PR: https://github.com/gravitl/netmaker/pull/548

Okay strange, you check uname | tr '[:upper:]' '[:lower:]' i don't know why it says unsupported OS then on Install. Because of Mojave?

merged PR. No idea why it wouldn't check that on mojave. Maybe something to do with the shell version.

netmaker 0.9.2 and ui 0.9.2 the List of all nodes sortes different every 5 seconds. Feature not a Bug?

you sure your UI is on v0.9.2? that should have been fixed...

If you have multiple networks with a "netmaker" node, those are sort of random since the names are the same (can fix by changing names), but the rest should be sorted, unless they also have same names..

just updated mine, still seems to work 🙂

yes, they all are named netmaker. I don't rename them in the multiple networks.

Hi @everyone, happy new year! We are considering making "client mode" required, meaning every network will always have a netmaker node included. This is how it already works by default, but you can disable it. If you disable client mode for any reason, please let us know here.

what are the current use cases for disabling client mode?

If for some reason the server should not be able to reach the nodes directly.

But I have a hard time guessing why that might be needed

Someone might use this if the server should not participate in egress ranges

A few people have asked if they can exclude nodes from getting egress, i think that is a better option.

though we'll still have to be able to develop that

I'd like to get some thoughts here on something we have in development: Telemetry https://github.com/gravitl/netmaker/tree/feature_v0.10.0_telemetry This is slated for 0.10 which should (hopefully) be later this week. It is designed to be opt-out, and would send anonymous statistics on usage once daily. All you have to do is set TELEMETRY=off in the docker-compose and it will not send any data. We're going to make it very obvious in the release and the docs that the feature is there, and how to turn it off. The purpose is to provide us with anonymous data on usage that will drive development. The platform is pretty broad, and we don't have the resources to focus on every component equally. It would send integer data about the number and types of nodes, and the version of the server, that would be it. You can see how it's designed here: https://github.com/gravitl/netmaker/blob/feature_v0.10.0_telemetry/serverctl/telemetry.go I'm guessing people will have some strong feelings about this so want to bring it up before we do the release and get some thoughts.

Will it be an opt-in or an opt-out?

Just asking it now as i'm sure others have the same question

The current plan is for opt-out, with very obvious / apparent details for how to turn it off

Just ask it when adding the initial user and have a switch in options, should be fine. Also local telemetry that is avaliable to admin would be nice

I agree, that's a good idea, but may have to wait till 0.10.1 since it will require a UI change and extra API configuration + function

I can see the need, and the current data looks innocuous, but how would any increase in data capture be communicated to admins in the future? Via the UI? Just thinking of what this might become. I'm not sure automatic opt-in sits well with EU data protection laws if anything personally identifiable were to be included in the future . As long as the whole thing can / will be revisited in if it evolves from its current form, then I would be comfortable with this.

Yeah that makes sense, maybe we can do it the same way that websites do it nowadays where you can toggle which data gets sent, and after upgrades we could give a popup in the UI

In any case the plan is to keep everything contained in the "telemetry.go" file, and to keep that file as short as possible, so you can see exactly what it's doing

just seen this- my 2c opt-out seems to be very common so I don't have a big issue with that, but - - currently I'm able to install silently and without the user needing to click anything. That's a very valuable feature for me, so I'd love a switch in the 'join' command to switch this off, like netclient join --name bob --telemetry="0" -t xxxxxx