Router fundamentals you should know

Routers are core to broadcast networks. These concepts regarding networking will help you understand how routers work.

What is in this article?:

  • Router fundamentals you should know
  • Route

Routers are core to broadcast networks. So, I want to introduce some fundamental concepts regarding networking that may help you understand how routers work.

Ethernet

Ethernet is both a protocol and a hardware specification. The Ethernet specification details electrical signals and voltages on the wire (or the RF transmission scheme in the case of wireless), and it lays out how Ethernet packets are built and what information Ethernet headers contain. Headers contain source and destination addresses. This helps routers direct packets to destination. Ethernet addresses differ from IP addresses.

Ethernet addresses (sometimes called MAC addresses) appear as: nn:nn:nn:nn:nn:nn (six groups of two hex digits). These are hardcoded into network interface chips on a specific computer and typically cannot be changed. Think of MAC addresses as Vehicle Identification Numbers stamped into engine blocks of cars. Ethernet is defined by the IEEE in its 802-x family of standards.

IP

IP is a core protocol. Its job is to move datagrams from one device to another. (A datagram is defined as a self-contained, independent entity of data. It carries sufficient information to be routed from a source to the destination computer without reliance on earlier exchanges between the source and destination computer and transporting network.) The IP layer prepares data sent to it by applications or other higher protocols for transmission across a specific network (an IP network), taking into account things such as packet length, hardware addressing structure and how data should split across multiple packets.

IP packets are the payload carried in Ethernet packets in an “IP over Ethernet” network (about 95 percent of all network installations). MAC addresses may be hardcoded, but IP addresses can be changed in the network configuration menu of almost all modern operating systems. IP is defined by the Internet Engineering Task Force (IETF) as Internet Standard 5.

Once a physical network is in place (wires, connectors, switches, etc.), equipment can be connected to it. With Ethernet and IP, the capability exists to identify specific equipment as packet sources and destinations. And, the means are available to logically group equipment into networks and pass messages from one network to another. But, another protocol is critical to the network functioning.

ARP

Here is a question: What mechanism associates the MAC address and, therefore, a specific physical piece of hardware, with an IP address?

Address Resolution Protocol, or ARP, provides the solution. Figure 1 shows an actual ARP transaction captured using Wireshark — a free packet capture and inspection tool. Assume a router with an IP address of 192.168.1.1 needs to send a packet to 192.168.1.43. The router will send an ARP request asking, “Who has 192.168.1.43? Tell 19.2168.1.1.” The computer with that IP address responds, “192.168.1.43 at 00:15:53:7C:22:5C.” The router then knows where the packet should go. In most cases, once the router has this information, it stores it in its ARP table for memory. ARP is defined in IETF Internet Standard 37.

Now that the IP address to MAC address question has been resolved, the network is almost ready to go. Packets can be sent from one computer to another on the same network, but what about from one network to another?

Route »

Discuss this Article 7

Brad Dick
on Oct 19, 2012

Reader comment:

Thank you so much for taking the time to write the great article on network protocols Router Fundamentals. I have been looking for a simplified explanation of this for some time. I have purchased several books, but usually find them a bit too deep, but now that I have read your article the "light has come on" and I understand this technology much better. I now can go back and re-read some of these books with more clarity. Thanks again.
If you have any suggestions on further reading material, I would love to see it.

R. Miller Jr. | Computer Broadcast Technician

Brad Dick
on Oct 19, 2012

Brad Gilmer responds:

I am very glad to receive your email. I have had a similar experience with many router protocol books, so it is good to know that the article helped.

