[go: up one dir, main page]
Scribd
Upload
22 views2 pages

Week 4 - Linux Troubleshooting Activity

The document outlines a Linux networking activity focused on troubleshooting common network issues. It includes objectives, prerequisites, and step-by-step instructions for verifying interface status, checking IP addresses and gateways, testing connectivity, and DNS troubleshooting. Students are required to document their command outputs and answer reflection questions on their experiences during the activity.

Uploaded by

okaykoo728
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
22 views2 pages

Week 4 - Linux Troubleshooting Activity

The document outlines a Linux networking activity focused on troubleshooting common network issues. It includes objectives, prerequisites, and step-by-step instructions for verifying interface status, checking IP addresses and gateways, testing connectivity, and DNS troubleshooting. Students are required to document their command outputs and answer reflection questions on their experiences during the activity.

Uploaded by

okaykoo728
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/ 2

Linux Networking Activity: Troubleshooting Common Network Issues

Objective
Students will practice identifying and resolving common networking issues using Linux
commands and tools.

Prerequisites
- A Linux system (Ubuntu preferred)
- Terminal access with sudo privileges
- Basic understanding of Linux networking commands

Instructions

Part 1: Verify Interface Status


1. List all network interfaces:
ip a

2. Check if interface is up or down:


ip link show
nmcli device status

3. Bring the interface up if it is down:


sudo ip link set <interface> up

Part 2: Check IP Address and Gateway


4. Verify IP address:
ip addr show

5. Check default gateway:


ip route

6. Add a default route if missing:


sudo ip route add default via <gateway-ip>

Part 3: Test Connectivity


7. Ping the default gateway:
ping -c 4 <gateway-ip>

8. Ping an external server (e.g., Google DNS):


ping -c 4 8.8.8.8

9. Use traceroute to trace the route:


traceroute google.com
Part 4: DNS Troubleshooting
10. Check DNS settings:
cat /etc/resolv.conf

11. Test domain name resolution:


nslookup google.com
dig google.com

Deliverables
- Command outputs and steps taken for each part
- Answers to the reflection questions

Reflection Questions
- What was the most common issue encountered?
- Which commands helped identify the root of the problem?
- How did you verify that the issue was resolved?

You might also like