Understanding the Data Link and Physical Layers: The Final Step in Mastering OSI Model and Computer Networking


This is the eighth and final part of the computer networking series. Check out the previous parts if you haven't. In this part, we'll see about:
- Data Link Layer
- Physical Layer
Table of Contents
Data Link Layer
The data link layer is responsible for sending the data packets received from the network layer over a physical link.
In the data link layer, the data is sent as frames.
If many devices are connected in a LAN, the devices communicate with each other using their data link layer addresses.
If you don't know what a LAN is, we've already discussed it in a previous part. You can check it here ↓
%[https://dev.to/vignesh_j/computer-networking-full-course-7ap]
Example of Communication in a LAN
Consider A, B, C, and D connected in a LAN, and A wants to send data to D:
- Checking ARP Cache:
- First, A checks its cache memory (known as the ARP cache) for D's data link layer address.
- Broadcast Request:
- If the address is unavailable, A sends a message to all devices in the network asking for D's data link layer address.
- The message is a frame that includes:
- The data link layer address of the sender (A).
- The IP address of the destination (D).
- A request for the data link layer address of the destination.
Address Resolution Protocol (ARP)
- ARP Cache: Stores mappings of IP addresses to data link layer addresses.
- MAC Address:
- A unique 12-digit alphanumeric string that serves as the data link layer address.
- Stands for Media Access Control.
The data link layer works closely with the physical layer to ensure communication.
Physical Layer
The Physical Layer is the bottom-most layer in the OSI Model. It represents the physical and electrical aspects of the system.
Key Features of the Physical Layer
- Hardware Components: Includes power plugs, connectors, receivers, and cable types.
- Transmission of Data Bits: Responsible for sending unstructured raw data streams from one device (e.g., a computer) to another.
- Encoding: Defines how 0s and 1s are encoded into signals for transmission over the physical medium.
The Physical Layer is responsible for communication over a physical medium like cables and wireless systems.
Conclusion
This marks the end of the OSI model and also the end of this series. I hope you’ve gained insights into some basic computer networking concepts necessary to understand how the internet works.
Remember, computer networking is a vast field with much more to explore. This series provides a foundational overview, but you can dive deeper into specialized topics by exploring additional resources.
Make sure to react and leave your feedback in the comments! It would be really helpful to understand what is good and what I need to improve.
If you like my content, you can follow me here:
Thank you for following along this journey!
Subscribe to my newsletter
Read articles from Vignesh J directly inside your inbox. Subscribe to the newsletter, and don't miss out.
Written by

Vignesh J
Vignesh J
I am Vignesh. I build full-stack web applications using the MERN stack and Java full-stack. I am a technical writer who writes technical content on dev.to and Medium. I have around 5k followers on dev.to. I contribute to open-source projects and have also maintained an open-source project of my own. I have participated in a few open-source programs, both as a contributor and a maintainer: -> Secured 3rd place as a contributor among 100+ participants in Code Sapiens 2024. -> Secured 7th place as a Contributor team among 1650+ teams in DevFest AI 2024. -> Secured 14th place as a project admin among 415+ projects in GirlScript Summer of Code 2024 - Extd. -> Completed the 4 PR mark as a contributor in Hacktoberfest 2024. -> Participated as a maintainer in Hacktoberfest 2024. I am passionate about building impactful software solutions and fostering collaboration in the open-source community. I enjoy working in collaborative environments and mentoring contributors in open-source communities. Feel free to connect with me to discuss web development, open-source contributions, or technical writing. I'm always happy to collaborate and share ideas!