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:

YouTube Video Network Traffic Optimization - WAN Optimization Demo ↗
Saturday' 13-Mar-2021

How to check a website using CDN ? ↗
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.

TOFFEE-Mocha WAN Emulation software development - Update: 15-July-2016 ↗
Saturday' 13-Mar-2021
Today I completed doing all the changes which are meant for the new upcoming TOFFEE-Mocha release. I have increased the resolution and the range of all factor variables. Instead 1 to 10 range now they have a range of 1 to 30. Unlike before the value 1 means it is lot more intense (or in some cases less intense) and the uppermost value 30 means lot less intense (or in some cases lot intense).

TOFFEE deployment topology guide ↗
Saturday' 13-Mar-2021
Assume you have two sites (such as Site-A and Site-B) connected via slow/critical WAN link as shown below. You can optimize this link by saving the bandwidth as well possibly improve the speed. However, the WAN speed can be optimized only if the WAN link speeds are below that of the processing latency of your TOFFEE installed hardware. Assume your WAN link is 12Mbps, and assume the maximum WAN optimization speed/capacity of Raspberry Pi is 20Mbps, then your link will get speed optimization too. And in another case, assume your WAN link is 50Mbps, then using the Raspberry Pi as WAN Optimization device will actually increase the latency (i.e slows the WAN link). But in all the cases the bandwidth savings should be the same irrespective of the WAN link speed. In other words, if you want to cut down the WAN link costs via this WAN Optimization set up, you can always get it since it reduces the overall bandwidth in almost all the cases (including encrypted and pre-compressed data).

TOFFEE-Butterscotch Documentation :: TOFFEE-Butterscotch-1.0.11-rpi2-23-nov-2016 ↗
Saturday' 13-Mar-2021
TOFFEE-Butterscotch Documentation :: TOFFEE-Butterscotch-1.0.11-rpi2-23-nov-2016



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.

My sample Wireshark packet capture files for research ↗
Saturday' 13-Mar-2021
I have a huge repository (or collection) of sample Wireshark packet capture files for reference. I use them extensively for research and development of TOFFEE as well to understand various protocol PDUs and protocol standards. I personally collected various test captures via Wireshark during my test and experimental research setup during the course of TOFFEE development. Say if you are a student and learning Networking and or say VoIP data and VoIP packets, you can analyse my VoIP sample Wireshark captures. Or in other case assume you are doing some quick research (or development) and want to refer few handful of VoIP packets then you can download and analyse my sample packet capture files.

TrueBench - Linux CPU Benchmarking system ↗
Saturday' 13-Mar-2021
TrueBench is an unique open-source benchmarking system in which the core system performance and efficiency parameters are measured at extreme high resolution in the order of several million/billion ยต-seconds for a given specific task. TrueBench is a part of The TOFFEE Project research.

CDN Introduction - Content Delivery Networks or Content Distribution Networks ↗
Saturday' 13-Mar-2021



Featured Educational Video:
Watch on Youtube - [89//1] B.E and M.E Final Year Projects - Form your Team ↗

TOFFEE-DataCenter WAN Optimization :: TOFFEE-DATACENTER-1.3.25-1-portable ↗
Saturday' 13-Mar-2021
Download TOFFEE-DATACENTER-1.3.25-1-portable.tar.xz via Google Drive share: platform independent (portable) source: TOFFEE-DATACENTER-1.2.2-1-portable.tar.xz * Alternatively download from SOURCEFORGE project site. * Here are the TOFFEE-DataCenter supported features. * To know more about the project kindly refer TOFFEE-Datacenter Documentation, News and Updates

TEST CASES :: TEST RESULTS :: Raspberry Pi WAN Emulator TOFFEE-Mocha-1.0.14-1-rpi2 ↗
Saturday' 13-Mar-2021

My Lab Battery Purchase and Service logs for Research ↗
Saturday' 13-Mar-2021
Here is a complete log of my lab battery purchase, service record which I maintain in Google drive. These I use for my home (or my family generic use) as well as a part of my home lab. I maintain a detailed log this way to monitor the failure rate of these batteries. This will allow me to select a specific brand/model which has higher success rate and to monitor any premature failure/expiry. The service log helps me to monitor and schedule the next service routine so that I can maintain these batteries in tip-top condition.

TOFFEE-DataCenter with GlusterFS Storage Cluster ↗
Saturday' 13-Mar-2021




Bitcoin Mining - Blockchain Technology - Network Optimization via TOFFEE Data-Center WAN Optimization ↗
Saturday' 13-Mar-2021
Bitcoin Mining - Blockchain Technology - Network Optimization via TOFFEE Data-Center WAN Optimization



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


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