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

M33 - Firewall: GUI and CLI

Understand what a host firewall does, inspect common firewall tools, and make only deliberate, minimal rule changes in the right context.

Networking

Firewall: GUI and CLI

Understand what a host firewall does, inspect common firewall tools, and make only deliberate, minimal rule changes in the right context.

35 min INTERMEDIATE BOTH Curriculum-reviewed
Prerequisites
Module M30 - Network Config: CLI Module M32 - Network Diagnostics
What you should be able to do after this
  • Explain what a host firewall is controlling.
  • Inspect basic firewall state on each platform.
  • Understand why minimal, intentional rules are safer than broad openings.

Why This Matters

A service can be listening correctly and still remain unreachable because a firewall is blocking the path.

That is why firewalls belong in the networking model rather than in a separate mystery category.

1. What a Host Firewall Does

A host firewall decides which network traffic is allowed to reach local services.

That means it can:

  • allow a needed port
  • block an unwanted port
  • restrict traffic based on direction, protocol, or other criteria

In simple terms, it acts as a gatekeeper between the network and the local machine.

2. Inspect the Firewall First

Before adding or removing rules, find out what the current firewall state already is.

Inspect Windows Firewall Tools

wf.msc

GUI inspection is often the clearest first step on Windows.

Inspect UFW Status

sudo ufw status verbose

3. Prefer Minimal, Intentional Rules

A safer firewall habit is to open only what is needed, not everything that might possibly work.

Examples of safer thinking:

  • allow one service, not all traffic
  • prefer the narrow port or protocol needed
  • understand whether the rule is inbound or outbound

Least-Exposure Habit

If a service only needs one inbound port, do not create a broad rule that opens far more than that.

4. Firewalls Are Not the Only Gate

A host firewall may be only one control point.

There may also be:

  • router rules
  • cloud security groups
  • upstream network firewalls

So “I opened the port on the machine” does not automatically prove the full path is open.

What to Ignore for Now

  • advanced packet filtering syntax
  • complex enterprise firewall policy design
  • deep stateful inspection internals

The important skill here is knowing where firewall checks fit in the troubleshooting chain.

Before You Move On

You are ready for the networking capstone when you can:

  1. explain what a host firewall does
  2. inspect basic firewall state on your platform
  3. explain why narrow rules are safer than broad ones

Next, we put the networking model together in a full connectivity-debug scenario.