The TOFFEE Project HOMEDOCUMENTATIONUPDATESVIDEOSRESEARCHDOWNLOADSPONSORSCONTACT ☰


DOCUMENTATION 》 TEST CASES :: TEST RESULTS :: TOFFEE-Mocha-1.0.32 asymmetric constant packet delay feature

Here are the TOFFEE-Mocha test cases and test results of new asymmetric constant packet delay feature supported in the new TOFFEE-Mocha-1.0.32 release. Click HERE to download TOFFEE-Mocha-1.0.32-1-x86_64.tar.xz and TOFFEE-Mocha-1.0.32-1-i386.tar.xz.

Here is my test network topology:
TOFFEE-Mocha asymmetric packet delay test setup

Test case1 :: no packet delay: This is a reference test with no packet delay.
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case1 - no packet delay 

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1.34 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=1.34 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=1.36 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=1.43 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 1.343/1.372/1.432/0.057 ms
kiran@WD-250GB:~$

Test case2 :: 1ms per packet delay: This will enable 1ms constant packet delay for all packets (i.e upstream and downstream).
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case2 - 1ms per packet delay 

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=3.38 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=3.28 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=3.49 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=3.34 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 3.288/3.377/3.493/0.094 ms
kiran@WD-250GB:~$

Test case3 :: 1ms upload alone packet delay: This will enable 1ms constant packet delay for all upstream packets alone.
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case3 - 1ms upload alone packet delay 

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.49 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.51 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.32 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=2.30 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 2.300/2.408/2.515/0.108 ms
kiran@WD-250GB:~$

Test case4 :: 1ms download alone packet delay: This will enable 1ms constant packet delay for all downstream packets alone.
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case4 - 1ms download alone packet delay 

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=2.31 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.33 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=2.41 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=2.41 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 2.313/2.367/2.416/0.067 ms
kiran@WD-250GB:~$

Test case5 :: 1ms download packet delay + 1ms per packet delay: This will enable 1ms constant packet delay for all downstream packets along with constant 1ms per-packet delay.
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case5 - 1ms download packet delay + 1ms per packet delay 

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=4.36 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=4.34 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=4.43 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=4.46 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 4.342/4.401/4.465/0.049 ms
kiran@WD-250GB:~$

Test case6 :: 1ms upload packet delay + 1ms per packet delay: This will enable 1ms constant packet delay for all upstream packets along with constant 1ms per-packet delay.
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case6 - 1ms upload packet delay + 1ms per packet delay 

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=4.26 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=4.46 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=4.35 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=4.47 ms
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 4.260/4.389/4.472/0.087 ms
kiran@WD-250GB:~$

Test case7 :: 1ms upload packet delay + 1ms download packet delay + 1ms per packet delay: This will enable 1ms constant packet delay for all upstream and downstream packets along with constant 1ms per-packet delay.
TOFFEE-Mocha-1.0.32 WAN Emulator network test tool Test case7 - 1ms upload packet delay + 1ms download packet delay + 1ms per packet delay 

kiran@WD-250GB:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=5.26 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=5.41 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=5.66 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=5.31 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=5.37 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=5.29 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=5.41 ms
^C
--- 192.168.0.1 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6009ms
rtt min/avg/max/mdev = 5.260/5.391/5.662/0.130 ms
kiran@WD-250GB:~$


Suggested Topics:


TOFFEE-Mocha - WAN Emulator


Categories

💎 TOFFEE-MOCHA new bootable ISO: Download
💎 TOFFEE Data-Center Big picture and Overview: Download PDF

Recommended Topics:

Raspberry Pi as a Networking Device ↗
Saturday' 13-Mar-2021
Raspberry Pi is often used as a single board computer for applications such as IoT, hobby projects, DIY, education aid, research and prototyping device. But apart from these applications Raspberry Pi can be used for real-world applications such as in making a full-fledged networking devices. Raspberry Pi is a single board ARM based hardware which is why it is also classified as ARM based SoC. Since it is ARM based it is highly efficient, tiny form-factor and lower in power consumption with moderate computational power. This will allow it to work several hours on emergency battery backup power supply such as low-cost domestic UPS and or some renewable energy source, which is a prerequisite for a typical networking device.

The TOFFEE Project :: TOFFEE :: WAN Optimization ↗
Saturday' 13-Mar-2021
TOFFEE is an open-source WAN Optimization (Network Performance Optimization) software which can be used to optimize your critical networks.

