does it matter?

Yes, because you need to set the endpoint per-node in that case

But if you’ve got a lot of machines then we probably need some other way

i am just testing ofc, i try to understand the possibilities thats all

I hope it can be of value for you guys

I understand. Is there a way that would make more sense in your case? I’m guessing the interface names are different too

I am trying to create a mesh network for my local servers. i now its not the primary usecase ofc

i just have a lot of vms for testing

these settings are just defaults which can all be overridden on the node level which is probably what is needed in more complex cases

and in the light of the new zero trust networing

Maybe we need an option to just deselect setting the endpoint automatically

Do you have an idea of how it might be able to select the correct ip in your case automatically?

i am going to test the primary usecase first, LAN > WAN mesh so i can understand the terms better

Ok, this is also helpful for me to understand user flow. If you are trying to set some settings and think “why doesn’t it just do X instead of Y” I’d like to hear it

yup ok, if you have more up to date documentation, let us know 😉

I'm annoyed at myself for not being able to figure this out. I setup an Ubuntu VM just to test this out. just did an apt install docker and docker-compose and changed the IP and I get this: @ubuntuvpnserver:~/netmaker$ sudo docker-compose up -d Removing netmaker mongodb is up-to-date Recreating 284373245f44_netmaker ... error ERROR: for 284373245f44_netmaker Cannot start service netmaker: error while creating mount source path '/usr/bin/wg': mkdir /usr/bin/wg: read-only file system ERROR: for netmaker Cannot start service netmaker: error while creating mount source path '/usr/bin/wg': mkdir /usr/bin/wg: read-only file system ERROR: Encountered errors while bringing up the project.

I have a ton of experience setting up wireguard, but zero using docker.

you need to install wireguard on your VM

oooh

gotcha

telaeris@ubuntuvpnserver:~/netmaker$ sudo apt install wireguard Reading package lists... Done Building dependency tree Reading state information... Done wireguard is already the newest version (1.0.20200513-1~20.04.2). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. telaeris@ubuntuvpnserver:~/netmaker$ sudo docker-compose up -d Removing netmaker mongodb is up-to-date Recreating 284373245f44_netmaker ... error ERROR: for 284373245f44_netmaker Cannot start service netmaker: error while creating mount source path '/usr/bin/wg': mkdir /usr/bin/wg: read-only file system ERROR: for netmaker Cannot start service netmaker: error while creating mount source path '/usr/bin/wg': mkdir /usr/bin/wg: read-only file system ERROR: Encountered errors while bringing up the project. telaeris@ubuntuvpnserver:~/netmaker$

hmmmm

NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=focal UBUNTU_CODENAME=focal telaeris@ubuntuvpnserver:~/netmaker$ uname -r 5.4.0-72-generic

I had some issues before with wireguard in the wrong alpine environment, perhaps this is similar for Ubuntu...

apt install wireguard-tools

already installed

I like the way you're thinking though....

the /usr/bin/wg file exists

Hmmm

I'm going to just yell at a wall and go get some beer.