Videos :: Videos :: Telnet installation and remote access

Here is my second software development update of TOFFEE-Butterscotch. In the previous update (28-Oct-2016) I discussed about the Alerts, etc. Whereas in my first TOFFEE-Butterscotch news update I have introduced about TOFFEE-Butterscotch research, project specifications, use-cases, etc.

TOFFEE-Butterscotch yet another variant of TOFFEE can be used to save and optimize your Home/SOHO Internet/WAN bandwidth. Unlike TOFFEE (and TOFFEE-DataCenter) TOFFEE-Butterscotch is a non peer-to-peer (and asymmetric) network optimization solution. This makes TOFFEE-Butterscotch an ideal tool for all Home and SOHO users.

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

In case if you need to deploy TOFFEE along with your existing VPN devices you can deploy the same as shown below. This will allow your VPN devices to encrypt your TOFFEE WAN Optimized network data. NOTE: Make sure about the VPN deployment topology done in the right order. Else TOFFEE (LAN side) may get VPN encrypted packets which may not be possible (and or difficult) to further optimize. Hence always make sure to deploy them in a topology suggested below so that TOFFEE devices are out of VPN tunnel.

Here is a list of TOFFEE-DataCenter features supported. TOFFEE-DataCenter currently supports some of the important features such as loss-less network data compression, Packet Deduplication (protocols/applications supported), Application Acceleration, TCP Acceleration, dynamic MTU optimization, data packaging, hardware offload support, etc.

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.

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

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.

Seems there are couple of Inmotionhosting servers are down. And one of the server includes The TOFFEE Project website hosted server. I was in touch with the Inmotionhosting team trying to resolve the same. I found a unique issue that all my website files are intact and the Joomla database. But the Joomla database tables are completely wiped out and missing. Besides there is also a sort of upgrade going on in their servers. Luckily I have the most recent backup of the entire website.

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

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.

Here is my home lab monthly power-consumption readings for research. This will help to measure and monitor the overall power usage and assess the power requirements. This will help me in future purchases such as UPS, battery upgrades and so on. And as well remove replace old obsolete hardware with new less power-consuming devices.