Hey, We provide an alternate solution ([1]Wormhole) that covers this scenario (and others). The main differences with e.g. Weave are: - Non Docker-specific -

Hey, We provide an alternate solution ([1]Wormhole) that covers this scenario (and others). The main differences with e.g. Weave are: - Non Docker-specific - Easier to deploy, in my opinion ofc :-) - Based on Open Source (You can just deploy SoftEhter's vanilla client as the agent) - We don't use vxlan, just SSL encapsulation. - Actually, every client will only generate outbound SSL connections, so chances are you won't need to reconfigure any firewalls or network gear for Wormhole to work. - By default, chances are you won't overlap with the provided IP addressing (non-public, non-RFC1918 IP space) - Multiplatform Windows / Linux / Os X - API available to create and deploy networks and clients - Our architecture requires traffic to go up to a central server and down to destination, so there's added latency. In my tests I've found this to not penalise performance for most applications as other solutions based on extra layers (I.e. Vxlan) like Weave. Don't get me wrong, I think Weave is brilliant. We're just an alternative that aims for simplicity. There's some overlapping, but we probably have different markets. [1]: https://wormhole.network https://wormhole.network