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.

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

You saw SYN/ACK on a single host. Now the same thing, but between different ones: three containers, two segments, and a packet that has to physically go somewhere and come back. You figure out where routing breaks.

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

Средний

Routing: h1 → r1 → h2 by hand

20 мин · урок входит в курс «Средний»

You have three containers: two hosts (h1, h2) and a router r1. Between them run two Ethernet "buses":

  • 10.10.1.0/24 connects h1 (10.10.1.10) and r1 (10.10.1.1)
  • 10.10.2.0/24 connects r1 (10.10.2.1) and h2 (10.10.2.10)

There is no direct link between h1 and h2; packets have to go through r1. Right now h1 does not know how to reach h2's subnet, and r1 is not yet set up as a router. You fix this by hand, step by step.

Switch between nodes with the "nodes" tabs at the top right.

Урок закрыт

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

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

дальше →

L3 connectivity is in place; the machines can see each other by IP. But people do not remember IPs, they remember names. Next comes DNS: resolvers, /etc/resolv.conf, and how dig shows the real path of a query.

Открыть превью: DNS: how a name becomes an addressв курсе «Средний» - /pricing
Footer
linuxlab-
Copyright © 2026 LinuxLab. All rights reserved.
Tutorials
Pricing
About
Privacy & cookies