Week 07 · lesson

Lesson 4: Internet and Network Types SOHO Lab

Core path: 42 minutes

Build the network from the provider edge inward, then classify what kind of network each boundary represents.

Internet connection types

Compare these at recognition/design depth:

  • satellite;
  • fiber;
  • cable;
  • DSL;
  • cellular;
  • WISP.

Different connection types change latency, bandwidth, physical handoff, coverage, and availability assumptions.

Network types

Recognize:

  • LAN;
  • WAN;
  • PAN;
  • MAN;
  • SAN;
  • WLAN.

These describe scope/purpose, not specific brands.

Lab topology

Design a fictional small office:

provider service
→ cable modem / DSL device / ONT / WISP/cellular edge as appropriate
→ router/firewall
→ managed or unmanaged switch
→ wired endpoints
→ access point
→ wireless endpoints

Use documentation-range or private lab addressing only.

Required decisions

Document:

internet connection type:
provider handoff device:
router/gateway:
switch type:
PoE need:
AP placement:
IPv4 private subnet:
static vs dynamic endpoints:
IPv6 expectation:
LAN/WLAN boundaries:
WAN boundary:

Then identify whether a phone-to-headset Bluetooth link is a PAN and why a storage network could be classified as a SAN.

Fault injection

Choose two:

  • cable service reaches modem but router WAN link is disconnected;
  • ONT has provider signal but router lacks valid WAN configuration;
  • endpoint receives APIPA instead of expected DHCP address;
  • AP has data link but lacks required PoE power;
  • endpoint has valid local address but wrong gateway;
  • wrong cable/environment selection for a building run.

Success criteria

A passing design can explain provider connection type, edge hardware, LAN/WLAN topology, IP addressing mode, and physical media as one connected system.

Technician topology

Trace the SOHO network before naming the failure

A current A+ small-office/home-office topology. Predict what survives, trace one dependency at a time, inspect evidence, then defend the narrowest supported diagnosis.

1. predict2. run3. inspect4. compare

What do you expect to keep working, and where do you think the path will stop?

Read the topology as text
  • ISP: upstream service
  • Modem / ONT: provider handoff
  • Router / firewall: gateway, NAT, policy
  • Switch: wired local network
  • Access point: wireless local network
  • Desktop: wired client
  • Network MFD: wired print/scan endpoint
  • Laptop: wireless client
  1. ISPModem / ONT: provider link
  2. Modem / ONTRouter / firewall: WAN handoff
  3. Router / firewallSwitch: LAN uplink
  4. Router / firewallAccess point: wireless LAN
  5. SwitchDesktop: Ethernet
  6. SwitchNetwork MFD: Ethernet
  7. Access pointLaptop: Wi-Fi
Ghostty terminal simulation

Diagnose an APIPA-style DHCP failure

Recognize an automatically assigned address, verify the missing gateway, renew the simulated lease, and retest local connectivity.

Ghostty Web renders the terminal, but this lesson still uses a controlled Robotnix command engine. No unrestricted operating-system shell is connected.

Commands worth trying
  • ipconfig
  • ipconfig /all
  • ping 192.168.10.1
  • ipconfig /renew
  • ipconfig
Read a deterministic terminal transcript

This fallback runs the same bounded Robotnix simulation against the suggested command sequence. It does not connect to an operating-system shell or network.

Robotnix DHCP diagnosis simulation
No real adapter, DHCP server, or network is connected. Type 'help' for supported commands.

$ ipconfig
Ethernet adapter Ethernet:
   Autoconfiguration IPv4 Address. : 169.254.44.21
   Subnet Mask . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . :

$ ipconfig /all
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . . : Yes
IPv4 Address. . . . . . . . . . . : 169.254.44.21
DHCP Server . . . . . . . . . . . : unavailable

$ ping 192.168.10.1
PING: transmit failed. General failure.
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

$ ipconfig /renew
Windows IP Configuration
DHCP lease obtained from simulated SOHO router.

$ ipconfig
Ethernet adapter Ethernet:
   IPv4 Address. . . . . . . . . . : 192.168.10.25
   Subnet Mask . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . : 192.168.10.1

Read it. Prove it.

Lesson knowledge checks

Answer from the lesson you just completed. Results stay in this browser and are not submitted.
Knowledge check 1

Which device should sit at the boundary between a small LAN and an ISP connection?

Knowledge check 2

Why might an access point be connected to a switch instead of replacing the switch?