Search Results

The cluster makes a few structural choices on purpose: Two vSwitches, not one. One private (cluster heartbeat plus VM east-west traffic), one public (inbound). Keeping the latency-sensitive cluster chatter on its own network means a busy public link can't dis...

MTU is the one that will haunt you. A vSwitch with VXLAN encapsulation adds overhead to every frame. Leave the VM/bridge MTU at the default 1500 and you get the classic, maddening symptom: ping works, but SSH hangs and TLS half-loads — small packets pass, lar...

What you'll learn What an IP address actually is and why machines need one. The difference between a public and a private address. What "a network" means, and how a host knows whether a destination is local or remote. The role of the default gateway and DNS i...

What you'll learn What a subnet mask is and what the /24 in 10.100.100.0/24 means. How to split an address into its network part and host part. Why the network address and broadcast address can't be used for hosts. How to look at any two addresses and decide ...

What you'll learn Why IP addresses alone aren't enough — and what a port adds. The difference between TCP and UDP, and when each is the right choice. What the TCP three-way handshake is and why "connection" means something specific. How to read ss/netstat out...

What you'll learn What ICMP is and why it's separate from TCP/UDP. How ping and traceroute actually work. A repeatable mental model for diagnosing "I can't reach X" — from the bottom of the stack up. Which tool answers which question, so you stop guessing. T...

Goal: prove you can read a real machine's network configuration and reason about it — the skills from Lessons 1 and 2. Where: SSH into the Jumpbox (your mentor will give you access). Everything here is read-only; you won't change anything. Tasks Find the Jump...

Goal: apply the bottom-up troubleshooting model (Lesson 4) and the TCP/port concepts (Lesson 3) to figure out why a connection fails — and prove it with evidence, not guesses. Where: from the Jumpbox. You'll probe a few real lab services and one deliberately-w...

Welcome. This is a 12-week, hands-on path from "I can use a computer" to "I can deploy and operate real systems." It's built for people who are new to Linux and infrastructure — every module assumes only what the modules before it taught. You drive; the mentor...

The program is 11 modules over 12 weeks, at roughly 30 hours per week. The order is deliberate: you learn to operate one machine by hand, then package it, orchestrate it, automate it, package it for Kubernetes, and finally observe it. The arc operate ─▶ contai...

Here is the bar for each module — what you should be able to do (not just recognise) before moving on. If you can do the things on the line, you're ready for the next module. These are also exactly what your mentor will look for at the weekly checkpoint. After...

Let's be transparent about how this works. This internship is a talent pipeline — the goal is to find people we want to keep. So it's worth knowing what "doing well" actually means here. We measure trajectory, not trivia You are not expected to master ten deep...

What you'll learn What a kernel actually does and why every computer needs one. The difference between kernel space and user space, and why that split exists. How system calls form the controlled boundary between your programs and the hardware. What a process...

What you'll learn Why Linux has one tree of directories starting at / instead of drive letters. What lives in the most important directories: /etc, /var, /home, /usr, /bin, /tmp. What the "virtual" directories /proc and /dev are and why they aren't real files...