# systems · systems.sh
Networking Configuration
Network design and configuration tasks — subnetting, routing and the diagram to match.
Networking assignments are marked on the design reasoning as much as the working config — why this subnet mask, why VLANs here and not there. We show the subnetting work, comment the configs, and test everything in the simulator your course actually uses before it comes back to you.
What you get
- Subnetting worked out and shown, not just the final addresses
- Router and switch configs commented line by line
- Network diagram delivered alongside the config files
- Tested in the simulator your course uses — Packet Tracer, GNS3
- Security basics addressed where your brief expects them (ACLs, VLANs)
- A short write-up justifying the topology chosen
What to send first
- The lab sheet or brief, including the topology or architecture diagram
- The tools required (Packet Tracer, GNS3, AWS, Azure, Docker, GitHub Actions…)
- What evidence the marker wants — configs, screenshots, logs, a report
- Access details only if the brief requires your own account (never your university login)
How it runs
- 01
Send the spec
The brief, the rubric, any starter code and the versions your marker uses. A photo of the PDF is fine to begin with.
- 02
Scope and quote in writing
We read it properly, ask what is unclear, and confirm a fixed price and delivery date. A small advance confirms the order.
- 03
Build against the brief
Work is tracked task by task against the spec. Longer projects are split into milestones you can review as they land.
- 04
Tested handover
A repo that installs from a README, run against your test cases, with the write-up if your rubric asks for one.
- 05
Fixes and walkthrough
One round of fixes if a marker flags something, and a walkthrough of how it works so you can explain it.
Networking Configuration: common questions
Usually not — we build in our own environment and hand over the configuration, infrastructure code and evidence. If the brief insists on your account, we agree scoped access first. We never ask for your university login.
Yes. Evidence is captured as the work is done, labelled to match the brief's tasks, so the report and the submission line up.
It depends on the scope of the brief, the stack and the deadline. Send the spec on WhatsApp and you get a fixed price and delivery date in writing before any work starts — no hourly meter.
Turnaround depends on scope and is agreed with the quote. Tell us the real deadline, including the timezone, and we will say honestly whether it is workable before you commit.
// related
Often paired with networking configuration
Cybersecurity Reports
Vulnerability assessments and security reports, written to a professional standard.
systems.shCloud Deployment
Cloud deployment tasks on AWS, Azure or GCP, matched to your course's platform.
systems.shCI/CD Pipelines
CI/CD pipelines built to automate the build-test-deploy cycle your brief describes.
./send-brief
Send your topology.
Paste the networking configuration brief into WhatsApp — the message already names the service. Scope and price come back in writing.