> complex tricks with the existing network stack To retain the essence of how weave operates, this would likely not just be complex but impossible, short of ke

> complex tricks with the existing network stack To retain the essence of how weave operates, this would likely not just be complex but impossible, short of kernel hackery. > you would really only need to do processing at the beginning of a connection and for some ARP request Weave needs to look at every Ethernet packet. Well, the headers at least. It's a virtual Ethernet switch. It doesn't even really know about IP, let alone TCP streams. See https://github.com/zettio/weave#how-does-it-work https://github.com/zettio/weave#how-does-it-work