re: Main Node - Well, that is how GoodCloud displays it. I’m quite aware how s2s and p2p vpns work. I just needed some way to reference the single node that has maintains the connection - The only one requiring an open port. Part of my configuration issues is I’m dealing with end-user/homeowner networks. I need a solution that I can just drop a router in place and either AP to their WiFi or hardwire and not have to deal with whatever NAT hell is going on there. The only node that I have control over is the main, home office node.

The problem I’m solving for is: My company installs IoT based Solar Power systems in residential locations. Consumer wifi is all over the place - I spend too much time fixing issues with our devices. I’m trying to create a walled garden that the on-premises devices can connect to, instead of the in-home wifi/network. Ideally the gl.inet router would be hardwire WAN in so the homeowner can change wifi passwords without requiring a site visit. And with the VPN I can now get granular configuration on the devices themselves, instead of taking a trip out there to modify a single setting.

I don’t think we need things always connected - but that raises issues for our service techs who don’t understand networking/VPN - and deploying/maintaining a very complicated (500-1000+) set of P2P VPN configurations. My solution is that if you VPN just into the one “Main Node” at the office then I can own the DNS to get my employee/tech to the correct site to administer by simply connecting to “client-name” dns entry.

Thanks for the link with your scripting work - If I go this route I’ll be needing something like that, building on your work here.