DoS vs DDoS
One source vs many — literacy on availability, never a flood against anyone else.
Visual · dos_vs_ddos
DoS is denial from a source; DDoS is distributed. Original Cyberlium.
Availability is a security goal. Flooding someone else is not a homework submit button.
Confidentiality and integrity get the headlines. Availability is the third classic goal: the service still answers the people who are allowed to use it. Denial of service (DoS) is the idea that a source can spend a victim's capacity. Distributed denial of service (DDoS) is the same idea with many sources. This module teaches you to name those ideas and to protect capacity YOU own. It does not teach you to knock anyone offline. Original Cyberlium.
1. DoS: one story about scarce capacity
A service has finite CPU, memory, sockets, bandwidth, and human attention. A denial-of-service condition is when those finite things are spent so legitimate work cannot complete. The source might be a bug (one request that livelocks a parser) or a brute volume. Both are availability failures. Only one looks like a “flood” on a graph.
On YOUR loopback helper, a tight loop of requests is still YOUR CPU talking to YOUR CPU. That can teach rate limits later. It is not permission to aim the same loop at a classmate, a game, or a public site.
2. DDoS: many sources, same scarce thing
Distribution makes attribution and blocking harder. It does not change the ethics: you still do not purchase “booter” time, join a flood, or “test” a school portal. Providers and incident responders exist for a reason. Students are not those teams just because a quiz used the acronym.
Cyberlium XP for finishing a lesson is not a pentest authorization and not a cert that says you may DDoS.
3. Identify DEMO, then do not “practice” on it if it is a router
If http://192.168.0.1/ is Router Admin, STOP. Availability testing a home gateway you casually share is how families lose Wi-Fi. This course never uses hping3 against that box.
Write the two definitions. You are ready to split volumetric noise from application-layer expensive requests.
Command guide
Identify DEMO, then do not “practice” on it if it is a router
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install python3
macOS:
Command — copy this
brew install python3
Windows: Download https://python.org/downloads/
═══ COMMANDS ═══
Command — copy this
python3 - << 'PY'
import socket
s = socket.socket(); s.settimeout(0.4)
print("127.0.0.1:8787", s.connect_ex(("127.0.0.1", 8787))); s.close()
print("do not probe other LAN IPs; do not flood")
PY4. What you ship: two definitions and a hard no-flood rule
DoS = capacity denial from a source. DDoS = many sources. Labs stay on No hping3, no booters, no LAN victims. DEMO GATE holds.
5. What you record before the next lesson
Date. DoS vs DDoS one line each. DEMO identified/STOP. SAFE NEVER hping3 flood, nmap /24, hydra. File t11-m08-l01-dos-vs-ddos.txt.
6. Wrong vs right: stranger networks vs literacy on systems you own
Worked failure — same network word, opposite target. Right never needs a café or campus LAN.
- Wrong: hping3 a game server “because DDoS is the module.” LOIC against a news site. nmap /24 to pick a “lab victim.”
- Right: Write the definitions. Keep stress tests for YOUR loopback later. Next: Volumetric vs Application Layer.
Mission: name DoS and DDoS without performing them
1) / STOP if router. 2) Write DoS vs DDoS in cyberlium-lab. 3) Write that hping3 floods of others are out. Never flood. Never scan for victims.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor what “capacity” means for a tiny Python server — not how to find a booter.
APPLY: A single buggy request makes YOUR toy API never return. Closest name?
APPLY: True or False: DDoS just means “DoS but the student used nmap first.”
APPLY: curl http://192.168.0.1/ is Router Admin. Availability homework?
Volumetric vs Application Layer
Part of Network Security with AI — DDoS Types and Availability Defense.
Rate Limits and Capacity You Own
Part of Network Security with AI — DDoS Types and Availability Defense.
Lab — Rate-Limit YOUR Loopback Server
Part of Network Security with AI — DDoS Types and Availability Defense.