Progress Summary
Team has made solid progress in setting up the test network in Packet Tracer, GNS3, and EVE-NG and started testing them against the requirements performance vectors.
Numerous issues with NS3 have required it to be dropped as a potential simulator as simply installing the program is a task that requires familiarity with the Linux terminal. Creating simulation scenarios requires in-depth knowledge of either C++ or Python to create simulation programs. There were issues getting Python-based scenarios to run at all. Because of this, testing NS3 further would be futile as it is impractical for an introductory networking class
Meeting Summary
The team met on 10/3 to go over the network plan to be used for testing and answer any questions about the network diagram and finalize who would be testing which simulators.
Key Events
Meeting on 10/3
Removal of NS3 as a candidate.
Member Activities
| Team Member | Major Tasks and Contributions | Workload (hours) |
|---|---|---|
| Justin McCannon | Compiled the NS3 source code to set up NS3 inside of an Ubuntu VM. Ran test files. Attempted to diagnose issue getting Python NS3 programs to launch. | 4 |
| Azm Uddin | Created a network topology on GNS3 and EVE-NG by using the cisco routers and switches. I also have configured the routers and switches to experiment with the project requirements. | 5 |
| Michael McInnis | I designed a basic network using Cisco Packet Tracer to test its functionality. We used Justin’s network plan as a reference. We also had a team meeting to discuss some of our findings. | 5 |
| Tiffany Nguyen | Began creating the network map Justin created last week in GNS3 and EVE-NG and also began experimenting around to determine requirement rankings, met with team on Monday | 5 |
| Nidhi Marsonia | Started building the network (Justin created the network plan for testing) on packet tracer to start evaluating the requirements. | 5 |
| Team Total | 24 |