Author Archives: Russ
Author Archives: Russ
I have lived through multiple toxic cultures in my life. It’s easy to say, “just quit,” or “just go to HR,” but—for various reasons—these are not always a good solution. For instance, if you are in the military, “just quit” is not, precisely, an option. So how should you deal with these sorts of bad situations?
Start here: you are not going to change the culture. Just like I tell my daughters not to date guys so they can “fix” them, I have never seen anyone “fix” a culture through any sort of “mass action.” You are not going to “win” by going to the boss, or by getting someone from the outside to force everyone to change. You are not going to change the culture by griping about it. Believe me, I’ve tried all these things. They don’t (really) work.
Given these points, what can you do?
Start with a large dose of humility. First, you are probably a part of a number of toxic cultures yourself, and you probably even contribute at least some amount of the poison. Second, you are almost always limited in your power to change things; your influence, no matter how right you Continue reading
The post Worth Reading: The CCDE Mindset appeared first on 'net work.
The post Worth Reading: IOS/XR in GNS3 appeared first on 'net work.
The post Worth Reading: Innovation at CIDR 2017 appeared first on 'net work.
The post Worth Reading: IPv6 server addressing strategies appeared first on 'net work.
The post On the ‘net: Considerations in Moving to an SDDC appeared first on 'net work.
The post Worth Reading: Every day is Monday in Operations appeared first on 'net work.
The post Worth Reading: Windows 10 steps up ransomware defenses appeared first on 'net work.
OSPF was originally designed in an age when processors were much less capable, available memory was much smaller, and link bandwidths were much lower. To conserve processing power, memory, and n-the-wire bandwidth, OSPF was designed using fixed length fields (FLFs). TLVs are more difficult to process than an FLF; to process a set of FLFs, you build a structure that mimics the FLF formatting, and simple “impose” it on the memory location where you have stored the data to be decoded, as shown below.
In the FLF model, the structure can simply be imposed on the memory locations, and the values can be read directly. In the TLV model, each type code must be read to determine the kind of information and the length must be read to determine the size of the field. Only once these two items in the TLV header have been read can the actual data be related to a particular field in the resulting data structure.
In the intervening years, however, compute, storage, and network capabilities have increased dramatically; the following chart, taken from a book I’m working on, shows this growth since about the start of the “network era.”
As compute, storage, and Continue reading
The post Worth Reading: Fix EULAs appeared first on 'net work.
The post Worth Reading: Internet routing detours appeared first on 'net work.
I’ve updated the generic icons linked from this page to include a virtual router/switch. I’ve also added two different spine and leaf topologies to the presentation. I may add other “generic” topologies over time, as I run across ones that seem worth including. These are completely public domain; I would encourage you to use them instead of the normal sets of vendor icons in drawing, books, blogs, etc.
Updated: Thanks to Greg Ferro, there is now a version of these in Omnigraffle! They’re linked on the same page.
The post Updated Generic Icon Set appeared first on 'net work.
The post On the ‘net: The background of I2RS appeared first on 'net work.
The post Worth Reading: Study highlights lack of IoT security appeared first on 'net work.
The post Worth Reading: Videos from ION Bucharest appeared first on 'net work.
Distributed Denial of Service is a big deal—huge pools of Internet of Things (IoT) devices, such as security cameras, are compromised by botnets and being used for large scale DDoS attacks. What are the tools in hand to fend these attacks off? The first misconception is that you can actually fend off a DDoS attack. There is no magical tool you can deploy that will allow you to go to sleep every night thinking, “tonight my network will not be impacted by a DDoS attack.” There are tools and services that deploy various mechanisms that will do the engineering and work for you, but there is no solution for DDoS attacks.
One such reaction tool is spreading the attack. In the network below, the network under attack has six entry points.
Assume the attacker has IoT devices scattered throughout AS65002 which they are using to launch an attack. Due to policies within AS65002, the DDoS attack streams are being forwarded into AS65001, and thence to A and B. It would be easy to shut these two links down, forcing the traffic to disperse across five entries rather than two (B, C, D, E, and F). By splitting the Continue reading