NETW360, Ben Brezinski
Hands on Lab
Microsoft Network Monitor Introduction and Wireless Frames
When we expanded frame 4 the signal strength was -60dbm, the data rate was 1mbps, and the SSID in the beacon frame was Amory. In frame 5, looking at the Hex Details, the BSSID for this access point was 00 15 E9 D1 48. The authentication status in frame 14 was successful. In frame 15, the Association Response status was in a successful state. When we tried to the Microsoft Network Monitor we were unable to pick up any management packets during our capture.
We were able to successfully ping 10.27.8.80 to verify we had access to the “managed” device. The batch file was set up with the 10.27.8.80 address and had commands to get information from that address. The name of the device was NPIF9460B and the status of it was “ready to print”. After we downloaded the MIB Browser and entered 10.27.8.80 into the address field, we were able to get the sysUpTime which was 830 hours 13 min and 2 sec.
Finding rogue access points
When using the command “netsh wlan show networks mode=bssid” in the command prompt we were able to identify 17 access points. Out of the 17 access points 11 were not part of the DeVry wireless network. Using the FindAccessPoints.BAT we were able to identify 18 access points and 12 of them were not part of the DeVry wireless network. Opening the FindAccessPoints.vbs in notepad we were able to see the script and the basis of the script worked around the command netsh wlan show networks mode=bssid. After we set up our Linksys as a rogue access point we had no problem finding it using the batch file. This would be very handy to use at your home network, if you lived in a place where there is many access points, because you could pick up any rogue access points that someone has set up to attempt to capture any of your information.
Here is our log file from our Linksys access...