š Network Protocols
ARP, FTP, SMTP, HTTP, HTTPS, DNS and DHCP
Series: Networking Fundamentals for Cloud & DevOps
We have already seen how hosts, switches, routers, MAC addresses and IP addresses work together. Now we move one level higher and look at the protocols that define how different types of communication happen.
1. Protocol
A protocol is a set of rules/messages that devices follow to communicate.
Think of a protocol as a common language with defined rules.
For example:
- If two devices need to resolve an IP address to a MAC address ā ARP
- If a client needs to transfer a file ā FTP
- If a client needs to send an email ā SMTP
- If a browser needs web communication ā HTTP/HTTPS
- If a host needs to convert a domain name into an IP address ā DNS
- If a host needs its network configuration automatically ā DHCP
A quick overview:
| Protocol | Full Form | Main Job |
|---|---|---|
| ARP | Address Resolution Protocol | IP ā MAC |
| FTP | File Transfer Protocol | Transfer files |
| SMTP | Simple Mail Transfer Protocol | Send email |
| HTTP | HyperText Transfer Protocol | Web communication |
| HTTPS | HTTP Secure | Secure HTTP using TLS |
| DNS | Domain Name System | Domain name ā IP |
| DHCP | Dynamic Host Configuration Protocol | Automatically gives network configuration |
The important thing is not just memorizing the names.
Each protocol solves a different communication problem.
2. ARP
ARP = Address Resolution Protocol
ARP solves this problem:
"I know the IP address, but what is the MAC address?"
Suppose a host knows:
9.1.1.22
but needs the corresponding MAC address.
It broadcasts an ARP Request:
Host 9.1.1.11:
"Who has 9.1.1.22?"
The host with that IP responds:
Host 9.1.1.22:
"My MAC is b3b3."
So the mapping becomes:
9.1.1.22 ā b3b3
Therefore:
ARP = IP ā MAC mapping
This connects directly to what we learned earlier:
IP address
ā
ARP
ā
MAC address
ā
Ethernet frame
ARP is mainly concerned with finding the Layer 2 address needed for communication on the local network.
3. FTP
FTP = File Transfer Protocol
FTP is used for file transfer.
The basic idea is:
Client āāāāāāāāāāāāāā FTP Server
file.pdf
For example:
Client āā RETR file.pdf āāā FTP Server
Client āāāāā file.pdf āāāāā FTP Server
RETR essentially means:
Retrieve/download this file.
So the simple memory rule is:
FTP ā File transfer
4. SMTP
SMTP = Simple Mail Transfer Protocol
SMTP is used for sending email.
Conceptually:
Client āā HELLO āāāāāāāā SMTP Server
Client āā email āāāāāāāā SMTP Server
The protocol defines how the email-sending communication takes place between the client and mail server, and between mail servers.
So:
SMTP = sending mail
5. HTTP
HTTP = HyperText Transfer Protocol
HTTP is used for web communication.
A browser/client can request a resource from a web server:
Client āā GET /index.html āāā Web Server
Client āāāāāāā 200 OK āāāāāāā Web Server
The client asks for a resource, and the web server responds.
So:
HTTP ā Web communication
This is the basic protocol underneath the request/response model used by the web.
6. HTTPS
HTTPS = HTTP + TLS security
HTTPS is HTTP communication protected using TLS.
The important idea is:
HTTP
+
TLS security
ā
HTTPS
TLS provides security mechanisms such as encryption and authentication for the communication.
Conceptually:
Client āāāāā encrypted HTTPS connection āāāāāā Web Server
So remember:
HTTP = Web communication
HTTPS = Secure web communication
HTTPS is what allows a browser to communicate with a web server while protecting the connection against unauthorized observation or modification.
7. DNS
DNS = Domain Name System
DNS solves a different problem from ARP.
ARP asks:
"I know the IP. What is the MAC?"
DNS asks:
"I know the website/domain name. What is its IP?"
Suppose you want to access:
site.com
Your computer needs the server's IP address.
It asks a DNS server:
What is the IP address of site.com?
The DNS server responds:
site.com ā 160.8.23.154
So:
DNS = Domain name ā IP
The key distinction is:
ARP:
IP ā MAC
DNS:
Name ā IP
8. Four Things a Host Needs for Internet Connectivity
A host generally needs four important pieces of network configuration:
1. IP Address
2. Subnet Mask
3. Default Gateway
4. DNS Server
For example:
IP:
9.1.1.11
Mask:
255.255.255.0
Gateway:
9.1.1.1
DNS:
8.8.8.8
Each one has a different job.
IP Address
Identifies the host on the network.
IP ā Which host am I?
Subnet Mask
Determines which addresses belong to the local network.
Subnet Mask ā Which network am I in?
Default Gateway
Provides the router used to reach other networks.
Default Gateway ā How do I reach other networks?
DNS
Converts domain names into IP addresses.
DNS ā What IP belongs to this domain name?
So:
IP ā identifies the host
Subnet mask ā determines the local network
Default gateway ā router used to reach other networks
DNS ā converts names into IP addresses
These four pieces work together whenever a host needs to communicate beyond its immediate network.
9. DHCP
DHCP = Dynamic Host Configuration Protocol
DHCP automatically provides network configuration to a client.
Without DHCP, a host would need to be manually configured with values such as:
IP = 9.1.1.11
Subnet = 255.255.255.0
Gateway = 9.1.1.1
DNS = 8.8.8.8
With DHCP, the client can obtain these settings automatically from a DHCP server.
The basic process is:
Client ā DHCP Discover
Server ā DHCP Offer
Client ā DHCP Request
Server ā DHCP ACK
The four steps are commonly remembered as:
D ā O ā R ā A
Discover
Offer
Request
ACK
The result is that the host receives its network configuration automatically.
DHCP automatically gives a host its network configuration.
Quick Revision
ARP
ā IP ā MAC
DNS
ā Name ā IP
DHCP
ā IP + Mask + Gateway + DNS
HTTP
ā Web communication
HTTPS
ā Secure web communication
FTP
ā File transfer
SMTP
ā Send email
The Big Picture
These protocols solve different problems, but they work together when a host accesses something on the Internet.
A simplified sequence could look like:
1. DHCP
ā
Get IP + subnet mask + gateway + DNS
2. DNS
ā
Convert domain name ā destination IP
3. Routing
ā
Decide whether destination is local or remote
4. ARP
ā
Resolve the next-hop IP ā MAC
5. HTTP / HTTPS
ā
Communicate with the web server
So don't think of these protocols as isolated terms.
They are different pieces of the same networking process:
DHCP
ā
Network configuration
DNS
ā
Find destination IP
Routing
ā
Find next hop
ARP
ā
Find next-hop MAC
HTTP / HTTPS
ā
Exchange web data
And other protocols solve other application-level problems:
FTP ā File transfer
SMTP ā Email
The important mental model is:
Protocols exist because different parts of communication need different rules.
Part 6 of 6 ā Networking Fundamentals for Cloud & DevOps
This completes the current networking fundamentals sequence and provides the protocol foundation needed for deeper AWS networking concepts.
Top comments (0)