NET Blog Post Assessment 3 #1

In this lesson, our objective was to set up four laptops as users, and connect them to a router configured with pfsense to give all of the user laptops ipv4 and ipv6 addresses through a DHCP server. For us to setup the router and configure details, view client details etc, we needed to first create a UniFi account, then install the UniFi controller. After this, we booted up the pfsense server using 10.1.1.1 monitor to discover the routers local IP address. We ran into an issue that meant that we needed to reset the router. We then connected the roiter to the UniFi application which now displayed our router. Once this was completed, we then needed to update the firmware on the router as the current version was no longer supported by UniFi.

We ran a few test to see if the network was working as expected. We found that when Jordan tried to host a local server, other users could not view it as his firewall was blocking others from accessing his server. This also meant that we could not ping him in command prompt, even though he was on the network and had been given an ipv4 and ipv6 address. Once he disabled his firewall, we could then access the local server he had set up.

Below we can see the GUI for UniFi. On the left we can see our router that we are connected through. This has its own IP address, 10.1.1.9. On the right hand side, we have a list of clients on the network. This displays the name of the device, the type, and their ipv4 address. This was helpful for us to know what devices were connected to the network.

We ran into another issue where our LAN gateway was not configured correctly. In order to fix this issue, we needed to start by resetting our pfsense server. Once done, we needed to set the WAN port as a virtual port on the LAN. We then assigned DHCP as 10.1.1.1/24. In doing this, we managed to fix the issues we were having.

We ran a few more tests by connecting other devices to the network. When in our browser, we could access pfsense using 10.1.1.1. Through this, we could manage our server on the user machines. We found that there were some timeout connection issues depending on the browsers we were using. Firefox and chrome couldnt access 10.1.1.1, but we could access this through Microsoft Edge and Opra.