weekly_status --public

This week focused on network-layer security and how routing, addressing, and lab simulations fit into secure network engineering.

student@dvcltr:~$ status --week module-03

./completed_this_week

  • Practiced subnetting and NAT concepts.
  • Completed a Docker-based lab related to network traffic and denial-of-service concepts.
  • Continued wargame practice with Bandit or Natas.
  • Discussed the evolution of IP addressing and Layer 3 security.
  • Added module vocabulary through the glossary activity.

ls projects/

[COMPLETED] Subnetting and NAT Practice
Focus: IP Addressing / Network Design
Summary: Worked with subnetting and NAT as core pieces of network structure.
What I learned: Good network design depends on understanding address space, segmentation, and how traffic moves between networks.
[COMPLETED] Docker-Based Traffic Lab
Focus: Network Simulation / Security Testing
Summary: Used a controlled lab environment to study traffic behavior and defensive implications.
What I learned: Containerized labs are useful for safely practicing network security concepts without exposing real systems.
[COMPLETED] Layer 3 Security Discussion
Focus: Network Layer Security
Summary: Reviewed how IP addressing and network-layer decisions affect security.
What I learned: Addressing, routing, and segmentation are security-relevant design choices, not just networking details.

cat currently_learning.txt

  • Subnetting and NAT
  • IP addressing strategy
  • Network-layer security
  • Docker-based lab environments
  • Safe simulation of network behavior

echo $BIGGEST_TAKEAWAY

The biggest takeaway this week was that network structure directly affects security visibility and control. Subnetting, NAT, and Layer 3 decisions shape how defenders monitor and protect systems.

next --focus

  • Continue wargame practice.
  • Move into transport-layer and VPN-related security.
  • Keep connecting lab work to defensive monitoring.