Learn Understand first, then practice while the concept is still fresh.

M30 - Network Config: CLI

Inspect network state from the command line and treat live configuration changes with enough caution to avoid breaking access unexpectedly.

Networking

Network Config: CLI

Inspect network state from the command line and treat live configuration changes with enough caution to avoid breaking access unexpectedly.

40 min INTERMEDIATE BOTH Curriculum-reviewed
Prerequisites
Module M28 - Network Model: How Networks Work Module M29 - Network Config: GUI
What you should be able to do after this
  • Inspect IP configuration and routing from the CLI.
  • Recognize common clues such as missing gateway or fallback addresses.
  • Understand why remote configuration changes should be tested carefully.

Why This Matters

The CLI is often the fastest way to answer a network question, especially on servers or remote systems.

Common first questions are:

  • do I have an address?
  • what route handles traffic leaving the local network?
  • what DNS or interface state do I currently have?

1. Inspect the Current Address State

Inspect Address State on Windows

ipconfig ipconfig /all Get-NetIPAddress

Inspect Address State on Linux

ip addr ip -br a nmcli device show

This is where you notice clues such as:

  • no usable address
  • wrong interface state
  • unexpected address ranges
  • missing DNS information

2. Inspect the Route Out

If a host can talk locally but not beyond the local network, routing becomes the next question.

Inspect Routes on Windows

Get-NetRoute route print

Inspect Routes on Linux

ip route

You are often looking for the default route or default gateway equivalent.

3. Treat Live Changes Carefully

Changing network settings from the CLI is powerful, but it can also cut off access immediately if you are remote.

Remote Safety Rule

If you are connected over SSH or another remote path, assume a bad change can disconnect you. Inspect first, document the current state, and prefer reversible or testable approaches.

That does not mean you should fear the CLI. It means you should respect the consequences of changing the interface you are actively using.

What to Ignore for Now

  • advanced multi-route policy
  • persistent config syntax for every Linux distro
  • advanced Windows enterprise network automation

The important skill here is inspection and cautious reasoning.

Before You Move On

You are ready for the DNS lesson when you can:

  1. inspect address state from the CLI
  2. inspect routing state from the CLI
  3. explain why remote config changes deserve caution

Next, we separate name resolution problems from basic connectivity problems.