Chapters

Network Topologies Module Guide

Start With One Site

This section: Start With One Site — A gateway is a bridge between networks.

A gateway is a bridge between networks. A protocol is a shared set of rules. Picture a site with cameras, small sensors, and one control room. Sketch who talks to whom, which device relays data, and which shared point can stop the service.

Use that sketch through this guide. Name the network shape, measure its paths and weak points, break one link, and record how service returns. The goal is a topology choice that a second person can inspect and test.

Follow Packet Pete as a cold-room alarm reaches a local relay but not the night operator.

  1. Packet Pete sees a cold-room sensor deliver an alarm to a nearby relay.

    The cold-room alarm reaches the local relay.

  2. Packet Pete observes as the route beyond the relay breaks before the operator.

    The same alarm does not reach the night operator.

  3. Pete marks the local hop as working and the end-to-end path as failed.

    One healthy link does not prove the full service.

  4. Two green characters work at night beside a monitor with a large red X. One holds a tablet showing a network path, while the other checks a clipboard. A small graph rests on the desk beside them.

    Remove one part and record what recovers.

A cold-room alarm reaches a local relay but not the night operator.
Packet Pete, your networking guide

Your guide: Packet Pete

“A packet you can’t trace is a claim you can’t defend — name the address, the route, and the hop that dropped it.”

Start With the Story

This section: Start With the Story — Picture a site plan where every sensor already has a job, but nobody can explain why one device talks through a hub, another relays through a neighbour, and a third needs a gateway before its data matters.

Picture a site plan where every sensor already has a job, but nobody can explain why one device talks through a hub, another relays through a neighbour, and a third needs a gateway before its data matters. This compact module turns that drawing into a defensible topology story: name the shape, measure its dependencies, test failure behaviour, select a bounded design, and record what makes it ready to release.

Start Here

This module teaches network topology, not a complete protocol stack. It has six substantive chapters and one topology lab. Older chapter names in this route are compatibility redirects, not additional lessons or labs.

What This Module Covers

This section: What This Module Covers

The six current chapters form one learning path:

  1. Core Topology Shapes and Trade-offs — recognise star, bus, ring, tree, mesh, and hybrid shapes and compare their first-order trade-offs.
  2. Measuring Topologies with Graph Metrics — model the network as a graph and examine paths, dependencies, scale, and failure domains.
  3. Topology Failure and Recovery — trace partitions, bottlenecks, shared failures, recovery paths, and evidence of restored service.
  4. Topology Selection Records — turn scenario constraints into a shortlist, pilot checks, and a bounded selection record.
  5. Managing Live Topology Changes — review changes to participating nodes, roles, routes, operating modes, and retest conditions.
  6. Network Design Readiness — connect device and traffic constraints to infrastructure boundaries, an address plan, topology views, and release gates.
  7. Practice: Trace and Compare Topologies — practise flow tracing, failure probes, comparison, and a design handoff.

Choose A Starting Point

This section: Choose A Starting Point

New to topology

I need the concepts first

Begin with Core Topology Shapes, continue to Topology Metrics, then study Failure and Recovery.

Making a choice

I have constraints to evaluate

Use Topology Selection Records. If the network already exists and its roles or routes are changing, continue to Managing Live Topology Changes.

Release review

I need to defend the deployment

Use Network Design Readiness to connect constraints, boundaries, addressing, topology records, ownership, and recheck triggers.

Practice

I need a hands-on exercise

Use the single current Topology Lab. It covers topology sketches, flow traces, failure probes, evidence notes, and a design handoff.

Where Protocol Content Lives Now

This section: Where Protocol Content Lives Now — The old iot-protocols-* pages in this module redirect to a general readiness chapter; they are not protocol lessons.

The old iot-protocols-* pages in this module redirect to a general readiness chapter; they are not protocol lessons. Use the current books instead:

These destinations cover the topics named above. This guide does not claim that they replace a dedicated IPv6, 6LoWPAN, CoAP, or MQTT course.

Quick Route Check

This section: Quick Route Check

A device fleet has mixed cameras, low-power sensors, and a gateway. Where should I start?

Start with Core Topology Shapes to identify the physical and logical patterns. Then use Topology Metrics and Failure and Recovery to expose shared dependencies before making a selection.

A small payload is failing because headers and retries consume too much airtime. Does this module teach that analysis?

No dedicated protocol-overhead lesson is delivered here. Use the linked current protocol books; return to Topology Metrics if relay count, path length, or shared links contribute to the failure.

A reviewer asks why the network is release-ready. Which path should I start with?

Start with Network Design Readiness. It asks for traceable device and traffic constraints, infrastructure boundaries, addressing, topology views, ownership, and future recheck conditions.

Review Questions

This section: Review Questions

Before leaving this module, make sure you can answer:

  1. Which topology is being used physically, and which topology describes the logical data flow?
  2. What device, traffic, energy, latency, and failure constraints shaped the network choice?
  3. Which nodes, links, paths, and shared roles create the most important dependencies?
  4. What evidence shows that required flows survive, recover, or fail safely under expected faults?
  5. What address plan, ownership record, and recheck trigger make the topology decision reviewable?

Back to All Modules

Find help

3 reviewed answers.

Where should I start in a module?

Open the module page from the sidebar to see its chapters in order. Use the module map to return to a topic you need.

Modules and paths

Reviewed

What can I try when a project does not work?

Check the symptom, then work through the diagnostic steps. Keep the error message and the smallest example that reproduces it.

When you are stuck

Reviewed

How do interactive examples work?

Use the interactive guide to check how examples and simulations work before changing your project.

Interactive examples guide

Reviewed