Webspace Sponsored by:
Version 0.0.0 @ 03:55/08.07.2000
Networking Theory 101: Introduction to Networking
(An Evolving Online Research for Peer Review)
by Michael Egan
Purpose: The purpose of this paper is to provide some networking information for people that wish to better understand it.
To facilitate this abstract topic's disassembly into a more tangible form more easily quantified, this review is broken into multiple parts or sections.
- Terms: (Incomplete: being written) This paper includes a few semi-technical words that are partially defined on this link's page. A general user unfamiliar with these words may want to examine this section to prepare themselves with the meaning of most of the technical words used here.
- Networking Models (Rough First Drafts in progress) can be reviewed, and would provide an initial reference for understanding the topics that will come later in this document below this point. (This includes a simple review of the ISO OSI 7 Layer Reference Model for networking and an attempt to push TCP/IP into a 5 Layer Model using some of the thoughts and ideas expressed in the earlier 7 layer model.)
Now that you have been able to encounter the ISO OSI 7 Layer Reference Model for Networking, the rest is likely to get easier.
- OSI Physical Layer (Will be moved out when work starts, but topics include:)
- Unshielded Twisted Pair
- Shielded Twisted Pair
- Fiber Optics
- OSI Data Link Layer(Will be moved out when work starts, but topics include:)
- Brodcast vs. Point-to-point communication with examples. Exampes include one each for Simplex, Half-Duplex, and Full-Duplex types of communcations.
- Ethernet (Broadcast Example)
- 10 Base T
- 10 Base 2
- 10 Base 5
- Fiber Optic
- 100 Base T
- PPP (Point-to-point Example)
- TokenRing here (Token Passing Example)
- LocalTalk here
- 100VG-AnyLAN (Demand Priority Example)
- OSI Network Layer (Will be moved out when work starts, but topics include:)
- From the TCP/IP suite of protocols: a partial list of common packets and/or protocols associated with the TCP/IP suite. (See an rfc which is also a tutorial on tcp/ip: rfc1180.)
- Network Layer: IP Packet: An examination of a routed protocol packet can help to explain what information a firewall system has available to use in allowing for networking policies. In this case a review of a Network Layer protocol packet like IP is a good standard candidate.
- ICMP Packet: A control packet that may also run over IP but is often considered to be part of the Network layer by most people since it may alter routes (as well as other things.) Some function does however make it appear as though it could be a Transport Layer protocol...
- From the IPX/SPX suite of protocols:
- From AppleTalk:
- something here NBP? hmmmm
- OSI Transport Layer (Will be moved out when work starts, but topics include:)
- From the TCP/IP suite of protocols:
- TCP Packet: An examination of a Transport Layer protocol packet can help to explain what information a firewall system has available to use in allowing for networking policies. In this case a review of TCP is a good standard candidate for this.
- UDP Packet: An examination of another Transport Layer protocol packet can help to explain what information a firewall system has available to use in allowing for networking policies. In this case a review of UDP is a good choice for seeing how little information exists in a UDP header for analysis. Also, with less information in the packet, you may think that UDP is less secure than TCP and you would be correct.
- Other Packets: A cursory examination of other Transport Layer protocol packets and Network Layer protocol payloads of IP packets helps to demonstrate the information that is available to a firewalling filter. (These are not examined in great detail.)
- From the IPX/SPX suite of protocols:
- OSI Session Layer (Will be moved out when work starts, but topics include:)
- NetBIOS? p169 MS hmmm odd.
- OSI Presentation Layer (Will be moved out when work starts, but topics include:)
- OSI Application Layer (Will be moved out when work starts, but topics include:)
TCP/IP Application Layer Protocols:
- Application Layer Protocols: This offers some systems even more information on what kinds of data to allow passed a firewall. (Most of the discussion of Application Layer protocols may be discussed in the Applications section.)
- OSI Application Layer, Presentation Layer, Session Layer Transport Layer, and Network Layers have examples here in the following TCP/IP Session examination from a real-world sniffed session:
- IPX/SPX from Novell Netware Application Layer (Much like the TCP/IP Application Layer by the 5 layer system in assigned tasks for layers:
- OSI Application Layer, Presentation Layer, Session Layer: NDS/NCP
- OSI Application Layer, Presentation Layer, Session Layer: SAP
- Apple File-sharing Protocol
- Firewall Theory for TCP/IP Suite protocols (Will be moved out when work continues, but topics include:):
- Integration of above information with theory: This may help to introduce the uninformed user on how the information contained in the above mentioned packets may be used in a firewalling system with policies to act as a firewall.
- Summary: Bringing all of the ideas together into a generalized and conceptual understanding while avoiding detailed examinations is the purpose of this section.
- History of some related communications (Will be moved out when work starts, but topics include:)
- Bibliography / Reference documents and books: (Being expanded as new resources are found) Most of the information contained in here is from memory or documents read. I try to include a list of most of the documents I used here.
- Comments and/or suggestions for this?: Email me at: email@example.com
- Attempts have been made to make the tables appear as they should for LYNX users by forcing a common field width for fields being used by padding them with other printable characters. This is meant to allow for LYNX users to see the tables much like the Netscape and other web browser worlds might show them. However, from personal experience, some versions of LYNX still manage to munge the tables, making them use up several pages. It seems to be a problem with how earlier versions of LYNX dealt with tables, but the problem has not been entirely isolated.
- Some have asked why this collection of on-line documents is so lacking of graphic content. To them I answer: faster downloads. Many of these pages are smaller than some pictures on many commercial web sites. You do not come here to look at my pictures. You come here to read content. Also, LYNX users benefit from this, and by using ALL text, people with ADA issues are able to use speech recognition software on the text to hear the words.
- Copyright (C) 1999, 2000, 2001, 2002 by Michael Egan: All rights reserved.
- A Special License: No part of this document may be used for profit without the consent of the author Michael Egan in writing. Content may be duplicated for retransmission for non-profit purposes as long as the copyright and license remain included in their entirety. The content is provided "as-is" and I take no responsibility on the content's truthfulness or consistency. Errors may exist in these documents, but acting upon these errors is left up to the reader to verify by a third party that will take responsibility for fact verification. When notified of errors or inconsistencies, attempts will be made to rectify the errors.
- In plan English this is meant to do many things: This copyright is meant to exist so that others may not profit from this work as published in paper form, or by duplicating the content to place advertisements over it and generate income. It is also meant to exist to prevent people from publishing this work as their own and receiving profit from this process on research they did not perform. It is not meant to stop a professor from running off copies to use in their classes for their students. It is also not meant to stop the student from printing up copies for their own education. How depressing it would be to find your work published in book form without your permission, or compensation. Another reason for this Copyright is to limit the effect of the mistakes I have made within this document before I was able to complete it. It would be even sadder to notice my mistakes in print and criticized before I could resolve them. Eventually, after I finish this work, I may retain copyright, but eliminate the license.