I'll PM you, we'll need to know some specifics

sure

appreciate it

Since the whole connection is now done inside the netmaker container how to i do an iperf3 speedtest through the wireguard tunnel on the netmaker server? thx

you cant, you have to go with one of the options we discussed earlier

either deploy an additional client on the host, or modify the docker-compose so that the networking runs on the host like it used to

@User I just got oauth working with Azure AD. Your docs need some changes, at least for this provider. A few tweaks for the environmental variables for Netmaker too, which don't work as stated. What would be the best way to submit these suggestions?

which variables were off / incorrectly worded? You can open a PR if you already have the fix or issue on GitHub and we'll look at it

The format of the variables (':' instead of '=' is a minor one)

SERVER_HTTP_HOST: fails including https:// here. Needs to just be api.

At least on Azure

ah yeah. that should always be the case, it auto adds it

Frontend_url does require it, suggest formatting as

FRONTEND_URL: "https://dashboard.<netmaker base domain>”

The server sends the request as https://api.netmaker.mydomain.com/api/oauth/callback , not oauth2

took me a while to find the request url that netmaker was using

lol, good catches

You're probably the first to use it other than me and @User

Cool!

I've never made a pull request or been active on GitHub, but I'd be happy to try for the learning experience. They're only documentation changes after all

that's okay we can grab from here then

ok, no worries

I have the repository cloned and the oauth.rst doc ready to edit, so I can try the PR for the funsies, unless you've already got it going?

go for it!

Done it, hope I did it correctly .. !

2021/11/03 17:39:20 [netclient] joining markus at grpc.netmaker1.url.eu:443 2021/11/03 17:39:20 [netclient] node created on remote server...updating configs 2021/11/03 17:39:20 [netclient] retrieving peers 2021/11/03 17:39:20 [netclient] starting wireguard 2021/11/03 17:39:20 error running command: /usr/sbin/ip link set mtu 0 up dev nm-markus 2021/11/03 17:39:20 RTNETLINK answers: Address already in use 2021/11/03 17:39:20 [netclient] failed to create interface with mtu nm-markus 2021/11/03 17:39:20 [netclient] error installing: exit status 2 2021/11/03 17:39:20 [netclient] removed machine from markus network on remote server 2021/11/03 17:39:20 [netclient] removed markus network locally 2021/11/03 17:39:20 [netclient] removed systemd remnants if any existed 2021/11/03 17:39:21 [netclient] removed systemd remnants if any existed And after that: ip a says: 12: nm-default: mtu 0 qdisc noop state DOWN group default qlen 1000 link/none 13: nm-markus: mtu 0 qdisc noop state DOWN group default qlen 1000 link/none

delete the iface

"ip link del dev nm-markus"

then rejoin

@User thanks but same problem. It creates the interface and then the error and it does not delete the interface. It was a fresh (some days old) ubuntu 20.04 server installed with nm-quick v0.8.5 "RTNETLINK answers: Address already in use" maybe because the public IP is already in use? This sure happens if i have netmaker already connected trough docker and now trying to connect withrout docker. It sure has the same public ip.

Run “ip a” and look at the interfaces