Menu

Test a Route

Part of the Stopping the Spread section of Coddy's Cybersecurity journey. Lesson 2 of 20.

A failed connection does not always mean a firewall blocked it. The destination program might simply be stopped.

Use probe to check the current route for a known connection:

seclab probe demo-order

You should see:

till-north -> demo-shop:443
Blocked: service_stopped

The result says service_stopped. The destination service is not running, so changing a firewall rule would not fix this problem.

In this practice case, the maintenance note confirms that demo-checkout should be running. Start it:

seclab process demo-checkout start

You should see:

demo-checkout: running.

Probe again:

seclab probe demo-order

You should see:

till-north -> demo-shop:443
Allowed: allowed (rule 1)

The route is now allowed. Probe checks the route without sending a customer file or advancing the clock. Read its reason before choosing a repair.

challenge icon

Challenge

Easy

Ticket from Sam, IT lead

Checkout stopped working after maintenance. Trace the place-order connection and find why it fails. Restore the approved service so customers can order again. Keep dispatch-pc’s approved backup working and leave the earlier account protections in place.

Try it yourself

Terminal

All lessons in Stopping the Spread