Categories
Cloud Computing

Strong Network Security with ARPless – Hapless without ARPless?

In the realm of network security we tend to hear a lot of terms like “denial of service”, “man-in-the-middle”, or “session hijacking” and so on. For those deep into the networking and network security field, dealing with these terms is a real-life situation everyday.

Also, keeping up to date with the latest trends, software and solutions is a major part of the knowledge gathering practices.

Although it is near-impossible to have a 100% final solution to the serious issues of denial of service, man-in-the-middle, or session hijacking and similar others, SynchroKnot has approached the underlying cause to help substantially reduce and, in some cases, fully alleviate these issues.

For those unfamiliar, SynchroKnot software transforms any server, workstation, desktop or embedded device into a decentralized cloud or data center [data decenter] in minutes. You can use any commodity X86_64 Desktop/Workstation/Server/Embedded device and connect them to eachother. There is no need to purchase virtualization software [VMware, OpenStack, Hyper-V etc], switches & routers or storage [SAN/NAS].

ARPless is a part of SynchroKnot Spatial Defined Networking and works with the virtual machines of the tenants. It builds a secure vacuum of multi-dimensional layers of security starting with not allowing the virtual machine’s MAC address to be spoofed. Then, it only allows the communication between groups of virtual machines with their matching 28-bit Interstellar Identification assigned to their MAC addresses, and as a last step, securely and intelligently auto-responds to the virtual machines when they make an ARP request so that they always know who is who and where to go. This practically makes ARP spoofing, ARP cache poisoning, or ARP poison routing very difficult-to-impossible.

[It is advised to read the post earlier about Interstellars]

As an additional option, ARPless can be invoked with blockchain cryptography, which ensures that security policies, accountability and awareness are at the same level across the team(s), department(s) and organization(s).

Above is just a brief description. Below are some of the highlights:

■ ARPless creates a secure vacuum for trusted communication between virtual machines, and also with the existing physical infrastructure.

■ ARPless does not allow forced traffic diversion from poisoned ARP caches of virtual machines to reach undesired destination(s).

■ ARPless ignores requests from virtual machines that impersonate the original to force divert traffic or gain access.

■ ARPless securely and intelligently auto-responds to the virtual machines when they make an ARP request [ no agent / software needs to be installed inside the virtual machine(s) ]. It does not allow ARP requests from the virtual machines to get onto the network.

■ ARPless can further limit ARP traffic within the secure vacuum.

■ ARPless practically makes ARP spoofing, ARP cache poisoning, or ARP poison routing very difficult-to-impossible, which in turn substantially reduces the possibilities of other attacks stemming from it, such as denial of service, man-in-the-middle, or session hijacking.

■ ARPless intelligently handles and manages the following opcodes : 1 Request, 2 Reply, 3 Request_Reverse, 4 Reply_Reverse, 5 DRARP_Request, 6 DRARP_Reply, 7 DRARP_Error, 8 InARP_Request and 9 ARP_NAK

We have an excellent video to sharpen your skills at the link below.

■ Network Security with Arpless Interstellar

More information is available at:
■ synchroknot.com

Categories
Cloud Computing

Flood Ping Fun with 24 Switches in a Ring Topology!

This demonstration video shows a total of 24 Ethernet switches in one large loop [ Ring Topology ] with Satellite Tree Protocol enabled and multiple switches being brought down and up every 10 seconds while Flood Pings are underway from multiple directions!

The SynchroKnot Satellite Tree Protocol an enhancement to the IEEE standard [ 802.1D (1998|2004), 802.1W ] while keeping the core semantics in place, and is a part of SynchroKnot Spatial Defined Networking.

Satellite Tree Protocol is the core networking component of the SynchroKnot Cloud Computing and Data Center Decentralization software which transforms any server, workstation, desktop or embedded device into a decentralized cloud or data center [data decenter].

The object is to ascertain the automatic and fast network resilience [root bridge failure, failover and failback], fault tolerance and intelligent path selection capabilities amidst very low hardware resources.

This demonstration setup has been purposefully done with an illogical setting so as to test how it can perform in extreme circumstances.

Mininet is used for actual network emulation.

You may also notice results of prior flood ping tests in the demonstration video before the current one gets underway.

We would like to assume that the outcome result with 0% [zero percent] packet loss with 24 switches is a bit much for our logical mind to digest and would love to blame the ping utility with a faulty flood ping option 🙂 ….. of course upon deeper contemplation you may develop an insight that differs.

■ In actual use case scenarios, with our unique cabling technique in a 5 X 5 2-D Torus topology, one may generally not have more than one or two hops! 24 nodes are used for purposes of extreme testing in difficult case scenarios.

■ Simple machine with 2 cores [4 threads] Intel Core i7-6500U Processor with 8 GB RAM. Alongside, a few running virtual machines not a part of this demo were used in the background to consume CPU and memory resources, leaving fewer CPU cycles and memory for Satellite Tree Protocol and the 24 nodes with Mininet. [This demonstration video was also recorded on the same machine and thus used additional CPU cycles and memory.]

■ Side Note : Spanning Tree Protocol and Rapid Spanning Tree Protocol generally respond to failures by recovering in about 40 to 300 seconds or more depending upon the timers and topology [ RSTP may recover faster in some scenarios ]. This is with the regular vendor / standards suggested timers found in most switches in standard setups today. One can increase the network diameter [ i.e number of switches between two endpoints ] to a maximum of about 18. This however will substantially increase the recovery time, alongside most likely put the timers of switches out of sync. Your mileage may vary. Please do your own research.

■ Caution : If you try a similar setup with standard physical Ethernet switches [Cisco, Juniper etc] then you are solely responsible if you brick your appliance(es). We cannot help you recover them.

In brief, the SynchroKnot software transforms any server, workstation, desktop or embedded device into a decentralized cloud or data center [data decenter]. You can use any commodity X86_64 Desktop/Workstation/Server/Embedded device and connect them to eachother. There is no need to purchase physical or virtual switches and routers or any of their licenses [Eg. Cisco, Juniper etc].

This demonstration video is available at the link below and also on synchroknot.com under the the demo section:

■ Spatial Satellite Tree Protocol showing Root Bridge failure, failover, failback with Flood Ping from multiple directions

More information is available at:
■ synchroknot.com