Most people walk into a networking interview after memorizing definitions, but that’s usually not enough.
Interviewers often move beyond questions like, “What is DNS?” and ask practical ones such as, “A user says the website is down, but you can ping the server’s IP address.
What would you check next?” The first tests what you remember, while the second shows whether you know how to troubleshoot a real problem.
I’ve put together 20 networking interview questions that are commonly asked for Linux System Administrator, DevOps, and technical support roles.
The answers are written in a simple, natural way, just as you’d explain them in an interview.
They’re short enough to answer in under a minute, while still giving you enough detail to confidently handle follow-up questions.
A computer network is simply a group of devices connected so they can communicate and share data.
These devices can be computers, servers, phones, printers, or even virtual machines.
The communication happens using standard protocols like TCP/IP, which define how data is sent and received.
Instead of sending data as one large block, it’s broken into small packets, transmitted across the network, and then reassembled at the destination.
A good real-world example is a company network where employees can access shared files, printers, and internet services through the same network.
The OSI model is a conceptual model with 7 layers that’s mainly used to understand how network communication works and to troubleshoot problems.
The TCP/IP model has 4 layers and is the model the internet actually uses.
The biggest difference is that the OSI model separates communication into more layers, while the TCP/IP model combines some of them.
For example, the Session, Presentation, and Application layers in OSI are grouped into a single Application layer in TCP/IP.
In interviews, the OSI model is especially useful because it helps you identify where a problem is happening.
For example:
So, I think of the OSI model as a troubleshooting guide, while the TCP/IP model is what real networks use every day.
It includes 240+ interview questions across three parts, with answers written the way you’d actually explain them in a real interview.
DNS (Domain Name System) is like the internet’s phonebook.
It translates a domain name, such as google.com, into an IP address that computers use to communicate.
When you enter a website address in your browser, your computer first checks whether it already knows the IP address from its local cache.
If not, it sends the request to a DNS resolver.
The resolver contacts other DNS servers until it finds the authoritative server for that domain, retrieves the correct IP address, caches the result for a period defined by the TTL (Time to Live), and returns it to your computer.
Your browser then uses that IP address to connect to the website.
Some common DNS record types are:
If I need to troubleshoot DNS on Linux, I’d typically use commands like dig, nslookup, or host to verify that a domain resolves correctly and to inspect its DNS records.
IPv4 and IPv6 are two versions of the Internet Protocol used to identify devices on a network.
IPv4 uses 32-bit addresses, which are written as four numbers separated by dots, such as 192.168.1.10.
It provides about 4.3 billion unique addresses, but with the rapid growth of internet-connected devices, those addresses have largely been exhausted.
To solve this problem, IPv6 was introduced.
It uses 128-bit addresses, written in hexadecimal and separated by colons, such as 2001:db8::1.
This provides an enormous number of unique addresses, enough to support the continued growth of the internet for the foreseeable future.
Besides offering a much larger address space, IPv6 also improves routing efficiency, supports automatic address configuration, and was designed with modern networking in mind.
Today, both IPv4 and IPv6 are widely used.
Many networks run in dual-stack mode, which means they support both protocols while the transition from IPv4 to IPv6 continues.
A subnet mask divides an IP address into two parts: the network portion and the host portion.
Devices that have the same network portion can communicate directly, while traffic to other networks must go through a router.
The /24 notation is called CIDR notation.
It means the first 24 bits are used for the network, which is the same as the subnet mask 255.255.255.0.
That leaves 8 bits for host addresses, giving 256 total addresses, with 254 usable for devices.
A few subnet sizes that are commonly asked in interviews are:
Whenever I see /24, I immediately know it’s equivalent to 255.255.255.0 and supports up to 254 devices on that subnet.
Private IP addresses are IP addresses used inside local networks, such as homes and offices.
They aren’t routable on the public internet, so the same private address ranges can be reused by millions of different networks.
The three private IPv4 ranges are:
You’ll also come across 169.254.x.x addresses, which are link-local addresses.
A device usually assigns itself one of these if it can’t get an IP address from a DHCP server.
To allow devices with private IP addresses to access the internet, routers use NAT (Network Address Translation).
NAT replaces the private source IP address with the router’s public IP address before sending traffic to the internet.
When the response comes back, the router uses its translation table to send the traffic to the correct device on the local network.
In most home and office networks, many devices share a single public IP address using a form of NAT called PAT (Port Address Translation).
TCP and UDP are both transport layer protocols, but they work differently.
TCP is connection-oriented and reliable.
Before sending data, it establishes a connection, makes sure packets arrive in the correct order, retransmits any lost packets, and checks for errors.
Because of these features, it’s used when reliable communication is important.
UDP is connectionless.
It sends data without establishing a connection or waiting for acknowledgements, so it’s much faster but doesn’t guarantee delivery or packet order.
Some common examples are:
A good example is loading a website.
Traditional HTTP and HTTPS use TCP because all the data must arrive correctly.
However, HTTP/3 uses QUIC, which runs over UDP while still providing reliable communication, making connections faster and reducing latency.
The TCP three-way handshake is the process used to establish a reliable connection before any data is exchanged.
It happens in three steps:
Once these three steps are complete, the connection is established, and data can be transferred reliably between the client and the server.
The sequence is easy to remember: SYN → SYN-ACK → ACK.
DHCP (Dynamic Host Configuration Protocol) automatically assigns network settings to devices, so you don’t have to configure them manually.
When a device joins a network, it follows a four-step process called DORA:
Along with the IP address, DHCP also provides the subnet mask, default gateway, DNS server addresses, and a lease time.
If DHCP isn’t available, many operating systems assign themselves a 169.254.x.x address, which usually indicates the device couldn’t reach a DHCP server.
A hub, switch, and router all connect devices, but they work at different layers and serve different purposes.
A hub works at the Physical Layer (Layer 1).
It simply repeats incoming data to every connected device, regardless of the destination, because of this, hubs are inefficient and are rarely used today.
A switch works at the Data Link Layer (Layer 2).
It learns the MAC address of each connected device and forwards data only to the correct destination making communication much faster and more efficient than a hub.
A router works at the Network Layer (Layer 3).
It connects different networks together and forwards packets based on IP addresses.
Home routers also commonly perform NAT, allowing multiple devices on a private network to share a single public IP address.
In simple terms, a hub broadcasts to everyone, a switch sends data to the correct device, and a router connects different networks together.
A default gateway is the router a device uses to reach networks outside its own local network.
If the destination isn’t on the local subnet, the packet is sent to the default gateway, which forwards it to the next network.
For example, if my computer is on the 192.168.1.0/24 network and I want to reach 8.8.8.8, the packet is sent to the default gateway because that address isn’t on my local network.
On Linux, I can view the routing table using the ip route command.
The routing table shows which routes the system knows about and where packets should be sent.
If there are multiple matching routes, Linux chooses the most specific route first, and if no specific route matches, it uses the default route.
ARP (Address Resolution Protocol) is used to find the MAC address of a device when its IPv4 address is already known.
When a computer wants to communicate with another device on the same local network, it broadcasts an ARP request asking, ‘Who has this IP address?‘ The device with that IP replies with its MAC address, allowing the sender to build the Ethernet frame and send the data.
To avoid sending ARP requests repeatedly, the operating system stores the results in an ARP cache, which you can view on Linux using the ip neigh command.
It’s also worth remembering that ARP is only used with IPv4.
IPv6 uses Neighbor Discovery Protocol (NDP) instead.
SMTP, POP3, and IMAP are email protocols, but they serve different purposes.
SMTP (Simple Mail Transfer Protocol) is used to send emails.
Email clients use SMTP to send messages to a mail server, and mail servers use it to relay messages to other mail servers.
POP3 (Post Office Protocol version 3) is used to receive emails by downloading them from the mail server to a device.
Traditionally, emails are removed from the server after they’re downloaded, making POP3 suitable for using email on a single device.
IMAP (Internet Message Access Protocol) is also used to receive emails, but it keeps messages on the mail server and synchronizes them across multiple devices.
That’s why most modern email services use IMAP, since people access their email from phones, laptops, and tablets.
In short, SMTP sends email, while POP3 and IMAP receive email.
The main difference is that POP3 downloads mail, whereas IMAP keeps it synchronized across devices.
HTTP and HTTPS are both protocols used to transfer web pages between a browser and a web server.
The main difference is security.
HTTP sends data in plain text, so anyone intercepting the traffic could potentially read or modify it.
HTTPS is HTTP protected by TLS (Transport Layer Security).
It encrypts the communication between the browser and the server, verifies the server’s identity using a digital certificate, and helps ensure that the data isn’t altered during transmission.
HTTP typically uses port 80, while HTTPS uses port 443.
Today, almost every website uses HTTPS because it protects user data and is considered the standard for secure web communication.
These terms describe networks based on their size or purpose.
An easy way to remember them is: PAN is personal, LAN is local, WLAN is wireless LAN, MAN covers a city, WAN covers long distances, and SAN is designed specifically for storage.
A crossover cable was traditionally used to connect two similar devices directly, such as computer-to-computer or switch-to-switch, because it swaps the transmit and receive wires.
However, on modern networks, you almost never need one.
Most network devices support Auto-MDI-X, which automatically detects the cable type and adjusts the connection.
This means a standard straight-through Ethernet cable works in almost all situations.
Today, you’d only need a crossover cable when working with older 10/100 Mbps devices that don’t support Auto-MDI-X.
These three terms describe different aspects of network performance.
Bandwidth is the maximum amount of data a network connection can carry.
For example, a 1 Gbps network link has a maximum bandwidth of 1 gigabit per second.
Throughput is the actual amount of data that is successfully transferred.
It’s usually lower than the available bandwidth because of factors like network congestion, protocol overhead, and packet retransmissions.
Latency is the time it takes for data to travel from the source to the destination and back.
It’s commonly measured in milliseconds using tools like ping.
A common interview question is whether increasing bandwidth reduces latency.
The answer is not necessarily.
A faster link can transfer more data, but it doesn’t significantly reduce the time it takes for a packet to travel across the network.
That’s why a long-distance connection can still have high latency, even on a very fast internet link.
Interview answers help you perform well in the interview, but a certification can help your resume get noticed first.
If you’re preparing for the Linux Foundation Certified System Administrator (LFCS) exam, check out the LFCS Certification Course on Pro TecMint.
It covers networking configuration along with the other LFCS exam objectives through hands-on labs and practical exercises designed to prepare you for the real exam.
A MAC (Media Access Control) address is a unique identifier assigned to a network interface.
It works at the Data Link Layer (Layer 2) and is used for communication between devices on the same local network.
A MAC address is 48 bits long and is usually written as six pairs of hexadecimal numbers, for example, 00:1A:2B:3C:4D:5E.
When a switch forwards data on a local network, it uses MAC addresses, while routers use IP addresses to forward traffic between different networks.
Although MAC addresses are assigned by the manufacturer, modern operating systems can temporarily change or randomize them for privacy reasons, especially on Wi-Fi networks.
Network reliability is measured by how consistently a network stays available and how quickly it recovers from failures.
Some common metrics are:
To improve network reliability, organizations often use redundancy, such as multiple network links, backup routers, or redundant internet connections.
This helps keep services available even if one component fails.
When troubleshooting a server that can’t reach the internet, I follow a step-by-step approach, starting from the network interface and moving upward.
This helps me identify the exact point where the problem occurs instead of guessing.
Here’s the order I’d follow:
The key is to troubleshoot one layer at a time, starting with the network interface, then IP configuration, routing, internet connectivity, DNS, and finally the application or service.
This systematic approach helps isolate the problem quickly and avoids unnecessary guesswork.
Knowing the commands is important, but knowing why you run them and in what order is what interviewers are really looking for.
For example, if you can quickly determine whether the problem is network connectivity or DNS resolution, you’re already troubleshooting like a Linux administrator.
Reading interview answers is helpful, but you’ll remember them much better if you practice saying them out loud.
In a real interview, employers aren’t just looking for someone who can list commands, they want to hear how you think through a problem.
The strongest answers explain both what command you’d run and why you’d run it next.
The more you practice explaining your troubleshooting process in a clear, logical order, the more confident you’ll sound during technical interviews.
Have you been asked a networking interview question that isn’t on this list? Share it in the comments below.
If it’s a good one, I’ll include it in the next update to help other Linux learners prepare.
15 Advanced MySQL Database Interview Questions and Answers
15 Linux Interview Questions and Answers for System Administrators
10 Core Linux Interview Questions and Answers – Part 4
10 Linux Interview Questions with Examples – Part 3
Top 15 VsFTP Server Interview Questions with Detailed Answers
15 Linux Interview Questions with Answers (Level Up) – Part 2
On troubleshooting, I always start with `mtr 8.8.8.8`.
It almost immediately gives me a complete overview of the network.
It tests the link, IP address, route, and even DNS.
So why run four commands when a single command can give you all the answers in one view?
Post like this article’s so freshers can understand with concepts clearly.
Good job
I got selected in interview after reading these basic questions.
Thank you team.
@Rajesh,
That really sounds great, congratulations for you new Job and keep visiting Tecmint.com
A few suggestions for your content as someone who has been in IT systems and network operations for over 20 years:
1.
The preponderance of three-letter acronyms for network types is overkill.
I wouldn’t expect even a skilled network engineer to know what a “PAN” or “GAN” is.
Frankly I’d never heard of either, though I suppose network survey books on the fundamentals of networking may indeed throw those largely disposable terms at newbies.
WAN, LAN, SAN, MAN, and possibly WLAN are really the only ones I’ve seen in popular parlance and I’ve been in this business for a long time.
2.
Virtually none of these questions are specific to Linux networking.
None.
These are generic, broad, and very general networking questions that aren’t specific to any particular operating system or piece of networking hardware.
Linux specific networking would probably center around stuff like iptables, tuning TCP options in the kernel configuration, bridged networking, and using OS-specific commands like ifconfig, ip, arp, etc.
– all far beyond technically the scope of what you’re trying to cover with these very basic questions.
3.
This response is not exactly correct: ”
Ans: A router is a physical device which acts as a gateway and connects to two network.
It forwards the packets of data/information from one network to another.
It acts as an interconnection Link between two network.”
A router hardly has to be physical (you may want to call it a “device” since it could be physical or virtual) for one and can be a gateway between two OR MORE networks.
High speed Internet routers can and often do route packets between millions of networks.
In any case I would clarify a router acts as a gateway between two or more networks.
All the best.
Also fails on Q3 to answer properly.
I’d fail that ;-).
It asks “Who manages these?” and that is not even addressed.
IANA would be a fair answer 😉
The usage of the term router is rather confusing for me in the original ANS of point 7, and also in this comment.
The router means originally a network entity that terminates the OSI layer 4 and selects the desired route for the information element.
The gateway, however, terminates higher layers and in some cases OSI layer 7 (e.g.
ALG).
It is no question that the physical devices may combine several functionalities over different layers, e.g.
a residential gateway has a bridge, switch, router, and gateway functions, and are called commonly routers.
Network routers are also called in some paper switches.
I would suggest to keep the layering at least in tutorials clean and let’s call things what they are.
It’s useful for me to refer
hi all
how to install a second os on laptop please help me
@Mahesh,
For dual-boot OS installation, go through this article https://www.tecmint.com/install-ubuntu-16-04-alongside-with-windows-10-or-8-in-dual-boot/
for dual boot, enter bootable CD, open BIOS, select CD from boot option, process it, when the option of formatting or booting is come then u have to skip and select next for process.
Then you have installed dual OS on single system/laptop.
Nice article.
But you didn’t answer who manage IP address in the 3rd question.
Should give the run down on IANA then go into ARIN, APAC and Afrnic etc.
keep up the good work!
Thanks …Good one
Welcome nithya
Awesome article! please publish in depth details.
Welcome @ venkatesha.
we are working to produce high quality articles for our reader.
Keep connected.
Thanks @ Avishek Kumar
Please discuss in-depth concepts in your future articles.
Really good site to learn thank’s bro…
Welcome @ saideeraj
awesome !!!!!!! very nice
Thanks @ vilas
Thanks for posting.Its very useful
Welcome @ Madvesha
Thank you for posting
Welcome @ venky sun
Basic but good to remember thanks bro keep going.
Yeah! welcome.
thank you very much , very useful please continue linux networking
Dear Mahdi,
Thanks for your Appreciation.
Find other Interview Articles here: https://www.tecmint.com/category/interview-questions/
Keep Connected!
Limit CPU Usage of a Process in Linux with CPULimit Tool
How to Setup Central Logging Server with Rsyslog in Linux
6 Key Performance Metrics to Monitor in Linux Servers – Part 1
How to Install Zabbix on RHEL 8
Cockpit – A Powerful Tool to Monitor and Administer Multiple Linux Servers via Browser
How to Install vnStat and vnStati to Monitor Network Traffic in Linux
4 Ways to Disable Root Account in Linux
Linux Tricks: Play Game in Chrome, Text-to-Speech, Schedule a Job and Watch Commands in Linux
DSH (Distributed Shell) – Run Commands on Multiple Linux Servers
2 Ways to Re-run Last Executed Commands in Linux
How to Repair and Defragment Linux System Partitions and Directories
How to Determine and Fix Boot Issues in Linux
5 Best Open-Source School Management Software for Linux
6 Best Modern Linux ‘init’ Systems (1992-2025)
5 Best PDF to Word Converters for Linux
16 Best Notepad++ Alternatives for Linux in 2025
Top 6 Command Line Music Players for Linux Users
7 Best Skype Alternatives for Linux in 2025
—
**📚 Original Source:**
[20 Linux Networking Interview Questions and Answers for 2026](https://www.tecmint.com/networking-interview-questions/)
About The Author
