Quick reality check

If writing code makes you break into a cold sweat you are not alone. This guide shows how to finish Lab 4 using only GUI tools and careful configuration. Same objectives, fewer keystrokes, and just enough nerd flair to keep graders impressed.

What you must do first

Read the objectives and study the topology like your grade depends on it. It does. The lab objectives tell you what to capture and what counts as evidence. Skipping this turns the exercise into a guessing game where the only winner is regret.

Scan the network diagram and task list

• Note which hosts need services and which paths traffic should take.
• Mark expected ports and protocols to filter during packet capture.
• Write a one line goal for each objective so you can prove it later.

Know the GUI like a friendly saboteur

Click around, but do it with a plan. Find configuration panels, the packet capture tool, and the log export buttons. GUI labs hide the same options a CLI would offer, just wrapped in dropdowns and toggles that pretend to be helpful.

Where the useful buttons live

• Configuration forms for services and interfaces.
• Live logs view and download or export links for evidence.
• Packet capture tool with export to pcap or save as file.

Configure services using the graphical interface

Populate form fields, pick values from dropdowns, flip toggles. Match the expected values from the lab instructions. If the lab wanted code it would say so, but most times the GUI gives the same knobs and buttons you need.

Practical tips

• Take a screenshot of each configured screen. Screenshots are cheap and persuasive.
• Use descriptive names for hosts and interfaces if the lab allows it so captures are easy to filter.
• If a setting is unclear check any inline help or the lab notes before guessing.

Capture and analyze traffic for proof points

Packet capture is the evidence that says you actually did something useful. Use the built in capture tool or export logs to a pcap and open it in your favorite analyzer.

Filtering like a pro

• Filter by host and port to remove noise from the capture.
• Apply timestamps and annotate packets that show the expected behavior.
• Export a trimmed pcap that only contains the flows you reference in your report.

Validate outcomes and assemble documentation

Validation is not happy luck. Reproduce the behavior for each objective and collect artifacts. A tidy bundle of screenshots logs and pcaps will save you from frantic explanations later.

What to include in your report

1. A short statement of the goal for each objective.
2. The actions you performed in the GUI with timestamps.
3. Key artifacts such as screenshots exported logs and filtered pcaps.
4. A brief explanation of observed results and why they meet the objective.

Final checklist before you submit

• Objectives read and annotated.
• Services configured in the GUI with screenshots.
• Relevant traffic captured and filtered.
• Validation steps reproduced and logged.
• Artifacts labeled and packaged neatly for the grader.

Follow this workflow and you will finish Lab 4 without writing code while still producing reliable evidence. If anything goes sideways you can always blame a mysterious UI bug and then fix it properly for extra credit.