Possible hundreds of clients - Main Node recommendations

[hubpub]

“Main node” is a term related to site-to-site VPNs, typically deployed between a fixed number of stably-connected locations where the head office acts as the “main node.”

When lots of VPN clients connect/disconnect on-demand or roam, you can deploy a traditional hub-and-spoke VPN architecture, and run any Linux x86 distro on the WireGuard VPN server (hub).

• assuming this VPN server is on-premise at the head office, configure and administer it directly (it is outside of the GoodCloud scope)
• GoodCloud should be used only to configure/monitor/troubleshoot the fleet of GL-inet routers as VPN clients

Given the large number of GL-inet routers involved, I recommend to drive the provisioning process through scripting. Below is a previous forum thread with some technical considerations.

Bulk flashing process

There are webAPIs for checking and triggering firmware updates. But this would require going through the upgrade process one router at a time (serially). In my case, I run an out-of-the-box-setup script to initialize the admin password (see below), and then enroll the routers into GoodCloud management. Business users can request a “business” level GoodCloud account, which can perform firmware upgrades and apply configuration templates in bulk/parallel. #!/bin/sh # router by IP (default) ROUTE…