Skip to main content

Make a Connection: What Is a Network?


The term "network" has been defined countless times. If there is anything I have learned about something being repeated many times, it means it is important. With networks, that is no different. I defined networking previously and briefly - a collection of devices that receive and transmit data amongst each other. Yet, it truly does not do it justice. I just finished my first co-op iteration at Motorola Solutions. Entering this new opportunity for me was more than just a foot in the door in the field of networking. I got to see critical infrastructure that transmitted and received signals relayed from first responders' and public sector communications. Long story short, I got to see the inner workings of a network, especially how different media and architecture converges to keep communications clear and functioning.

Humanizing Networks

 The world's networks, big and small, have been compared to:
  •  Extensive highways that carries information across "tolls", experiences "heavy traffic", and gets off its "exit" to reach its destination
  • A series of post offices and mail people delivering our precious packages and mail to its proper destination to its intended recipient

If you think about it, these analogies humanize networks into everyday life.  This brings up another analogy and one I am quite fond of: the backbone of communication. An average adult human grows to have 24 bones that make up the vertebrae or backbone. All these bones come together to provide vital functions, such as support, protection, and connection points. Those are the exact functions, amongst others of course, of today's networks. 

Today's networks are made of many middleboxes, media, and messages traversing the biggest network of them all - the Internet - and even within our own homes. Without these guiding centers and lines, our e-mails, videos, and smart homes and devices will not operate effectively, or at all. Just as how our vertebrae keep us upright and we would protect it from damage, a lot goes into keeping the Internet, routers, firewalls, cables and security mechanisms operational. 

An Internet Behind-the-Scenes Look

Let's take a behind-the-scenes look. If you accessed this blog, you more than likely reached here using a web URL - a Universal Resource Locator. Whether you looked it up or via a link, there was a process for you to get this web resource. Thanks again for coming, by the way! The first few letters of that web address should be https. Have you ever thought about what that means? Well, first, it means HyperText Transfer Protocol Secure. Actually, I mean how does it come about - its origin. That is an example of a protocol. 

We are familiar with protocols. Generally, a protocol is usually a set of rules or codes that we follow that keeps society going, whether it is a dress code, dealings within a business, or proper etiquette around the dinner table. Computer networks, and especially the Internet, follows protocols. A protocol is a set of rules that determines how different communications between devices and services operate. Clearly, there is a protocol for when we browse the Web (HTTPS/HTTP), but there are also protocols when it comes to sending and receiving an email (SMTP/IMAP), videoconferencing and streaming TV (SIP/UDP), reliable transfer (TCP), and thousands other applications. 

The Internet is quite complex, and it is always changing. Not just because of news stories, social media posts, and new technologies, but as to what keeps it going in an orderly fashion. To help with that order and prevent it from being a digital Wild West, there is an international organization that standardizes Internet protocols - the Internet Engineering Task Force. The IETF publicly records these standards and protocols in readily available documents. This transparency has allowed us to understand how the Internet works and further updates to achieve their goal: "to make the Internet work better". (IETF) 

The most interesting thing about the IETF is that anyone can join. Not sponsored, but the amount of content online and in video form on YouTube is something that caught my eye. Learn more about them at their site. 

What's Next?

I can keep going. I love networking because it is foundational. Everything builds from it. Maybe that is the inspiration even behind the blog name, NodeConnect. A network is essentially devices, or nodes, connecting. The thing is - this happens on different levels. That's right! From your Bluetooth headphones to the network beast of them all - the Internet, there comes a different architecture that caters to its users and scope. Doing networking justice is always going to evolve, but it all begins with the Tim Duncan of facts - "the Big Fundamentals" of networking. 

 

   

   

Labels:

Comments

Post a Comment

Popular posts from this blog

IP in Practice: Special IPv4 Addresses

We have already discussed three private ranges used in classful and classless subnetting. The list does not stop there. This post identifies six types of special IP addresses that you will encounter. By the end of this post, you should have a clearer understanding of how these addresses are used in troubleshooting, how they appear on certification exams, and how they shape the way traffic moves across the Internet. 1. Loopback Address (127.0.0.1) Every networked device has a loopback address. Most commonly, it is 127.0.0.1 . The loopback address is typically used to test internal connections. You may wonder, “Why do I need to know if my device can connect to itself? Shouldn’t it connect to other resources and the Internet?” Think about it this way. Before you walk out the door, you make sure you look presentable by taking a shower, brushing your teeth, ironing your clothes, and checking yourself in the mirror. Once everything looks good, you are ready to go. Similarly, your compute...
Post a Comment
Read more

How to Set Up a Cisco Router as a DHCP Server (Step-by-Step Guide)

Lab time! Want to build a DHCP server?  In this lab, I will show you how to build your own DHCP server on a router using Cisco Packet Tracer, as shown above. By the end of this post, you will be able to create your own DHCP server with a Cisco 2911 router, perhaps in a home lab setting, and prepare you to build your own on other hardware.  Why a Router?  A DHCP server is a centralized, automated service that assigns important network configuration details to devices on a network, such as IP addresses. Without it, we would have to create manual entries for our entire network, which can be time-consuming and lead to errors. Traditionally, there are dedicated servers to handle these functions. There are many ways to implement a DHCP server in your topology, including a dedicated physical server, a virtual machine, cloud-based gateways, and firewalls. However, there are specific benefits to using a router as your DHCP server: Reduced infrastructur...
Post a Comment
Read more

New Series: IP in Practice

I have done a few posts on subnetting and the inner workings of DHCP. I wanted to do a post on IPv6 and a hands-on demo on implementing DHCP on actual networking equipment. However, I missed a few parts that I would like to cover that would particularly help in understanding how IP works and why it is needed. Unlike the previous series, this will be a direct approach to a certain protocol: Internet Protocol (IP). I recently started my first series, covering important ports, protocols, and acronyms used in the networking field. However, I realized not only is it difficult to address the ones to mention, but for some letters it's hard to find. The intended structure was to have several per letter not just one. The idea seemed fun and engaging, however, doing over 20 posts alphabetically on acronyms, ports, and protocols lacks order and deviates from the direct approach I want this blog to have. For that reason, I am putting it on hold indefinitely. It was fun at first, but it was not...
Post a Comment
Read more