networking


In 1999 I wrote a series of Border Gateway Protocol tutorials including a tutorial on autonomous system numbers. Since then AS numbers have been changed from 16-bit to 32-bit numbers to avoid running out of identifiers for BGP sessions. I have updated theAS numbers tutorial with a table that outlines what each range of autonomous system numbers are used for.

This question was cobbled together from several common e-mails this week.

Hey, Inetdaemon,  Doesn’t bandwidth solve all network problems with [Skype, Facetime, Vonage, NetFlix, Hulu, YouTube, World of Warcraft (WoW)…], and push my frame rates through the roof in [choose any FPS/MMORPG]?

Answer:  Not so!

Engineers use a measurement called “latency” to measure delay between endpoints in communications systems, including the Internet.  High latency is bad, low latency is good.  High latency indicates a problem between endpoints. This could be you and a friend across Skype, Facetime, Vonage or  anything else.  Problems with ‘delay’ are the real causes of ‘slowness’ and communications problems. More bandwidth will only fix issues with congestion and over-subscription, and only if you can add more bandwidth along the entire path from end-to-end.   More bandwidth can’t do anything about the actual delay from the communications systems, routers, switches and the infrastructure supporting it or delay from the server.  Moreover, if the “internet pipe” at the far end serving the person or site you’re trying to reach is full, their router is busy, or their servers are overloaded, there’s no benefit to upgrading your own service to higher bandwidth.  Given the nature of the Internet, everyone else would also have to upgrade thier Internet connection to make your services faster to every site you use frequently.

Continue Reading about Latency and Delay


We covered the OSI Model in CCNA Lesson 5, now we move on to the TCP/IP Model which you will also need to know for the CCNA exam.   Since internetworking is based on the TCP/IP protocol suite, the TCP/IP model is a bit more important than the OSI model on the CCNA exam.

While the ISO folks were meeting in committees to develop the OSI Reference Model, the rest of the world got busy making networks actually work and the TCP/IP suite of protocols is the result.  The TCP/IP model of networking describes how the TCP/IP protocol suite functions and operates. Simpler than the OSI Reference Model, the TCP/IP model describes the most common stack of network protocols in use today.  This network model goes by several names:   the DARPA Model, the Department of Defense (DoD) Model,  and today we just call it the TCP/IP Model.

Basics

  • Four Layers
  • De-facto standard networking
  • Models the TCP/IP protocol suite

There is a full tutorial on the TCP/IP Model here at InetDaemon.com.

There are two basic network models, the OSI Model and the TCP/IP Model.  Both outline the basic functions of how networks work and are each a standard in their own right. Understanding the OSI Reference Model is a requirement for passing any exam on networking whether it is the CCNA, CCNP, Network+ or any Juniper exam.

Memorize the OSI Reference Model. Now. You’ll use it over and over again and none of the information we cover from here on will make any sense if you don’t.  Networks were built one layer at a time over a period of time.  First physical communication was made possible, then logical addresses were used to  allow you to move computers around on a network. Next, the ability to route packets from one network to another was worked out, then ways to guarantee delivery of large volumes of data and finally ways to boot up and to manage the network, provide names humans can remember, and finally to serve up stored data as web pages.

Continue reading