Introduction to IP - CompTIA A+ 220-1201 - 2.1

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/10

encourage image

There's no tags or description

Looks like no tags are added yet.

11 Terms

1
New cards

A Series of Moving Vans

•Efficiently move large amounts of data

- use a shipping truck

•The network topology is the road

- ethernet, DSL, coax cable

•The truck is the Internet Protocol (IP)

- we've designed the roads for this truck

•The boxes hold your data

- boxes of TCP and UDP

•Inside the boxes are more things

- application information

<p>•Efficiently move large amounts of data</p><p>- use a shipping truck</p><p>•The network topology is the road</p><p>- ethernet, DSL, coax cable</p><p>•The truck is the Internet Protocol (IP)</p><p>- we've designed the roads for this truck</p><p>•The boxes hold your data</p><p>- boxes of TCP and UDP</p><p>•Inside the boxes are more things</p><p>- application information</p>
2
New cards

IP - Internet Protocol

*Routing protocol that is in charge of forwarding packets on the Internet from the Client to the Server

- Ethernet Header -> Ethernet Payload -> Ethernet Trailer

- Ethernet Header -> IP -> IP Payload -> Ethernet Trailer

- Ethernet Header -> IP -> TCP -> TCP Payload -> Ethernet Trailer

- Ethernet Header -> IP -> TCP -> HTTP data -> Ethernet Trailer

<p>*Routing protocol that is in charge of forwarding packets on the Internet from the Client to the Server</p><p>- Ethernet Header -> Ethernet Payload -> Ethernet Trailer</p><p>- Ethernet Header -> IP -> IP Payload -> Ethernet Trailer</p><p>- Ethernet Header -> IP -> TCP -> TCP Payload -> Ethernet Trailer</p><p>- Ethernet Header -> IP -> TCP -> HTTP data -> Ethernet Trailer</p>
3
New cards

TCP and UDP

*Transported inside of IP

- encapsulated by the IP protocol

*Two ways to move data from place to place

- different features for different applications

*OSI Layer 4

- the transport layer

*Multiplexing

- use many different applications at the same time

- TCP and UDP

<p>*Transported inside of IP</p><p>- encapsulated by the IP protocol</p><p>*Two ways to move data from place to place</p><p>- different features for different applications</p><p>*OSI Layer 4</p><p>- the transport layer</p><p>*Multiplexing</p><p>- use many different applications at the same time</p><p>- TCP and UDP</p>
4
New cards

TCP (Transmission Control Protocol)

•Connection-oriented

- a formal connection setup and close

•"Reliable" delivery

- recovery from errors

- can manage out-of-order messages or retransmissions

•Flow control

- the receiver can manage how much data is sent

<p>•Connection-oriented</p><p>- a formal connection setup and close</p><p>•"Reliable" delivery</p><p>- recovery from errors</p><p>- can manage out-of-order messages or retransmissions</p><p>•Flow control</p><p>- the receiver can manage how much data is sent</p>
5
New cards

UDP (User Datagram Protocol)

•Connectionless

- no formal open or close to the connection

•"Unreliable" delivery

- no error recovery

- no reordering of data or retransmissions

•No flow control

- sender determines the amount of data transmitted

<p>•Connectionless</p><p>- no formal open or close to the connection</p><p>•"Unreliable" delivery</p><p>- no error recovery</p><p>- no reordering of data or retransmissions</p><p>•No flow control</p><p>- sender determines the amount of data transmitted</p>
6
New cards

Why would you ever use UDP?

*Real-time communication

- there's no way to stop and resend the data

- time doesn't stop for your network

*Connectionless protocols

- DHCP (Dynamic Host Configuration Protocol)

- TFTP (Trivial File Transfer Protocol)

*The data might not get through

- the application keeps track and decides what to do

- it might not do anything

<p>*Real-time communication</p><p>- there's no way to stop and resend the data</p><p>- time doesn't stop for your network</p><p>*Connectionless protocols</p><p>- DHCP (Dynamic Host Configuration Protocol)</p><p>- TFTP (Trivial File Transfer Protocol)</p><p>*The data might not get through</p><p>- the application keeps track and decides what to do</p><p>- it might not do anything</p>
7
New cards

Communication using TCP

•Connection-oriented protocols prefer a "return receipt"

- HTTPS (Hypertext Transfer Protocol Secure)

- SSH (Secure Shell)

•The application doesn't worry about out of order frames or missing data

- TCP handles all of the communication overhead

- the application has one job

<p>•Connection-oriented protocols prefer a "return receipt"</p><p>- HTTPS (Hypertext Transfer Protocol Secure)</p><p>- SSH (Secure Shell)</p><p>•The application doesn't worry about out of order frames or missing data</p><p>- TCP handles all of the communication overhead</p><p>- the application has one job</p>
8
New cards

Speedy Delivery

•The IP delivery truck delivers from

one (IP) address to another (IP) address

- every house has an address,

every computer has an IP address

•Boxes arrive at the house / IP address

- where do the boxes go?

- each box has a room name

•Port is written on the outside of the box

- drop the box into the right room

<p>•The IP delivery truck delivers from</p><p>one (IP) address to another (IP) address</p><p>- every house has an address,</p><p>every computer has an IP address</p><p>•Boxes arrive at the house / IP address</p><p>- where do the boxes go?</p><p>- each box has a room name</p><p>•Port is written on the outside of the box</p><p>- drop the box into the right room</p>
9
New cards

Lots of Ports

•IPv4 sockets

- server IP address, protocol,

server application port number

- client IP address, protocol, client port number

•Non-ephemeral ports - permanent port numbers

- ports 0 through 1,023

- usually on a server or service

•Ephemeral ports - temporary port numbers

- ports 1,024 through 65,535

- determined in real-time by the client

<p>•IPv4 sockets</p><p>- server IP address, protocol,</p><p>server application port number</p><p>- client IP address, protocol, client port number</p><p>•Non-ephemeral ports - permanent port numbers</p><p>- ports 0 through 1,023</p><p>- usually on a server or service</p><p>•Ephemeral ports - temporary port numbers</p><p>- ports 1,024 through 65,535</p><p>- determined in real-time by the client</p>
10
New cards

Port Numbers

•TCP and UDP ports can be any number

between 0 and 65,535

•Most servers (services) use non-ephemeral

(not-temporary) port numbers

- This isn't always the case -> it's just a number.

• Port numbers are for communication, not security

• Service port numbers need to be "well known"

• TCP port numbers aren't the same as UDP port numbers

<p>•TCP and UDP ports can be any number</p><p>between 0 and 65,535</p><p>•Most servers (services) use non-ephemeral</p><p>(not-temporary) port numbers</p><p>- This isn't always the case -> it's just a number.</p><p>• Port numbers are for communication, not security</p><p>• Service port numbers need to be "well known"</p><p>• TCP port numbers aren't the same as UDP port numbers</p>
11
New cards

Ports on the Network

*Web server - tcp/80

*VoIP server - udp/5004

*Email server - tcp/143

<p>*Web server - tcp/80</p><p>*VoIP server - udp/5004</p><p>*Email server - tcp/143</p>