DOCUMENTATION 》 TCP Tune-up and Performance Analysis Graphs - Congestion Control - Research - Dos and Don'ts

Here is my first software development update of TOFFEE-Butterscotch. In my first TOFFEE-Butterscotch news update I have introduced about TOFFEE-Butterscotch research, project specifications, use-cases, etc. Introducing TOFFEE-Butterscotch Alerts: These are simple packet counters which corresponds to the filter type. For example if the incoming TCP-SYN packets are blocked then its corresponding alert counter will increment whenever such a packet arrives and gets filtered (dropped).

When you build a WAN Optimization device with TOFFEE the entire packet processing (data optimization) takes place in software layer or in other words more precisely Operating System kernel space. However if you have any compression or encryption hardware accelerator hardware card the parts of the TOFFEE packet processing modules can be offloaded to hardware layer and thus improving its efficiency.

Timelapse Screen Capture of TOFFEE-DataCenter Network Acceleration - with new RRDtool graph support

PiPG is a powerful and yet simple Raspberry Pi Network Packet Generator. With PiPG you can now fabricate custom network packets and send via any Network Interface. Supports all kinds of standard Network Ports (Linux Kernel driver generated) such as Physical Network Interface ports, and an array of virtual ports such as loopback, tun/tap, bridge, etc. indispensable tool for: Network Debugging, Testing and Performance analysis Network Administrators Students Network R&D Protocol Analysis and Study Network Software Development Compliance Testing Ethical Hackers you can generate the following test traffic: L2-Bridging/Slow protocols: STP, LACP, OAM, LLDP, EAP, etc Routing protocols: RIPv1, RIPv2, IGMPv1, IGMPv2, OSPF, IS-IS, EIGRP, HSRP, VRRP, etc Proprietary protocols: CISCO, etc Generic: IPv4 TCP/UDP, etc Malformed random packets

Here is a step-by-step DIY to build your own Intel based Mini PC WAN Optimization Device with TOFFEE. I chose this below Intel Celeron Mini PC since it is fan-less aluminium case and as well it has 2 dedicated inbuilt Gigabit Ethernet ports. You can use one for LAN Network and one for WAN Network.

Here is my power-consumption measurements of various devices deployed within my home lab. I measured via my kill-a-watt sort of power-meter which is fairly reliable and accurate. I checked its accuracy with various standard load such as Philips LED laps and other constant power-consuming devices to make sure that the power-meter is precise.

This is my next software development update of TOFFEE-DataCenter which I am working since past few weeks. I was very busy in implementing the core TOFFEE-DataCenter components along with prototyping, benchmarking, implementing and testing the same. However today is the first time ever I did a fresh new CLI interface for the upcoming new TOFFEE-DataCenter.

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).

Network Packet Queue or Buffer - Packet Flow Control, Fragmentation and MTU

When you are dealing Deep Space Networks (DSN) one among the most challenging parts is the Interplanetary distances and communicating data across such vast distances. This is where we are not dealing with common Internet type traffic such as HTTP/FTP/VoIP/etc but it is completely different when it comes to DSN so far. So optimizing data in DSN becomes mandatory. For example if you think one of the Mars Rovers, they have used LZO lossless compression.

Currently what we have is a single homogeneous (sort of) WWW Internet. Which we can consider as a single-dimensional network. What I propose is that we can create complete independent multiple Internets with each Internet having its own IP-address space, Domain namespace and an authority to manage Domain names. And these networks/Internets can be entirely IPv4 only based or IPv6 only based.