Skip to main content

Proving "It's not the Wi-Fi network"

 

We’ve all been there – or at least most of us have, anyway.  The Wi-Fi network appears to be misbehaving and users are frustrated.

 

Your users will be working for several hours, and then, it looks to them as if someone shut the entire WLAN off.  Their workstation’s Wi-Fi icon, when hovered, states “no Wi-Fi connections are available”.

 

Now comes the fun part – well, to me it’s fun, anyway.  Let’s start out with what the normal operation of the WLAN client looks like.  This particular client is stationary.  It’s a laptop that is used like a stationary desktop, and is cabled to the desk via lock and key.  I wanted to clarify that because you won’t see any roaming in this packet capture, and you shouldn’t see any.

 

Since the client is associated to an AP on channel 36, I set my protocol analyzer to only look at that channel, and then set a filter to only look at the client adapter.  This makes is a lot easier to what’s going on.  I will use this as my baseline, since I want to know what it looks like when everything is working normally.  Here’s normal for this client:

 

Encrypted data from AP to client

Client Request to Send to the AP

AP responds with Clear to Send

Client sends data

AP acknowledges data with ACK packet

 

 

Now we will fast forward a few hours.  The user called you and told you “The Wi-Fi is down”.  Or is it?  To them, it is!

 

We start our same packet capture as before – same filter, same channel.

 

Now the picture is very clear.  The Client doesn’t see the beacon of the AP’s BSSID because it is sending probe request to ff:ff:ff:ff:ff:ff and we are seeing the unicast probe responses from the APs (only on channel 36 because of the filter) to the client.  I believe the client should send unicast probe request to the AP.

 

The c lient does not appear to see the beacon of the APs, and starts sending out probe requests.  The APs respond, but the client does not appear to see the probe response.  Almost as if they WLAN client has gone deaf.

 

  

Thankfully, the “quick fix” is to turn the WLAN adapter off and then back on.  Long-term fix will most likely entail downloading and installing new WLAN client drivers.

 

 

 

 

Comments

Popular posts from this blog

Build your own Ekahau ePerf & Speedtest.mini server!

One a recent forklift project, we decided to replace our aging 802.11a/g hardware and deploy new 802.11ac WLAN gear.   We designed the building with Ekahau’s ESS - our default WLAN survey and design tool.  After designing the WLAN to meet our healthcare requirement (in this case, Aeroscout tags, Vocera badges, 5GHz Voice and data) we installed the gear and then validated the WLAN.   For this initial 802.11ac deployment, we decided to do both passive and throughput validations.  With throughput surveys, we measure actual data, such as packet loss and jitter.   On a side note - for some time now, we have said to ourselves, “I wish we had a portable Ookla Speedtest server”.   Spoiler alert!   We needed a throughput server that would be both simple to use and portable.  After talking with our Ekahau team, we decided to use the Odroid C2, and configure it for two purposes.  (It turns out that Ekahau has done the homewor...

Easy way to mount a Cisco 3602 or 3702 to the wall with off the shelf materials

Here is an option on how to Cisco AIR-CAP3602I-A-K9 access point to a wall from materials you can easily purchase from Home Depot.  (ie, I have done all the homework already)  All for under six dollars.  Check out last screen capture for the receipt. The access point was designed to be ceiling mounted in carpeted office environments, ten feet above the finished floor.  That said, there are areas that we to provide Wi-Fi coverage to that do not fit the above mentioned description – such as manufacturing, warehouses and older buildings. In these cases, we have nowhere to mount the access point.  Ceilings may be 30 feet, which is not where we want to install the AP.  In these cases we need to install the AP on a wall, approximately ten feet above the floor.  The AP does not come with a wall mount bracket that will mount it parallel to the floor, so I have come up with an off-the-shelf solution from Home Depot. The two things from the hardware sectio...

How to add AP licenses to a Cisco 5508 WLAN controller

How to add AP licenses to a Cisco WLAN controller. I recently had to do this and I must say if I had the link (below) when I first started out, life would have been much easier. You should have a PAK from Cisco when you purchased your adder license.   Go to  https://tools.cisco.com/SWIFT/LicensingUI/Home  and register it with the controller.         In this case, the PAK is 3681J1B047A.   You are going to need the serial number of your controller in order to generate the license for it.  I SSH into the controller and issue either "show udi" or "show license udi".  Just make sure you are communicating with the controller you intend to upgrade licenses on!  I am sure there are other ways to get this information, but this is how I do it.     After you enter in the information, you can view and download your licenses, or wait for them to arrive via email.  I downloaded the two license files in this exa...