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:

Network Latency and Bandwidth Assessment - for Network Admins and Infrastructure Architects ↗
Saturday' 13-Mar-2021

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

Detect and Monitor Failing Harddrive in Linux - My Seagate 500GB HDD Died ↗
Saturday' 13-Mar-2021
My 500GB Seagate Barracuda 7200RPM hard-drive suddenly started making mild clicking noise. I found this happening since morning. I was suspicious that something wrong in this drive and when I opened the Linux Disks app, I can find the cause of this issue. The disk is increasingly getting read errors. Besides I can see various other parameters such as Power-On Hours, Temperature, Head flying hours, etc.

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

TOFFEE Download :: TOFFEE-1.1.70-1-portable ↗
Saturday' 13-Mar-2021

TOFFEE (and TOFFEE-DataCenter) optimized Wireless Mesh-Networks - B.A.T.M.A.N [open-mesh.org (Open Mesh)] ↗
Saturday' 13-Mar-2021
TOFFEE/TOFFEE-DataCenter can be used to optimize Ad-Hoc Mobile Wireless Mesh-Networks. To learn more about the same here are some references: B.A.T.M.A.N. - https://en.wikipedia.org/wiki/B.A.T.M.A.N. Mobile ad hoc network (MANET) - https://en.wikipedia.org/wiki/Mobile_ad_hoc_network Wireless ad hoc network (WANET) - https://en.wikipedia.org/wiki/Wireless_ad_hoc_network open-mesh.org (Open Mesh) Wiki - https://www.open-mesh.org/projects/open-mesh/wiki

Watch on Youtube - [1888//1] Deep Space Communication - Episode1 - Introduction ↗


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 :: Optimized ISP backbone networks for countries with slowest Internet Speed ↗
Saturday' 13-Mar-2021

IP Header Compression in WAN Links and TOFFEE-DataCenter WAN Optimization ↗
Saturday' 13-Mar-2021

Timelapse Screen Capture of TOFFEE-DataCenter Network Acceleration - with new RRDtool graph support ↗
Saturday' 13-Mar-2021
Timelapse Screen Capture of TOFFEE-DataCenter Network Acceleration - with new RRDtool graph support



Featured Educational Video:
Watch on Youtube - [943//1] x23e TrueNAS ZFS Pool Resilver over and over again issue | ZFS NAS Storage | Forever Resilver ↗

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-Mocha WAN Emulation software development - Update: 20-Oct-2016 ↗
Saturday' 13-Mar-2021
I was doing some specific tests in my TOFFEE and TOFFEE-DataCenter (WAN optimization) scenarios such as variable upload and download speeds. And I was also doing some experiments with speedtest.net and I did some of these tests with TOFFEE-Mocha. I realized there is a case that I can introduce asymmetric constant delays so that you can get different download speed and a different upload speed. And in some cases much faster download speeds and relatively slower upload speeds.

TOFFEE-Mocha WAN Emulation software development - Update: 16-June-2016 ↗
Saturday' 13-Mar-2021
I started TOFFEE-Mocha WAN Emulation software development on 1-June-2016. I took the existing TOFFEE components as a base. Although the TOFFEE-Mocha is entirely an independent fresh Open-Source WAN Emulation solution. Ever since I am in the process of defining and inventing features. So far I come up with the most important feature which is expected to be present in any WAN Emulation software is the packet delay option.

TOFFEE-Mocha - WAN Emulator :: TOFFEE-MOCHA-2.0.3-0-10-nov-2018-x86-64.iso ↗
Saturday' 13-Mar-2021
Download TOFFEE-MOCHA-2.0.3-0-10-nov-2018-x86-64.iso via Google Drive share: Live bootable x86-64 Debian Stretch 9.5 with light-weight LXDE UI ISO (includes source-code): TOFFEE-MOCHA-2.0.3-0-10-nov-2018-x86-64.iso You can find the source tar-ball in the /root folder. To know more about the project kindly refer TOFFEE- Mocha: News and Updates - Documentation. To know more about current specific release, objectives, features, release notes/updates, quick demo and future road-map, you can watch my video below.




IP Header Compression in WAN Links and TOFFEE-DataCenter WAN Optimization ↗
Saturday' 13-Mar-2021



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