B04
Port Channel with LACP
- Devices
- Platforms
- EVE-NG / GNS3
- Mode
- Practice / Reference
Projects / Network Lab FactoryIndependent project · Design & implementation
Turn an idea into
a working lab.
I built a terminal assistant to create network labs and prepare IPv4 addressing in existing topologies—with group pools, fixed choices and a review before changes.
See the actual interface1 / CHOOSE
A recipe with a purpose.
Choose the exercise. The topology, interfaces and requirements come from one consistent recipe.
B04 / 2 switches + 2 hosts
Topology from the implemented recipe · select a device to inspect it
Select a device to see its prepared interfaces.
24 reference scenarios · recorded validation on EVE-NG and GNS3.
Inspect the recorded resultsThe tool,
in your terminal.
Create a lab from a recipe, or address the routers you already connected. Review automatic and fixed assignments together before applying them.
One tool.
A wider practice ground.
From two routers to a Nexus fabric. Each scenario defines what gets prepared and what you get to practice.
It has to work.
And show its work.
Every reference scenario was deployed and checked on both tested platforms. The evidence records preparation checks, protocol observations and reachability.
Open the validation reportHistorical catalog campaign: October 29, 2026. One implemented variant per scenario, limited to the documented images and profiles. It does not validate the new portable connection or existing-lab assistant. Their real-lab tests remain pending.
Recorded validationEVE-NGGNS3
Basic scenarios8 / 8 passed8 / 8 passed
Intermediate8 / 8 passed8 / 8 passed
Advanced8 / 8 passed8 / 8 passed
Existing-lab preview · automated checks
294 tests and CI on Python 3.11–3.13. Pool allocation, preservation checks, partial failures and the assistant flow are covered with fixtures. Read the scope and pending validation.
Beyond the happy path
Selected fault / recovery tests, five GNS3 practice samples and a Nexus reboot check are documented separately.
A clean end to the experiment
All owned QA labs were removed after testing. Existing projects were preserved.
The engineering behind the experience.
One recipe drives the entire lab.
Devices, interface assignments, generated configuration, diagrams and checks share the same source. This keeps the preview consistent with what the assistant prepares.
Preparation and learning are separate.
Practice mode sets up the prerequisites without completing the exercise. Reference mode applies the solution and verifies it. The scenario documentation explains that boundary.
Existing configurations are a constraint.
The assistant reads the lab before planning, reserves fixed and observed subnets first, and adds only missing primary IPv4 addresses. It rechecks the topology and configuration before writing, keeps private backups and asks separately before permanent save. Unread devices make a plan export-only.
A failed check stays a failed check.
The tool preserves partial records and does not silently recreate an interrupted deployment. Correctness comes from device observations; a generated configuration is not proof that the network works.
Explore the code.
Build your next lab.
Network Lab Factory · by Carlos Alvarado