How does Nomad Branch ensure subnets only receive packages once?
As a package is advertised to machines within a remote branch, one Nomad Branch client will be elected as a ‘master’. This client will begin to download the package to its local cache. The other clients on the remote branch subnet will then use their local ‘master’ as an alternative distribution point and use simple peer-to-peer networking to download the software. If multicast is enabled the ‘master’ will also be able to broadcast the download as an alternative to the peer-to-peer transfer.