Regarding further reading, I have several suggestions. First, it helps if you have a specific problem you are trying to solve, or a particular protocol you need to learn more about. With that in mind, I typically go to the bookstore and look through whatever is on the shelf until I find a book that specifically addresses what I need to know, but also is written in a way I can understand. Then I buy it. Sometimes this is the rub - these books tend to be expensive, especially considering that I usually only need a single chapter, or maybe even a part of a chapter.
But I find if I buy the book, study it, and then use it to resolve my problem, then I retain the information much better. In this case, I do not have a specific book - any book will work well as long as you can understand it. Second, if you are trying to understand how routers and protocols work, you should download a copy of Wireshark (http://www.wireshark.org). This free packet capture software is just about the best thing going if you really want to understand how protocols work. Get out the book you just bought, look at the descriptions and the diagrams for the protocol you are curious about, and then open Wireshark, capture some network traffic and then look specifically at what that protocol data looks like on the wire. This can be *extremely* helpful. If you are studying an obscure protocol, a quick Internet search for a wireshark capture with the protocol name usually yields a pre-captured file you can feed into Wireshark to play with.

As for specific books, I have two recommendations, both from O'Reilly:
- Internet Core Protocols, the Definitive Guide by Eric A. Hall This book gives you a great overview of the protocols that drive the Internet. If you understand what is in this book, you will be miles ahead in dealing with issues surrounding Video over IP, because after all, we are talking about putting video on an IP network.

- DNS and BIND by Paul Albiz and Cricket Liu This might seem like a strange recommendation, but it is really important to understand how IP addressing works, how computers find each other over the Internet. Understanding the DNS system can save you hours of troubleshooting time since frequently DNS problems manafest themselves as IP connectivity issues. Being able to quickly tell if you have a DNS problem or a connectivity problem is a key skill.

I hope this helps, and thanks again for the feedback!

sivakumar (not verified)
on Oct 21, 2012

Thanks for the details,
i want to know more about using sdi to ip encoders,decoders via public network and tips regarding it

ddisiva (not verified)
on Oct 21, 2012

please give more tips regrding using sdi to ip encoder and decoders using pubblic network and leased fib.
thanks
Sivakumar, Broadcast Enginner

Brad Dick
on Nov 8, 2012

Reader comment:

I thought Brad Gilmer’s primer on network fundamentals was brilliant and probably very useful to newbies just coming to IP networks. But I think he missed the chance to describe the fundamental differences between MAC and IP addresses. The former are physical addresses, unique in the world and tied to a specific LAN. The latter are logical addresses and can be freely reused. That’s why you can have a network on your side of the router that’s numbered 192.168.1.1 and so can I. But you can’t have an adapter with the same MAC address as I do, even if they are separated by non-interconnected routers.

Finally, thanks for responding to my initial press release as Zixi’s marketing guy. Is this the kind of news you ever use on your website?

I look forward to meeting you at an industry event.

Thanks.

Best,
Alex

Brad Dick
on Nov 8, 2012

Mr. Gilmer responds:

Hi Alex,

Thank you very much for your comment. You are right of course – Layer 2 MAC addresses are distinctly different from Layer 3 IP addresses. I like to think of the MAC address as a Vehicle Identification Number (VIN) on a car, and the IP address as the license plate. You can change the license plate, but the VIN is stamped into the engine block at the factory and cannot be changed. And you are also correct that there is a very significant difference between public IP address and private IP addresses. And lastly, it is very useful to understand how routers associate IP addresses with MAC addresses through ARP tables. All of these are good topics for books, let alone for a 1200 word article. So every month I have to choose a topic and focus on it, knowing that there are many details left unaddressed (that was a joke).

Anyway, I have received similar comments that the tutorials have been very helpful, and Brad Dick and I have discussed spending more time on networking basics. The topics you mention are all good ones for articles – and interestingly, I have covered all of them in depth as single-topic columns before. But repetition may be good, especially for very important fundamental subjects.

Thanks again for your feedback.

Brad Gilmer

Arthur Key (not verified)
on Dec 17, 2012

An excellent article. Just one question. I entered http://67.208.46.146. My IE 8 just displayed "piscesweb13".I'm in Bangkok, Thailand.Is there a simple explanation for this?

Post new comment
Sign In or register to use your Broadcast Engineering ID
(optional)

Ads by Google

Watch Broadcast Engineering at NAB

Read the NAB blog for the latest show news

Why Go Digital

Newsletter Block - Editable

Subscribe to our newsletters and get regular updates on the technology that most interests you.

Download Smart Playout Center