Layer 2 Testing

I downloaded this package this evening. It has to be compiled.

Works a bit like iPerf in a certain kind of way. You have to run a server on one side and a client on the other side.  Unfortunately I only had one Layer 2 side available to test. I will set up the other one - a Raspberry Pi - and then attempt to "ping" - via Layer 2 - between the two boxes.

https://dazdaztech.wordpress.com/2013/08/27/layer-2-ping/

Note: There's more to the story. I am using a virtual Layer 2 stack to do this.

WebRTC

I guess this is a communications platform that slme guys are working on in the lab. Until I know more.

VRRP

Someone today was running VRRP on a box as a clustering / load balancing mechanism.

Did some reading to discover that this is in a family called  FHRP - First Hop Redundancy Protocols.

There are three 'competing' protocols in this class:
VRRP - Virtual Router Redundancy Protocol
GLBP - Gateway Load Balancing Protocol
HSRP - Hot Standby Router Protocol

VRRP is the only open (IEEE) one (HSRP is Cisco).
UPDATE: NOTE: Both Cisco and IBM are claiming patents on VRRP, based on what I saw on Wikipedia for VRRP. But per Wikipedia, some executive at Cisco has made a statement (to Wikipedia, or publicly such that Wikipedia has listed it on the site) that they will not be enforcing patent claims. 

I am reading comparisons, but so far they look very similar with VRRP being slightly more advantageous(?) with faster hello.

Next, we will examine VRRP implementations.

Python

In a group discussion, it was decided that Python was a scripting language worth learning.

I'll look into this...post more on this when I do.

Where are databases headed in 2016?

http://www.planetcassandra.org/what-is-nosql/

First article on the topic of NoSQL and database technology.

This came up when I heard that development was going to implement Cassandra.

systemd article slash editorial

Doing some reading on systemd, and found this interesting article.

I come from the old SystemV Release 4 days, so some of this new-fangled stuff like systemd has a bit of a learning curve adjustment (old dog new tricks).

The author here writes an editorial opinion on systemd.

http://www.infoworld.com/article/2608798/data-center/systemd--harbinger-of-the-linux-apocalypse.html

The sysctl interface for system tuning on Linux

I looked into sysctl mainly because of the fact that the TuneD package (used to tune systems dynamically with specific pre-created system profiles) relies on sysctl parameters.

I found a useful article on sysctl in Linux Journal, which I will post here.

http://www.linuxjournal.com/article/2365?page=0,0

In summary, the /proc folder in Linux is essentially the 'portal' to the kernel parameters. While some are locked down and cannot be tinkered with, others (in /proc/sys) are available for configuration.

This is not for the novices. Understanding the parameters themselves is a daunting task; something that only kernel developers used to understand by being thoroughly familiar with the kernel source code. Playing and tinkering with the parameters can absolutely cripple a system if you don't know what you're doing.

But - it is good to understand the architecture and facilities within Linux. And understanding sysctl; what it is, why it is there and what it is used for - is certainly something important if you're going even remotely consider calling yourself a Linux geek.