To get started, I created VLAN 70 for the guest network and VLAN 80 for the video devices, making sure to name each one in a way that reflects their purpose. Naming VLANs helps keep everything organized, especially in a growing network like this.

I worked on the guest wireless network using a subnet of 192.168.70.0/25, which is optimized to handle up to 70 users efficiently without wasting IP addresses. To ensure seamless connectivity, I enabled DHCP, allowing devices to automatically receive IPs starting from 192.168.70.10. The SSID, "Guest_WiFi," was kept straightforward, and authentication was disabled to provide easy access for users, as outlined in the project requirements. This setup ensures scalability while maintaining simplicity for customer use.

For the video cameras, I used VLAN 80 and assigned them static IPs (192.168.80.10 and 192.168.80.11). This approach ensures they always retain the same IP, simplifying management and troubleshooting if needed. Segmenting the video traffic into VLAN 80 not only enhances security by isolating it from other networks but also ensures that the cameras have the necessary bandwidth for smooth operation. I verified that both cameras were securely connected to VLAN 80, confirming that the setup met the project requirements.

Segmentation was a critical aspect of this project, so I ensured that the guest and video networks were completely isolated. To verify this, I ran a series of ping tests. Guest devices were unable to communicate with the video network, and the cameras could only interact within their designated VLAN. These results confirmed that the segmentation worked as intended, providing an essential layer of security by preventing unauthorized access between networks. Additionally, segmentation helps optimize performance by ensuring network traffic stays confined to its intended VLAN, reducing unnecessary congestion and potential interference.

When setting up the subnets, I opted for a /25 mask for the guest network. This choice efficiently supports the current need of up to 70 users without wasting IP addresses while leaving some room for future growth. If the organization ever needs to accommodate more users, upgrading to a /24 subnet would be a seamless adjustment, allowing for up to 254 usable addresses. Although the DHCP lease time couldn’t be adjusted due to hardware limitations, the current configuration provides flexibility and scalability to adapt to evolving organizational needs.

After configuring the network, I performed several tests to ensure everything was working as intended.

• Ping Tests: I tested connectivity within VLANs (e.g., devices in VLAN 70 communicating with the wireless router) and verified segmentation by confirming that devices in different VLANs couldn't communicate.
• Device Functionality: I ensured that guest devices connected to the wireless network received IP addresses via DHCP, and cameras on VLAN 80 remained operational with their assigned static IPs. 

These tests confirmed that the network was secure, properly segmented, and performing as expected.

To ensure reproducibility and future scalability, I documented all configuration steps:

• Labeled each VLAN and device in the network diagram with corresponding IP addresses and roles.
• Captured screenshots of the VLAN table, router configurations, and ping tests to demonstrate compliance with the project requirements.

This documentation provides a clear reference for future troubleshooting or expansion of the network.