mr-r3b00t/vulnerable_edge_trainer — explained in plain English
Analysis updated 2026-05-18
Run a lab where students configure gateway and proxy firewall rules on a realistic appliance.
Practice reviewing security event logs and tuning brute force protection thresholds.
Teach the difference between layer 3/4 gateway filtering and layer 7 proxy hostname filtering.
| mr-r3b00t/vulnerable_edge_trainer | alirezarezvani/promptor | ayushk58/crawlyx | |
|---|---|---|---|
| Stars | 9 | 9 | 9 |
| Language | Python | Python | Python |
| Last pushed | — | 2025-09-14 | — |
| Maintenance | — | Quiet | — |
| Setup difficulty | hard | easy | easy |
| Complexity | 4/5 | 2/5 | 2/5 |
| Audience | developer | pm founder | pm founder |
Figures from each repo's GitHub metadata at analysis time.
Full gateway-mode labs need Docker macvlan networking knowledge to give the appliance its own LAN address.
This project builds a practice gateway appliance for cybersecurity training labs. It is packaged as a Docker container that acts like a real network gateway or proxy device, so students can learn how to administer users, read logs, tune brute force defences, and lock down management access on something that behaves like a genuine piece of network hardware. It is meant for classrooms and labs only, not for production use. Once started with Docker Compose, the appliance can forward traffic for a whole network (acting as a default gateway with NAT) or run as a Squid forward proxy on port 3128 with full logging. Management happens through SSH on a published port, or through a web dashboard served over HTTPS with a self signed certificate. That dashboard lets an administrator create and edit user accounts, reset or change passwords, and review three kinds of logs: traffic flows through the gateway and proxy, every request made to the management interface itself, and a security event log covering logons, lockouts, and configuration changes. Logs can be paged through and exported as CSV files, with safeguards against spreadsheet formula injection built into the export. A rule engine lets students build ordered allow and deny rules based on protocol, ports, source and destination addresses, and hostnames, which get applied to both the gateway and the proxy paths. Addresses can be organized into reusable objects, groups, zones, and locations, and two starter locations covering private and public IP ranges are seeded automatically so common policies can be built with one click. There is also a packet capture feature using tcpdump, with limits on duration and file size, so captures can be downloaded and inspected afterward. Setup for a full network lab, where client machines route through the appliance, requires some Docker networking knowledge, such as configuring a macvlan network so the container gets its own address on the physical network. The README documents both this routed setup and a simpler Docker bridge based lab.
A Docker based training gateway and proxy appliance for practicing network admin, logging, and firewall rules in a lab.
Mainly Python. The stack also includes Python, Docker, Squid.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.