Networking Tips


[an error occurred while processing this directive]

No Title

[an error occurred while processing this directive]

Reference: Cisco: Internetworking Basics



In TCP/IP, there are two types of entities that exist on a network - hosts and routers. All networks must have hosts, while not all networks require routers. Whether you use routers should depend on the physical topology of the network. This section of "Networking Basics" introduces the concepts of network topology and routing, important when you decide to add another network to your existing network environment.

Network Topology

Network topology describes how networks fit together. Routers are the entities that connect networks to each other. From a TCP/IP perspective, a router is any machine that has two or more network interfaces. However, the machine cannot function as a router until properly configured.

Two or more networks can be connected together by routers to form larger internetworks. The routers must be configured to pass packets between two adjacent networks. They also should be able to pass packets to networks that lie beyond the adjacent networks.

The following figure shows the basic parts of a network topology. The first illustration shows a simple configuration of two networks connected by a single router. The second shows a configuration of three networks, interconnected by two routers. In the first case, network 1 and network 2 are joined into a larger internetwork by router R. In the second case, router R1 connectes networks 1 and 2, and router R2 connects networks 2 and 3, thus forming a network made up of networks 1, 2, and 3.

Two Networks Connected by a Router           
+-------------+     |     |     +-------------+
|  Network 1  | --- |  R  | --- |  Network 2  |
+-------------+     |     |     +-------------+
Three Networks Connected by Two Routers           
                    +----+                         +----+
+-------------+     |    |     +-------------+     |    |     +-------------+
|  Network 1  | --- | R1 | --- |  Network 2  | --- | R2 | --- |  Network 3  |
+-------------+     |    |     +-------------+     |    |     +-------------+
                    +----+                         +----+

Routers join networks into internetworks and route packets between them based on the addresses of the destination network. As internetworks grow larger and more complex, each router must make more and more decisions regarding where packets are to be sent.

A set up in complexity is shown in the next figure. Networks 1 and 3 are directly connected by a router R3. The reason for such redundancy is reliability. If network 2 goes down, router R3 still provides a route between networks 1 and 3. Any number of networks can be interconnected and communicate as long as they all adhere to the same network protocols.

Providing an Additional Path Between Networks           

                                   |    |
        -------------------------- | R3 | ---------------------------
       /                           |    |                            \
       |                           +----+                            |
       |                                                             |
       |            +----+                         +----+            |
+-------------+     |    |     +-------------+     |    |     +-------------+
|  Network 1  | --- | R1 | --- |  Network 2  | --- | R2 | --- |  Network 3  |
+-------------+     |    |     +-------------+     |    |     +-------------+
                    +----+                         +----+

How Routers Transfer Packets

Routing decisions on a network are based on the network portion of the IP address of the recipient that is contained in the packet header. If this address includes the network number of the local network, the packet goes directly to the host with that IP address. If the network number is not the local network, the packet goes to the router on the local network.

Routers maintain routing information in routing tables. These tables contain the IP address fo the hosts and routers on the networks to which the router is connected. The tables also contain pointers to these networks. When a router gets a packet, it consults its routing table to see if it lists the destination address in the header. If the table does not contain the destination address, the router forwards the packet to another router listed in its routing table.

Three Interconnected Networks           

     Network 192.9.200           Network 192.9.201         Network 192.9.202
  ________________________        ________________      _______________________
 /                        \      /                \    /                       \
|   +--------------+    +--------+              +--------+    +--------------+ |
|   | Host A       |    | Router |              | Router |    | Host B       | |
|   | |    |   R1   |              |   R2   |    | | |
|   +--------------+    +--------+              +--------+    +--------------+ |
 \________________________/      \_______________/     \______________________/

Router R1 connects networks 192.9.200 and 192.9.201. Router R2 connects networks 192.9.201 and 192.9.202. If host A on network 192.9.200 sends a message to host B on network 192.9.202, this is what happens.

  1. Host A sends a packet out over network 192.9.200. The packet header contains the IP address of the recipient host B,
  2. None of the machines on network 192.9.200 has the IP address Therefore, router R1 accepts the packet.
  3. Router R1 examines its routing tables. No machine on network 192.9.201 has the address However, the routing tables do list router R2.
  4. R1 then selects R2 as the “next hop” router and sends the packet to R2.
  5. Because R2 connects network 192.9.201 to 192.9.202, it has routing information for host B. Router R2 then forwards the packet to network 192.9.202, where it is accepted by host B.

About the Author

Jeffrey Hunter is an Oracle Certified Professional, Java Development Certified Professional, Author, and an Oracle ACE. Jeff currently works as a Senior Database Administrator for The DBA Zone, Inc. located in Pittsburgh, Pennsylvania. His work includes advanced performance tuning, Java and PL/SQL programming, developing high availability solutions, capacity planning, database security, and physical / logical database design in a UNIX / Linux server environment. Jeff's other interests include mathematical encryption theory, tutoring advanced mathematics, programming language processors (compilers and interpreters) in Java and C, LDAP, writing web-based database administration tools, and of course Linux. He has been a Sr. Database Administrator and Software Engineer for over 20 years and maintains his own website site at: Jeff graduated from Stanislaus State University in Turlock, California, with a Bachelor's degree in Computer Science and Mathematics.

Copyright (c) 1998-2017 Jeffrey M. Hunter. All rights reserved.

All articles, scripts and material located at the Internet address of is the copyright of Jeffrey M. Hunter and is protected under copyright laws of the United States. This document may not be hosted on any other site without my express, prior, written permission. Application to host any of the material elsewhere can be made by contacting me at

I have made every effort and taken great care in making sure that the material included on my web site is technically accurate, but I disclaim any and all responsibility for any loss, damage or destruction of data or any other property which may arise from relying on it. I will in no case be liable for any monetary damages arising from such loss, damage or destruction.

Last modified on
Monday, 20-Sep-2010 10:43:02 EDT
Page Count: 3434