Many characteristics of client behavior can be learned through capturing the wireless communication between the Access Point and the wireless client. The actual Analysis of the packets is not covered in this blog entry.
The purpose of this demonstration is to show how to capture client traffic for troubleshooting analysis. WLAN IP is 100.29.29.215 We will be capturing packets from this device.ġ Wireshark monitoring notebook. I am still in the process of building my own setup where I can capture directly from a notebook, but in the meantime I utilized the Dell Powerconnect-W(Aruba OEM) equipment in my work lab and put together a small configuration consisting of a Campus AP, an Instant AP, local controller, capturing notebook running wireshark, and test client that can connect to my test SSIDs.ġ Aruba 7030 controller – Firmware version 6.4.3.6ġ Aruba 225 Access Point – IP 100.72.29.200, AP name is Shark_testġ Aruba 225 Instant Access Point – IP 100.72.29.24 AP name is Shark(I’m super original). My previous experience had been strictly in capturing wired traffic using wireshark, and had only briefly touched on 802.11 MAC headers in studying for my CWSP certification. Through the course and in the subsequent studying, I have learned the value of capturing 802.11 traffic. With that let’s get to my first topic: Recently I have had the privilege of taking the CWAP bootcamp at the Wireless LAN Professionals conference in Phoenix, taught by one of the CWAP PW0-270 Certification Guide Authors, Peter Mackenzie.
I welcome any feedback on improvement, and corrections on any mistakes made. As this is a journey, I welcome my fellow travelers and their input. The purpose of this blog is to document my experiences and lessons as I journey through my career as a Wireless Professional. Welcome to my first blog entry! This is going be a fun, and no doubt educational experience.
0 kommentar(er)
