Here is the TrafficSqueezer historical project progress timeline since its inception. It marks all the major activities/tasks, achievements and project source-code releases which are completed and soon or later if there is anything expected to be completed in the near future.
TrafficSqueezer Project Road Map
Release - Mainstream Series [Feb-2011 - till-date]
Here is the TrafficSqueezer - mainstream updated feature list:
| Feature Description | Supported/Not-supported | Comments |
|
|
| Supported Device Configuration Modes | |
|
| Routing Mode |
 |
Traffic Squeezer engines are hooked to Linux Kernel network -> IPv4, IPv6 routing APIs. So it supports routing mode. |
| Transparent Bridging Mode (Layer2 L2 Bridging) |
|
Traffic Squeezer engines are hooked to Linux Kernel network -> bridge APIs. So it supports layer2 L2 bridging/Switching mode. |
| Local Device and or Local Server Optimization | |
Traffic Squeezer engines are hooked to Linux Kernel network -> IPv4, IPv6 local device packet RX, and TX flows and APIs. So it supports directly local device or local server optimization. |
|
|
| Data Optimization | |
|
| Traffic packet/frame coalescing |
|
Does coalescing/multiplexing of packets,there by it creates highly optimized tunnel. |
|
| Data Templating – version 19x |
|
Optimizes
- HTML, Javascript, CSS and other scripts
- HTML, PDF and other file optimization
- MySQL DB communication optimization
- SSH/SCP Protocol handshakes
- Citrix ICA Protocol Optimization
- SPICE Protocol Optimization
|
|
| Application Specific Optimization |
|
|
|
| HTTP Protocol Optimization – version 12x |
|
Optimizes
Optimizes what is not covered in packet templating.
|
|
|
| Packet Compression | |
Supported lossless compression algorithms:
LZO (via LZO Linux Kernel Library),
LZ77, RLE. (RLE/LZ77 via BCL Open-Source generic Compression Library, custom ported to Linux Kernel within Traffic Squeezer.) |
| Email Optimization |
|
Supported via Templating. |
| DPI Filters |
|
Supports Deep Packet Inspection of Application layer protocols: HTTP, DNS, SMTP, POP, etc.Supports extensive DPI logs and historic analysis via Aquarium. |
| L7filter Filters |
|
Supports Application layers: DNS traffic filter. |
|
| HTTP-Caching, FTP-Caching |
|
Supported via SQUID-Cache. TrafficSqueezer provides an abstraction over the same. |
|
| DNS-Caching |
|
Supported via dnsmasq DNS-Caching. Traffic Squeezer provides an abstraction over the same. |
|
| Network Monitoring and Analysis |
|
|
|
|
| Performance Statistics | |
|
|
| Historical Statistics | |
Historical Statistics are only supported via Aquarium. |
|
| TS Limited Firewall |
|
|
|
|
| Data Encryption |  |
Should be supported in future. Or can be done on demand. |
|
| QoS (Quality of Service) |
|
|
|
|
| TCP Optimization and Acceleration |
|
|
|
| WAN Simulator (Integrated) |
|
Can use/configure a dedicated Traffic Squeezer machine as a WAN Simulatorinstead as Traffic Squeezer
WAN Optimization solution. |
|
| VPN Support |
|
Should support external VPN Deployments,but yet to be tested with local VPN setups namely via OpenVPN or IPSec. |
|
|
| High-Availability |
|
Includes a custom simplified High-Availability feature which enables to configure a stand-alone backup
Traffic Squeezer machine as a slave machine to enhance availability in a critical path/traffic based requirements. |
|
| Protocol Spoofing |
|
|
| Send TCP as UDP |
|
|
| Send UDP as TCP |
|
|
|
| IPv6 Support | |
Should be supported in future. (Should be released during September-2011 or by Christmas-2011). |
| GUI Support |
|
Supports extensive Traffic Squeezer GUI and automation via Doublefish Solutions Aquarium. |
CLI Support |
|
Traffic Squeezer CLI support is dropped after Traffic Squeezer - BETA series.
(i.e CLI is dropped in on-going and future mainstream series) |
Release - Beta [Sep-2010 - Feb-2011]
Traffic Squeezer - BETA is released and you can
download the same.
Release - Pre-Beta (Prototype Version) - [Jun-2010 - Sep-2010]
This release is far more stable than the old releases. As well it incorporates a light-weight Application and refined TrafficSqueezer Kernel Core. It has also been provided with a integrated light-weight loosely-coupled new Device GUI.
This new Device GUI is suitable for both standalone installations such as Home users/SOHO/Corporate users. And even scalable for large Network service providers too. For more details about the new Device GUI please refer the section
"Traffic Squeezer - Control/Configuration Interfaces" of the Documentation.
The Traffic Squeezer - PRE-BETA feature list is removed, since now there is new Traffic Squeezer - mainstream series is available. Updated: 12-Jul-2011.
Traffic Squeezer - Big Picture
TrafficSqueezer have been made or designed to remain highly modular. WAN Optimization the more we discover, we can find its highly creative and yet no single/major technique cannot be much standardized.
Hence to achieve optimization sometimes we need to write specific optimization techniques, or else at least we should bring some existing third-party open-source modules under one roof. Linux Kernel already have some open-source modules (mostly they exist for NON-wan-optimization context), TrafficSqueezer can make use of them in the WAN Optimization Context, in the Traffic Squeezer Context and so vice versa.
Performance/latency vs Data Optimization:
TrafficSqueezer delivers reasonable packet delivery rates, which is more adequate for a reasonable WAN/Leased-Link existing services. CPU/Mother-board/RAM speeds are keep improving, for WAN or any moderate speed network-links, we are now at a point that we can do huge data-processing via TrafficSqueezer on any basic high-end system.
Kernel vs User-space:
One can recollect for example IPSec is all Kernel solution, vs. OpenVPN is all User-space solution. Both have its own advantages and disadvantages.
ТраффицСкуеезер почетку неке три године уназад мислио да све то језгро решење, док је пред-алфа је направљен за тестирање неких изводљивости / прототипа током 2006-2007 у свим корисницима простора моду. Касније Алпха је први прави ТраффицСкуеезер у кернел простору, док је пред-бета за сада је још увек све кернела решење, али је ускоро пред-бета треба да се хибридни режим рада значи да оптимизација-модули би требало да буде доступна у кернел простору, неке би требало да буде доступна у корисника простора. Не може бити чак и случајевима где-као неке веома важне основне оптимизације-модули треба да добију подршку како у кернелу, као и корисника простора.Разлог за овај уврнути предлог је да, на основу захтева, против времена, вс Хардвер вс случајеви коришћења, корисници би требало да се више слободе да изабере онај који је најпогоднији за њих.
So this unique architecture is shown in the picture below:
Traffic Squeezer - Alpha, Beta
Ово је стварна производња издање очекује да обезбеди комплетан сет ВАН оптимизација технологије описане у документацији.Језгро саобраћаја Менгеле саобраћају оптимизације функционалности ће бити урађено у кернелу простору. Ово би свакако побољшати перформансе. У циљу да конфигуришете исто, корисник простора Цонфигуратион Утилити ће бити обезбеђен. Ово издање може да има две варијанте једне саобраћаја Менгеле који ради као Лаиер-2 моста и друге послове и потпуно подржава Лаиер-3 технологија засноване на ИП рутирање мреже и може интерворк у ИП преусмерава мреже.Рунтиме статистике саобраћаја стискивачем, конфигурацију и контрола исто се може постићи са корисником простора апликације. Овај кориснички апликација омогућава и Цомманд Лине Интерфаце (ИКЛ) и графичког корисничког интерфејса Веб базирани конфигурације интерфејса. У будућности, такође би требало да подржи даљински конфигурација кроз телнет и ССХ сесије.
The final Traffic Squeezer architecture is expected to provide a complete FLEXIBLE and MODULAR solution to the end-user, abstracting completely low-level functional operation details. So, this includes a unified look and feel Traffic Squeezer Application and a Traffic Squeezer Kernel Level Framework.
Application Objectives:
* Allows users to configure Traffic Squeezer (both GUI/CLI based)
* Show the runtime statistics of the same (both GUI/CLI based)
* Show graph of the periodic runtime statistics samples (only GUI)
Framework Objectives:
* Any layer of PDU compression (L2 Payload, Transport Layer Payload or Complete frame,refer Traffic Squeezer Documentation)
* Any software compression algorithm(s) can be plugged
* Software Level Compression (Kernel Space) or Hardware Level Compression (Refer figure below)
* Support any third-party compression hardware accelerator cards (Refer figure below)
* Any Physical Layer Network and its corresponding Data Link Layer
Traffic Optimization in Hardware
The kernel space Traffic Squeezer in future can have a facility of a platform to which any custom Traffic Optimization can be done through any custom hardware. This is expected to make possible with the pluggable driver interface within the Traffic Squeezer Framework.
Whereas, to perform traffic data processing in hardware, a dedicated third-party hardware accelerator card performs the same job. Controlling/configuring the same can be achieved with the existing Traffic Squeezer standard user-space interface.
Release - Pre-Alpha (Prototype Version)
The prototype version of the Traffic Squeezer is the first primitive version/stage to test some capabilities which is provided by Traffic Squeezer. It supports the functionality in the user space also the data compression and frame coalescing done only on Layer-2 frame payload. The objective Traffic Squeezer software is to provide users a better way of creating a compressed and optimized data communication tunnel between two peers through which the L2 frame payload gets compressed. These features are showcased in the Traffic Squeezer first Pre-Alpha version. However this version is still a demo version, the actual Traffic Squeezer usable software would be released from Traffic Squeezer Apha and subsequent Beta versions. Refer Documentation for details.
| Author/Founder: Kiran Kankipati - Copyright © (2006-2013) All rights reserved. - Project Launch Date: April 2006 | Last Revised: 19-Mar-2013 |
