linuxlab.io
Tutorials▾
  • Linux & networking
    File system, processes, TCP/IP, BGP and OSPF
    →
  • Terraform & IaC
    HCL, state, plan/apply on a LocalStack sandbox
    →
  • Git & GitHub
    Object model, plumbing, branching, GitHub Actions
    →
All tutorials →
PricingAboutSign inCreate account
/
  • Introduction
  • Lessons
  • How it works
  • Simulator
  • Knowledge base
  • Interview prep
Lessons
Footer
linuxlab-TutorialsPricingAboutPrivacy & cookies
Copyright © 2026 LinuxLab. All rights reserved.

← из прошлого урока

cgroups v2 are limits on CPU and memory. Next comes another axis of constraint: the network. tc + netem simulate a poor link: delay, loss, duplication. Without this you cannot run proper chaos in CI.

← к прошлому уроку

Продвинутый

tc + netem: simulating a bad network

15 мин · урок входит в курс «Продвинутый»

tc (Traffic Control) is the kernel's main subsystem for shaping, queueing, and classifying traffic. Today one part matters: netem (network emulator), which adds artificial latency, loss, duplication, and reordering on an interface.

Why: you check how an application behaves when the network degrades. A common combination is netem plus tcp-handshake/tcp-states, to watch how retransmits and timeouts catch the loss. Production CI often runs integration tests with tc qdisc add ... loss 5%, which catches race conditions that never surface on a clean LAN.

Урок закрыт

Чтобы запустить sandbox и пройти этот урок целиком, нужен соответствующий курс. Внутри - ещё много практических уроков того же уровня и сквозной прогресс.

Купить курсВойти← Все уроки

дальше →

You can model a bad network now. Next: how TCP behaves under these conditions, and which sysctl knobs let you tune it. CUBIC vs BBR, keepalive, the congestion window in plain sight.

Открыть превью: TCP tuning: sysctl, congestion control, ss -tiв курсе «Продвинутый» - /pricing
Footer
linuxlab-
Copyright © 2026 LinuxLab. All rights reserved.
Tutorials
Pricing
About
Privacy & cookies