TOFFEE Benchmarks :: TOFFEE-1.1.28 ↗
Saturday' 13-Mar-2021
Here is the TOFFEE WAN Optimization benchmarks of the TOFFEE version: TOFFEE-1.1.28. This is the current TOFFEE development version till date (2-Jul-2016). This is a HPC TOFFEE variant meant for high-end custom build servers and high-end desktops (i.e High Performance Computing a.k.a HPC). TOFFEE built this way often needs customized kernel compilation and build such as processor specific and hardware specific tune-ups since it is highly CPU intensive (if not offloaded via Hardware Accelerator Cards).

Upgrading Ubuntu 17.10 to 18.04 via TOFFEE-DataCenter WAN Optimization Screenshots ↗
Saturday' 13-Mar-2021

Riverbed and Silver Peak WAN Optimization vs TOFFEE-DataCenter (TOFFEE and or TrafficSqueezer) - FAQ ↗
Saturday' 13-Mar-2021

TOFFEE-DataCenter - First Live Demo and software development - Update: 26-Aug-2016 ↗
Saturday' 13-Mar-2021
Today I have done a test setup so that I can able to connect my Android Samsung Tab via TOFFEE DataCenter. Below is my complete test topology of my setup. For demo (and research/development) context I configured TOFFEE DataCenter in engineering debug mode. So I do not need two devices for this purpose.


Building my own CDN - choosing a web-hosting to deploy my CDN - Update: 28-July-2016 ↗
Saturday' 13-Mar-2021
The TOFFEE Project website is hosted on Inmotion Hosting. And so I am looking for alternate hosting provider to build my first CDN node. My plan is to make multiple sub-domains of my website such as cdn1.the-toffee-project.org, cdn2.the-toffee-project.org and point each of this corresponding subdomain(s) to various alternative web hosting servers geographically spread across the world. Sometimes choosing the same vendor for multiple CDN nodes may result multiple servers existing in the data-center. And this becomes an issue if there is some catastrophic network disaster.

TOFFEE-DataCenter a TOFFEE variant for Data Center applications ↗
Saturday' 13-Mar-2021

TOFFEE-DataCenter packet packaging feature for WAN Optimization ↗
Saturday' 13-Mar-2021

Tweaking Network Latency - Live Demo - via TOFFEE-DataCenter ↗
Saturday' 13-Mar-2021


Featured Educational Video:
Watch on Youtube - [1836//1] x257 tp-link UE300 Linux Kernel Realtek Driver Codewalk rtl8153a-3 r8152 USB 3.0 to Gigabit - Part1 ↗

Setting up a WAN Emulator within VirtualBox ↗
Saturday' 13-Mar-2021

TOFFEE-Mocha Documentation :: TOFFEE-Mocha-1.0.14-1-x86_64 ↗
Saturday' 13-Mar-2021

TOFFEE (and TOFFEE-DataCenter) optimized Mobile Wireless Backhaul Networks ↗
Saturday' 13-Mar-2021
TOFFEE can be used to optimize expensive Wireless backhaul network infrastructure. TOFFEE can be deployed over existing slow or often outdated old backhaul networks too. This will leverage mobile ISPs and network service providers to reduce their bulk IT CapEx and OpEx Costs.

Tweaking Network Latency - Live Demo - via TOFFEE-DataCenter ↗
Saturday' 13-Mar-2021


VPN Network Optimization via TOFFEE WAN Optimization ↗
Saturday' 13-Mar-2021
VPN Networks may degrade network performance due to various packet processing overheads such as encryption and by adding extra network protocol header(s) (such as IPv4/IPv6, IPSec, etc). This may inflate near MTU sized packets and causes excessive packet fragmentation. Here are the few examples of packet processing involved in a VPN (or a VPN like) Tunnel. With TOFFEE you can optimize these packets even before they get processed on to a VPN device. TOFFEE optimizes packet contents (application payload and transport headers) so that these TOFFEE optimized packets when they get processed by VPN devices (or VPN software stack) they may never need further packet fragmentation. Here is a deployment scenario of TOFFEE with VPN devices.


Research :: Optimization of network data (WAN Optimization) at various levels:
Network File level network data WAN Optimization
Learn Linux Systems Software and Kernel Programming:
Linux, Kernel, Networking and Systems-Software online classes
Hardware Compression and Decompression Accelerator Cards:
TOFFEE Architecture with Compression and Decompression Accelerator Card [CDN]
TOFFEE-DataCenter on a Dell Server - Intel Xeon E5645 CPU:
TOFFEE-DataCenter screenshots on a Dual CPU - Intel(R) Xeon(R) CPU E5645 @ 2.40GHz - Dell Server