Linux for network engineers lab 1 of 14
iproute2: addresses, routes, neighbours and sockets
A new Linux box arrives at the depot with nothing configured. You give it addresses, routes and neighbours with `ip`, see its sockets with `ss`, and make a host's settings permanent.
Run this lab
It needs Lite: its 3 nodes are set to 3 vCPU and 1,536 MB in total. That fits the free demo too.
In your workspace: Shared, then Linux for network engineers guided labs, then 01 - iproute2 - addresses routes neighbours and sockets
- Level
- Beginner
- Time
- About 50 minutes
- Nodes need
- 3 vCPU, 1,536 MB
- Smallest plan
- Lite
The scenario
You've just joined the network team at Kestrel Couriers. The new Linux box at the Leeds depot, LNX1, arrived with nothing configured. It has to reach the depot router R1 and the office PC H2 by lunchtime, and the team's rule is simple: use ip and ss, the iproute2 tools you'll find on every current distribution.
| Device | Interface | Address | Role |
|---|---|---|---|
| LNX1 | eth0 | 10.1.10.10/24, then 10.1.10.11/24 | the new box (you configure it) |
| R1 | Gi0/0 | 10.1.10.1/24 | depot gateway |
| R1 | Gi0/1 | 10.1.20.1/24 | office gateway |
| R1 | Loopback1 | 10.1.99.1/24 | head office, as far as this lab goes |
| H2 | eth0 | 10.1.20.20/24 | office PC |
| Device | Runs | How to log in |
|---|---|---|
| H2 | Alpine Linux 3.20 | root, no password. |
| R1 | Cisco IOSv 15.9 | The console opens at >; enable has no password. |
| LNX1 | Alpine Linux 3.16 with iptables and iproute2 | Opens on a menu: press 5, then Enter, for a root shell. |
What you’ll practise
- Read interfaces, addresses, routes and neighbours with iproute2
- Add primary and secondary addresses and choose the source address
- Add static and default routes and prove the longest-prefix match
- Read and set neighbour entries
- List listening and established sockets with ss
- Make network settings persistent on Alpine and name the equivalents on other distributions
The tasks
- Start the Linux nodes
- Read the box before you touch it
- Bring up the port and add an address
- Add a second address
- Routes and the longest match
- Neighbours
- Sockets with ss
- Make H2's settings survive a reboot
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- LNX1
eth0to R1Gi0/0 - R1
Gi0/1to H2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| H2 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| LNX1 | Alpine WAN emulator | clbalpinewanem-alpine-3-16-2-wanem | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Linux for network engineers guided labs.Open
01 - iproute2 - addresses routes neighbours and socketsand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More Linux for network engineers labs
All Linux for network engineers labs
CloudLabBox is independent of Cisco, CompTIA, the Linux Foundation and the Linux Professional Institute. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.