0% found this document useful (0 votes)
6 views35 pages

KomJar Pertemuan 02

Chapter 2 of CompTIA Network+ focuses on the OSI model, detailing its purpose, layers, and characteristics. It compares the OSI model with the TCP/IP stack and discusses common TCP/UDP port numbers for applications. The chapter emphasizes the importance of reference models in simplifying network communication and facilitating interoperability among different network components.

Uploaded by

jinanramadhan.a
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views35 pages

KomJar Pertemuan 02

Chapter 2 of CompTIA Network+ focuses on the OSI model, detailing its purpose, layers, and characteristics. It compares the OSI model with the TCP/IP stack and discusses common TCP/UDP port numbers for applications. The chapter emphasizes the importance of reference models in simplifying network communication and facilitating interoperability among different network components.

Uploaded by

jinanramadhan.a
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 35

CompTIA Network +

Chapter 2
Dissecting the OSI Model
Objectives
▪ What is the purpose of a Network model?
▪ What are the layers of the OSI model?
▪ What are the characteristics of each layer of the
OSI model?
▪ How does the TCP/IP stack compare to the OSI
model?
▪ What are the well-known TCP and/or UDP port
numbers for a given collection of common
applications
The Purpose of Reference Models
• It breaks network communication into smaller, simpler parts that
are easier to develop.
• It facilitates standardization of network components to allow
multiple-vendor development and support.
• It allows different types of network hardware and software to
communicate with each other.
• It prevents changes in one layer from affecting the other layers
so that they can develop more quickly.
• It breaks network communication into smaller parts to make
learning it easier to understand.
The OSI seven-layer model
7 Application

6 Presentation

5 Session

4 Transport

3 Network

2 Data Link

1 Physical

Figure 2-2 OSI Stack


Mnemonics for the OSI Model
Away All
Pizza People
Sausage Seem
Throw To
Not Need
Do Data
Please Processing
Physical Layer
Application

Presentation

Session

Transport

Network • How Bits are represented


on the medium
Data Link • Wring standards for
connectors and jacks
Physical • Physical topology
• Synchronizing bits
• Bandwidth usage
• Multiplexing strategy

Figure 2-4 Layer 1: Physical Layer


Wiring Standards
Layer 1 Devices
• Cables
• Wireless access points
• Hubs
– Because they don’t pay any attention to
addresses, they just deliver signals to every
connected device like a crossover cable
Data Link Layer
Application

Presentation

Session
• Physical Addressing
Transport • Logical topology
MAC
• Method of transmitting
Network on the media
Data Link

Physical • Connection Services


LLC • Synchronizing
transmissions

Figure 2-8 Layer 2: The Data Link Layer


MAC Addresses
• IPCONFIG /ALL
• Physical Address
• Built into the network interface
Layer 2 Devices
• Switches
• Bridges
• Network Interface Cards (NICs)
Network Layer
Application

Presentation

Session
• Logical addressing
Transport • Switching
• Route discovery and
Network selection
• Connection services
Data Link • Bandwidth usage
• Multiplexing strategy
Physical

Figure 2-9 Layer 3: The Network Layer


IP Address
• Logical address
• Changes when the device is moved
Switching
• Packet switching
– Data is broken into packets
– Many packets travel along network
connections like cars on a freeway
• Circuit switching
– A physical line is dedicated to each
connection
– Ex: old copper landline phone systems
• Message switching
– Store-and-forward, like email
Layer 3 Devices
• Routers
• Multilayer Switches
Transport Layer
Application

Presentation

Session
• TCP/UDP
Transport • Windowing
• Buffering
Network

Data Link

Physical

Figure 2-10 Layer 4: The Transport Layer


TCP and UDP
• Transmission Control Protocol (TCP)
– Connection-oriented and reliable
– Handshake makes sure both ends are ready
– Segments are acknowledged and resent if
necessary
• User Datagram Protocol (UDP)
– Connectionless and unreliable
– No handshake
– Best-effort delivery, no acknowledgements
ICMP
(Internet Control Message
Protocol)
• At layer 4
• Used by ping and traceroute, and to
indicate errors such as dropped packets
Session Layer
Application

Presentation • Setting up a session


• Maintaining a session
Session • Tearing down a session
Transport

Network

Data Link

Physical

Figure 2-12 Layer 5: The Session Layer


Example of a Session
• User logs in with a username & password
• All data now has a special significance
until that user logs off, or the session times
out, or is terminated some other way
• Layer 6 Protocol
– H.323 (voice or video)
– NetBIOS (file sharing)
Presentation Layer
Application • Data formatting
• Encryption
Presentation

Session

Transport

Network

Data Link

Physical

Figure 2-13 Layer 6: The Presentation Layer


Application Layer
• Application services
Application • Service advertisement
Presentation

Session

Transport

Network

Data Link

Physical
Application Layer
• Closest to the user
• Hands data to an application in the format
it expects, with no addresses or other
transmission artifacts
• Examples: a downloaded file, an email
message
The TCP/IP Stack

Application

Transport

Internet

Network Interface
The TCP/IP and OSI Models Compared
OSI Stack TCP/IP Stack
Application

Presentation Application

Session

Transport Transport

Network Internet

Data Link
Network Interface
Physical

Figure 2-15 TCP/IP Stack


IP Ver4 Header
TTL (Time-to-Live)
• TTL decreases by one each time the
packet is forwarded by a router
• If TTL reaches zero, the packet is
discarded
• This eliminates packets trapped in routing
loops
Demo: Routing Loop
TCP Header

Figure 2-17 TCP Segment Format


TCP Header Fields
• Port numbers
– Indicate which program on the end device
should receive the data
– Examples: Port 25 for email, 80 for HTTP
• Window size
– Number of bytes that can be sent before
waiting for an ACK
TCP Header Fields
• Sequence and Acknowledgement
numbers
– Used to put packets in order to reassemble
files and other large messages
• Flags like SYN and ACK are used for the
TCP handshake and to acknowledge data
received
UDP Header
0 16 31
SOURCE PORT DESTINATION PORT
LENGTH CHECKSUM

• No handshake, acknowledgements,
sequencing, or flow control
Common Ports
Link Ch 2d for flash cards
Port Types
Port numbers are assigned in various ways, based
on three ranges:

▪ System Ports (0-1023), System Ports are assigned by IETF process for
standards-track protocols, as per RFC6335. Also known as well-
known-ports

▪ User Ports (1024-49151) ,User Ports are assigned by IANA using the
"Expert Review" process, as per RFC6335

▪ Dynamic and/or Private Ports (49152-65535), Dynamic Ports are not


assigned, they are dynamically created as your computer need them.
Also known as ephemeral ports.
Communication Between Two Systems

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy