LAB-NET-01 - Interfaces and IP Addresses
Identify local network interfaces and addresses so you can tell which interface is active and which address actually matters for the current network path.
Interfaces and IP Addresses
Identify local network interfaces and addresses so you can tell which interface is active and which address actually matters for the current network path.
- Identify local network interfaces and addresses so you can tell which interface is active and which address actually matters for the current network path.
- Repeat the workflow without copy-paste or step-by-step prompting.
- Run network changes in a lab or VM first so you do not break your active connection unexpectedly.
Part A: The Field Guide
Before troubleshooting connectivity, you need to know which interface and address the system is actually using.
This lab keeps the goal simple:
- inspect interfaces
- identify your current address
- separate loopback from the real network path
Cross-Platform Truth
Even if you mainly use Windows later, the same ideas still matter: which interface is active, which address is local, and which address is only loopback.
Important Distinction
The loopback address proves the local networking stack is alive. It does not prove that your machine can reach the wider network.
Part B: The Drill Deck
Terminal required: inspection first, no risky changes.
G Guided Step by step - type exactly this and compare the result >
Exercise G1: Show the interface list
- Run
ip -br a - Identify the
lointerface - Identify the main non-loopback interface if present
- Note its IPv4 address if one is shown
Exercise G2: Look at the fuller view
- Run
ip addr - Find the
inetline for your main interface - Find the
link/etherline - Explain which one is the network address and which one is the hardware address
Exercise G3: Compare loopback and external identity
- Note the address on
lo - Note the address on your active network interface
- Explain why these serve different roles
S Solo Task described, hints available - figure it out >
Exercise S1: Short explanation
In your own words, explain:
- what loopback is for
- why one machine may have more than one interface
- why the visible IP can differ by interface
Exercise S2: Optional link-only view
- Run
ip -br link - Compare it with
ip -br a - Explain what disappears when you ask for the link layer instead of the address layer
M Mission Real scenario - no hints, combine multiple skills >
Mission M1: Identify the interface that matters
Using only inspection commands, answer:
- which interface appears to be carrying normal network traffic
- which address is only for internal loopback use
- which details you would quote first if someone asked for your current local IP
If you can answer that cleanly, the first step of networking is under control.
What to do next
Best next step LearningReturn to the related lesson if you want the concept explained more deeply.