Closed bcookatpcsd closed 2 years ago
Hi @bcookatpcsd, main thing to keep in mind when running server internally is that UDP Hole Punching will not work (known issue). This should not be necessary for internal networks anyway, so just leave that off. Look through the env vars in the docker-compose.yml and make sure they're all pointed towards the internal addresses.
That is for mesh network-to-network specific correct? If I was doing hub and spoke or traditional vpn concentrator.. that doesn't apply right? (I'm still working on getting wg going.. )
https://dashboard.nm.192-168-10-100.nip.io/networks/vpn/edit and then default here is 51821..
Then I'm trying to nat that to gravitl/netmaker:v0.9.2 on the docker host..
RIght?
Hmmm...you're trying to do a hub-and-spoke network (traditional VPN) with the server on your home network? Not sure I understand the use case for that...since it will still use your home IP...you'd usually want a cloud VPS for this.
@bcookatpcsd closing as there has not been an update
I wanted to have this internal only..
I modified the Caddyfile
./nm-quick.sh -v true -m false -e name@domain42.dom -c 5 -d nm.192-168-10-100.nip.io
Also I removed the dpkg section as I was getting this to work on Fedora..