Traffic Squeezer - Virtual Private Network (VPN)

Traffic Squeezer - with VPN (virtual Private Network)

Traffic Squeezer can be inter-connected with (or existing) the VPN based tunnels. Provided one have to make sure that the traffic/packets goes to the VPN engine ONLY after Traffic Squeezer optimization.

The reason for this connectivity or packet flow order is that once a packet gets basically encrypted (mostly happens with any VPN based tunnels), there is little room left for any compression in case. In theory a plain-text which is encrypted can never be further compressed, since the data looks more like random jumbled binary bytes once it get compressed. So if the data passes via Traffic Squeezer optimization then to any VPN based software or hardware, one can get both the benefits of data-optimization as well traditional VPN services.

However the inter-operability between Traffic Squeezer and other Open-Source VPN solutions namely OpenVPN and IPSec is not yet been tested. In case if anyone tests this particular scenario, can share their experience with us. The future Traffic Squeezer - Beta/Pre-Beta, possibly this might get tested to confirm its inter-operability and if not possibly can be made inter-operable too. And in case if found mandatory by popular demand the same can be also bundled with existing Traffic Squeezer base and so that one can get unified configuration interface for everything.

The case VPN Software within Traffic Squeezer box is a question, only for the reasons that order of packet processing within single Box/PC where packets get processed by VPN + Traffic Squeezer software, and the order they do.

But in case if one have or already using a dedicated VPN Hardware/Box, possibly it should work with no issues with Traffic Squeezer within its deployment. Since the packets compressed or optimized with Traffic Squeezer are still complaint with TCP/IP so routing should happen with no issues. And so can be passed via Internet through a VPN Device as shown below.