Communicating on a Network – Page 4

TCP/IP Overview

The TCP/IP Model is the implemented network protocol suite of the internet, the OSI Model is now considered a theoretical model because it was never caught on like TCP/IP but it has been a very influential model. Cisco uses both the OSI and the TCP/IP models to talk about how data is separated into pieces which are turned into smaller packages. This process is called encapsulation which happens from Layer 7 down to Layer 1. The encapsulated packets or packages travel across the network or the internet and are rebuilt – decapsulation) at the receiving host end. Decapsulation happens from the bottom up, Layer 1 to Layer 7

As data is built into packets or packages it is done in layers. By separating the networking process into layers developers and engineers are able to isolate the necessary functions for their products and not concern themselves with the entire networking architecture. In this way, a layered approach and the rules and protocols recommended by each layer, promote hardware compatibility, easier software development, and competition. By clearly separating the role of each layer networkers are able to easily troubleshoot network failures. It is common for network technicians to identify a layer 1 issue as an unplugged network cable. Similarly a computer which can ping an ip address but is unable to ping a domain name is operating fine at layer 3 but is having an issue at layer 7. See my video tutorials below for an explanation of network layer characteristics.

Video Tutorials

Transport Layer

Transport Layer Overview

The transport layer of both the OSI and TCP/IP models is very important. At this layer the data being prepared to be sent over the internet is broken into pieces called segments. The PDU or protocol data unit at this layer is called a segment. Their are two main protocols that function at this layer TCP and UDP. TCP or transmission control protocol is a very reliable and connection oriented protocol. TCP is characterized as being reliable because of the fact that it will only send data once a three way handshake has first been established, it uses sequence numbers to track all segments and it also uses system of syns and acks (acknowledgments), and it will not send new data until an acknowledgement has been received for data already sent. If the acknowledgement is not received it will resend data. UDP or user datagram protocol on the other hand is not reliable, it is a best effort delivery system, a connectionless protocol, that does not require an established connection with another computer before sending data. UDP’s advantage is the fact that its header fields or control information is a lot smaller than TCP’s so there is a lot less to process and as a result it is a faster  but less reliable protocol.

TCP 

UDP 

segments– sequence numbers, acknowledgements, many header
fields, lots of overhead
datagrams– no sequence numbering, few header fields, little overhead = fast

 

reliability -due to sequence numbering, and resending of data if no acknowledgement is received unreliable – sends all data regardless of whether or not it was received
connection oriented – Three way handshake receiving computer prior to sending data connectionless –  no handshake to establish connection
source and destination port numbers in the header source and destination port numbers in the header
flow control – dynamically change the windows size to not overwhelm the receiver with data no flow control

Here is a short list of some of the most useful port numbers. You should memorize these ports.

 Port Number

Protocol

80

HTTP

23 

Telnet 

20,21 

FTP 

22 

SSH 

25 

SMTP 

53 

DNS 

110 

POP

Well Known Ports

0 – 1023

Registered Ports

1024 – 49151

Dynamic Ports

49152 – 65535

Video Tutorials – Packet Tracer for Beginners

Packet Tracer for Beginners – Part 1: How to connect a client and a server to a switch, test connectivity with Ping and Run server services like HTTP and FTP