11/27/11 Neok Poocol Leel

1/5 .compechdoc.og/independen/neoking/gide/neandad.hml
Previous Page Next Page
Home
Independent
Networking
1. Introduction
2. Network
Topology
3. Hardware
Connections
4. TCP/IP Ports
and Addresses
5. Network
Protocol Levels
6. Data Link Layer
and IEEE
7. Network
Protocol
Categories
8. Repeaters,
Bridges,
Routers
9. ARP and RARP
Address
Translation
10. Basic
Addressing
11. IP (Network)
12. TCP
(Transport)
13. UDP
(Transport)
14. ICMP
15. Hardware
Cabling
16. Wireless media
17. Outside
Connections
18. Ethernet
19. Token Ring
20. ARCnet
21. AppleTalk
22. FDDI
23. IPX/SPX
24. NetBEUI
Netork Protocol Leels
You should be aware of the fact, that when talking about networking you will hear
the word "protocol" all the time. This is because protocols are sets of standards that
define all operations within a network. They define how various operations are to be
performed. They may even define how devices outside the network can interact with
the network. Protocols define everything from basic networking data structures, to
higher level application programs. They define various services and utility programs.
Protocols operate at many layers of the network models described below. There
are protocols considered to be transport protocols such as TCP and UDP. Other
protocols work at the network layer of the OSI network model shown below, and
some protocols work at several of the network layers.
RFCs
Protocols are outlined in Request for Comments (RFCs). At the end of this
document is a list of protocols and associated RFC numbers.Protocols. Although
RFCs define protocols not all RFCs define protocols but may define other
requirements for the internet such as RFC 1543 which provides information about
the preparation of RFCs. The following RFCs are very central to the TCP/IP
protocol.
RFC 1122 - Defines host requirements of the TCP/IP suite of protocols
covering the link, network (IP), and transport (TCP, UDP) layers.
RFC 1123 - The companion RFC to 1122 covering requirements for internet
hosts at the application layer
RFC 1812 - Defines requirements for internet gateways which are IPv4
routers
Netork Models
There are several network models which you may hear about but the one you will
hear about most is the ISO network model described below. You should realize,
however that there are others such as:
The internet layered protocol
The TCP/IP 4 layered protocol
The Microsoft networking protocol
If you don't like any of these models, feel free to invent your own along with your own networking scheme
of course, and add it to the list above. You can call it "The MyName Protocol". Ever wonder why
networking can be so complex and confusing? Welcome to the world of free enterprise!
The OSI Netork Model Standard
Cisco Sitches For Sale Find Ne & Refb Cico Siche Fee Delie & Tech Sppo! .MemoDeal e.com/Si che
Complete CCNP Training Inan acce o 900+ ho of Cico aining ideo. Onl $159 .INE.com/CCNP
CCNA Training Fo BE/Bech Fehe B Pena CCIE ! neo.i n/CCNA
11/27/11 Neok Poocol Leel
2/5 .compechdoc.og/independen/neoking/gide/neandad.hml
25. AeTa
26. SNA
27. Ohe
28. Sie Rig
29. Me Ce
Rig
30. IP
Maeadig
31. Fiea
32. Dai Nae
Seice (DNS)
33. Via Piae
Neig
34. DHCP
35. BOOTP
36. RPC ad NFS
37. Badcaig
ad
Micaig
38. IGMP
39. Daic
Rig
Pc
40. Sie Mai
Tafe
Pc
(SMTP)
41. Sie Ne
Maagee
Pc
42. Ne
Seice
43. Iaig
Die
44. Ne
Oeaig
Se
45. Aicai
46. Wide Aea
Ne
47. Bacig he
e
48. Fa Teace
49. Tbehig
50. C ed
Ne P
51. Neig
Te ad
Defiii
52. Neig
RFC ad
Pc
The OSI Netork Model Standard
The Ieaia Sadad Ogaiai (ISO) ha defied a adad caed he Oe Se
Iececi (OSI) efeece de. Thi i a ee ae achiece ied be. Each ae i
cideed be eibe f a diffee a f he cicai. Thi cce a deeed
accdae chage i echg. The ae ae aaged hee f he e ee aig ih he
hica (hadae) he highe ee.
1. Phica Lae - The aca hadae.
2. Daa Li Lae - Daa afe ehd (802 ehee). P daa i fae ad ee e fee
aii. A c he iig f he e aii. Add fae e, adde, ad
e c ifai. IEEE diided hi ae i he fig bae.
1. Lgica Li c (LLC) - Maiai he Li beee ce b eabihig
Seice Acce Pi (SAP) hich ae a eie f ieface i. IEEE 802.2.
2. Media Acce C (MAC) - Ued cdiae he edig f daa beee ce.
The 802.3, 4, 5, ad 12 adad a hi ae. If hea ee aig ab he
MAC adde f a e cad, he ae efeig he hadae adde f he cad.
3. Ne Lae - IP e c. Re eage ig he be ah aaiabe.
4. Ta Lae - TCP, UDP. Ee e eeced ad e fee aii.
5. Sei Lae - The e' ieface he e. Deeie he he ei i beg
eed, h g i i ed, ad he i i ced. C he aii f daa dig he
ei. S eci ad ae eabig ce cae each he.
6. Peeai Lae - ASCII EBCDEC daa a. Mae he e f daa aae he
ae ad i. Ued aae dae ce ecific fa ch a be deig. I a
icde cei. I eae he daa, eihe f he e he aicai deedig
he dieci i i gig.
7. Aicai Lae - Pide eice fae aicai eed. Pide he abii f e
aicai ieac ih he e.
Ma c ac ea he bde f he ee ae de b eaig a ie ae f he
de. Fie Ta Pc (FTP) ad ee bh a he aicai, eeai, ad he
ei ae.
The Internet, TCP/IP, DOD Model
Thi de i eie caed he DOD de ice i a deiged f he deae f defee I i
a caed he TCP/IP f ae c, he iee c. I ha he fig ae:
1. Li - Deice die ad ieface cad hich a he daa i ad hica ae f he OSI
de.
2. Ne - Ced he e ae f he OSI de ad icde he IP, ICMP, ad
IGMP c.
3. Ta - Ced he a ae ad icde he TCP ad UDP c.
4. Aicai - Ced he OSI Sei, Peeai ad Aicai ae ad icde
FTP, Tee, ig, Rgi, h, TFTP, SMTP, SNMP, DNS, ga, ec.
Peae e he f ae TCP/IP c. Each ae ha a e f daa ha i geeae.
1. The Li ae ced he hadae, icdig he deice die ad ieface cad. The i
ae ha daa ace aciaed ih i deedig he e f e beig ed ch a
ARCe, Te ig ehee. I cae, e i be aig ab ehee.
2. The e ae aage he ee f ace ad he e ad icde IP, ICMP,
ad IGMP. I i eibe f aig e ha acage each hei deiai, ad if he d',
eig e.
11/27/11 Neok Poocol Leel
3/5 .compechdoc.og/independen/neoking/gide/neandad.hml
53. Fhe Readig
54. Cedi
Neig
Ideede
He
eig e.
3. The a ae i he echai ed f ce echage daa ih egad
fae. The e f c ha ae he a echai ae TCP ad UDP. Thee
ae a he e f c f e he ha TCP/IP b e i a ab TCP ad
UDP i hi dce.
4. The aicai ae efe eig c ha ae ed ai eice ch
a FTP, Tee, BOOTP, ec. Ne hee aid cfi, ha he aicai ae i geea
efeig c ch a FTP, ee, ig, ad he ga deiged f ecific e
hich ae geed b a ecific e f c defied ih RFC' (ee f ce).
Hee a ga ha a ie ca defie i daa ce ed beee
cie ad ee ga g a he ga bh he cie ad ee achie
dead c. F eae he ga e a ce ahe achie, i i
ig TCP c, b he daa ed deed h ce i.
Data Encapsulation, a Critical concept to be understood
Whe aig ih c ha a he e ae f he e de, each e f daa i
aed iide he e e ae c, iia aig ee iide a eee. The
application ceae he daa, he he transport ae a ha daa iide i fa, he he netork
ae a he daa, ad fia he link (ehee) ae ecaae he daa ad ai i.
11/27/11 Neok Poocol Leel
4/5 .compechdoc.og/independen/neoking/gide/neandad.hml
To continue, you should understand the deIinition oI a client and server with regards to networking. II you
are a server, you will provide services to a client, in much the same way as a private investigator would
provide services to their clients. A client will contact the server, and ask Ior service, which the server will
then provide. The service may be as simple as sending a single block oI data back to the client. Since there
are many clients, a server must be constantly ready to receive client requests, even though it may already
be working with other clients. Usually the client program will operate on one computer, while the server
program will operate on another computer, although programs can be written to be both a client and a
server.
Lets say you write a client chat program and a server chat program to be used by two people to send
messages between their machines. You run the server program on machine B, and the client program on
machine A. Tom is on machine A and George is on machine B. George's machine is always ready to be
contacted, but cannot initiate a contact. ThereIore iI George wants to talk to Tom, he cannot, until Tom
contacts him. Tom, oI course can initiate contact at any time. Now you decide to solve the problem and
merge the Iunctionality oI the two programs into one, so both parties may contact the other. This program
is now a client/server program which operates both as a client and a server. You write your code so when
one side initiates contact, he will get a dialog box, and a dialog box will pop up on the other side. At the
time contact is initiated, a socket is opened between the two machines and a virtual connection is
established. The program will let the user (Tom) type text into the dialog window, and hit send. When the
user hits send, roughly the Iollowing will happen.
1. Your program will pass Tom's typed text in a buIIer, to the socket. This happens on machine A.
2. The underlying soItware (Code in a library called by a Iunction your program used to send the data)
supporting the socket puts the data inside a TCP data packet. This means that a TCP header will be
added to the data. This header contains a source and destination port number along with some other
inIormation and a checksum. Deamon programs (Daemon deIinition at the bottom oI this page) may
also work at this level to sort packages based on port number (hence the TCP wrapper program in
UNIX and Linux).
3. The TCP packet will be placed inside an IP data packet with a source and destination IP address
along with some other data Ior network management. This may be done by a combination oI your
library Iunction, the operating system and supporting programs.
4. The IP data packet is placed inside an ethernet data packet. This data packet includes the
destination and source address oI the network interIace cards (NIC) on the two computers. The
address here is the hardware address oI the respective cards and is called the MAC address.
5. The ethernet packet is transmitted over the network line.
6. Assuming there is a direct connection between the two computers, the network interIace card on
machine B, will recognize its MAC address and grab the data.
7. The IP data packet will be extracted Irom the ethernet data packet. A combination oI deamons and
the operating system will perIorm this operation.
8. The TCP data packet will be extracted Irom the IP data packet. A combination oI deamons, the
operating system, and libraries called by your program will perIorm this Iunction.
9. The data will be extracted Irom the TCP packet. Your program will then display the retrieved data
(text) in the text display window Ior George to read.
Be aware that Ior the sake oI simplicity, we are excluding details such as error management, routing, and
identiIying the hardware address oI the NIC on the computer intended to receive the data. Also we are not
mentioning the possible rejection oI service based on a packet's port number or sender's IP address.
A deamon program is a program that runs in the background on a computer operating system. It is used to
perIorm various tasks including server Iunctions. It is usually started when the operating system is booted,
but a user or administrator may be able to start or stop a daemon at any time.
11/27/11 Neok Poocol Leel
5/5 .compechdoc.og/independen/neoking/gide/neandad.hml
but a user or administrator ma be able to start or stop a daemon at an time.