I'm a delegate at Mobility Field Day 1!
★ THE BLOG ★ Ramblings on WiFi & stuff.
And another one is added the collective. Brocade to acquire Ruckus Wireless.
What's Primary and Secondary coverage? @DevinAkin wrote a blog about it.
FCC’s “nutrition labels” for broadband show speed, caps, and hidden fees Hmm, this is nice.
BOOKMARK THIS: How to manage WLANs on Windows from the command prompt. (Hint: it's netsh.)
Yeah, baby. One of May favorite "passive-aggressive" moves. 😈
Jake Snyder (@jsnyder81) wrote about the new Aruba AP-330. He seems to likes it.
EU court says no liability for no-password Wi-Fi is OK.👌 So, does this mean I can FINALLY get "wee-fee" when I'm in Europe? ¯\_(ツ)_/¯
It’s interesting that Aruba showed off “Clarity”, a new feature in its network management product AirWave, at Atmosphere. It’s interesting because it seems that lately there have been discussions about users blaming Wi-Fi for non-Wi-Fi related issues. I even blogged about it myself a few weeks back. And recently, Lee Badman posted the "soon to be famous cocktail napkin" he drew, to explain how wireless issues are more complicated then they appear. When users are connected to Wi-Fi, and they can't get to a webpage, or get an IP address, or that fancy captive portal you spent so much time customizing, the assumption is, “the Wi-Fi’s broke” ¯\_(ツ)_/¯. And the user is right… well, as far as they know, or care. And that’s where Clarity comes in.
What Clarity does is offer a window into what may be affecting the wireless user experiencing a problem. Clarity gives you a "heads up" letting you know there are issues with DHCP, or DNS queries, association, and authentication failures, by showing you an overview in its dashboard. Also, it gives you a "real-time" view of a client experience. Maybe it's taking too long for a client to associate to an AP, or the captive portal is not working, and you see DNS issues on the clarity dashboard - insight into what the REAL issue could be.
The fact is many help desk calls about wireless, are not wireless problems. The problems lay elsewhere in the infrastructure. Knowing where to start your troubleshooting helps you find resolution faster. Clarity is another tool in the help desk arsenal to help you get customer complaint resolution quicker, and more efficiently.
But, that's not all. Clarity also offers "Synthetic testing". Essentially, it allows you to simulate user activity on the WLAN, by using an access point as a client. You can then use that simulated client to run tests on the WLAN. If there are service affecting issues you have an opportunity to find them, and fix them, before you actual users arrive.
In a scenario we were shown you would go to the VisualRF tab and select the location you would like to perform the test. You then click on the AP you would like to act as your client and perform tests that simulate a client connecting to the WLAN. This test should expose issues with DHCP, DNS, captive portals, etc.
In theory, this should help predict, or rather, REVEAL problems that could occur once the real clients arrive onto the WLAN. This is what we as WLAN professionals do when we perform validation surveys after a deployment. You do perform validation surveys after all your deployments, right? It's a very appealing idea to be able to perform tests, maybe even SCHEDULE tests, on a regular basis, to head off those issues at the pass.
This is what I would love to see - a mobile app that can be installed on a client, that can perform those same tests. This would be an improvement to the already great option of testing with an AP or an AM (Air Monitor), but here's the difference - it's an ACTUAL client. It's not an AP, on a ceiling (where there are no clients), with super RX sensitivity. It could be a single-stream mobile device, or 3-stream MacBook Pro, and you can run test AS THE CLIENTS THEMSELVES WOULD. Run test in multiple clients at the same time - like you would see with REAL clients.
Well, Aruba is already working on that. It will initially be an Android only app, that will allow you to perform Clarity tests from the client itself. There is no word on a release date, but I am hopeful that it will come in a timely manner.
At introduction, Clarity will be available only for Aruba controller-based platforms.
Aruba Clarity with real-time monitoring will be available as part of the Airwave 8.2 release coming out in the next few weeks. Synthetic testing will soon follow.
This is a great talk, from a great guy, with a fantastic post of view.
"Integrity and the WLAN Profession” WLPC session by @samuel_clements is a “must watch” for any WLAN engineer.
Building networks where the sun don't shine. @bmroute doing some cool Wi-Fi stuff in the netherworld.
Is there a need for a Spectrum Policy within the Enterprise? by @JustDoWiFi. I can totally see the need for this especially in critical environments like hospitals.
Understanding OFDM CWNE #10 @RickMurphyWiTS posts on OFDM are great.
AiRISTA to acquire Ekahau RTLS Not the Wi-Fi side (whew), but still, big news.
Aruba Visio Stencils Updated stencils. And they work in OmniGraffle too!
COOL TOOL: Netool - Pocket sized network tester and analyzer First batch of beta units are coming out. Looks to be pretty nice.
Want to clean up India? Turn trash into free Wi-Fi Now THAT's an interesting concept. Socially engineered Wi-Fi.
NASA Releases New High-Resolution Earthrise Image Oh, my stars. 😳
Your Letters Helped Challenger Shuttle Engineer Shed 30 Years Of Guilt What a story. This poor guy was on the right side of history and no one knew.
Chuck Lukaszewski, from Aruba, talks at the Wireless LAN Professionals Conference about what's coming after 802.11ac. Well, it's a lot. So much about how we understand Wi-Fi to work is going to be turned on its head. Two-way MU-MIMO, infrastructure control/influence on clients, SMALLER channels, and more.
This is a must watch for anyone involved in wireless.
And here's a link to ALL the videos from WLPC. So many great sessions to watch.
Announcing the Ekahau Master Wi-Fi Certification Jussi from Ekahau just announced this at WLPC. Pretty excited about this new program!
SSID Overhead, Now There's an App for that! WLPC is just full of firsts! @RevolutionWiFi announced an app version of his SSID Overhead calculator built by @RAdzima. Great tool for determining if your SSID count is causing any appreciable effect on your WLAN. Also, great for proving to the customer that 10 SSIDs is not a good thing. 👍
Engineers achieve Wi-Fi at 10,000 times lower power This seems like a very interesting option for IoT. It's all just "in the lab" at the moment, but I see potential.
WiFi Channel Simulator by CWNE Rick Murphy This is a fantastic tool to visualize channels in 2.5/5Ghz. How many 80Mhz channels are available with, and without DFS? This will show you. Want to visualize for a customer why you shouldn't use overlapping channels (anything other that 1, 6, 11) in 2.4? This will show you. Luv!
Apple: an iPhone Backdoor Would Be Reused by China, Russia, and the US It's about what the Gov't is gonna ask for in the future. Oh, and EVERY OTHER COUNTRY as well.
802.11ah Emerges to Connect the Internet of Things Old things have become new. 900MHz is being positioned to be the savior of the IoT Apocalypse.
What do "your" WiFi clients support? CWNE #150, Mike Albino, has created an online database of wireless clients and their capabilities. In this post Mike shows various ways to get that data from probe requests. This is a great resource for anyone in Wi-Fi.
Asus lawsuit puts entire industry on notice over shoddy router security Uhg. This is why we can't have nice things. 😕
How Wireless Works CWNEs Rick Murphy and Devin Akin have a new site that offers resources on wireless. Also, online training to learn Wi-Fi in-depth. Looks great.
Airport Experiment Shows That People Recklessly Connect to Any Open WiFi Hotspot Personally, I ALWAYS use a VPN when on a public WLAN. Even an encrypted one. But, that's just me. ¯\_(ツ)_/¯
A tense prequel fully explores Back To The Future’s terrorist backstory Cuz, who doesn't wish Doc Brown was bad-to-bone?
Estimated reading time: 1 minute, 24 seconds. Contains 280 words
Well, it's that time of year again - Wireless LAN Professionals Conference (WLPC). This is the 3rd (U.S.) conference, and my 3rd as well. I look forward to this gathering of Wi-Fi geeks all year. I tell anyone who asks about learning wireless - if you can only go to ONE conference - this is the one.
My first WLPC was in 2014 in Austin, TX, and other than following WLAN pros on Twitter, I knew no one. I was overwhelmed at the knowledge, and people, I had access to. I got to listen in on conversations with people like Keith Parsons, GT Hill, Devin Akin, Andrew Von Nagy, Chuck Lukaszewski, and others.
I was a total fish out of water. I had just gotten my CWNA a few months before, but I really didn't know how far I would go. This conference was the impetus to start my blog, get involved in the WLAN community, and set a goal of achieving CWNE.
I was encouraged by all the people I met. People like me, who were relatively new to the wireless thing, and those who were well entrenched. Meeting other 'newbies' was encouraging, because I wasn't the only one who felt insecure in their Wi-Fi proficiency. Meeting the 'Pros' was encouraging because they were welcoming and open to sharing their knowledge and expertise with those of us that were new.
I encourage all WLPC first timers to get in the thick of it. Make an effort to get to know people, ask questions, listen in, and get involved. Push aside any timidity you may have, because the folks at WLPC are more than willing to welcome you in and share the knowledge.
When is Wi-Fi blocking justified? by Peter Thornycroft
How Levi’s Stadium Delivered 10 TB of Wi-Fi for the Super Bowl Webinar from Chuck "I'll NEVER be on the Twitter" Lukaszewski. Don't miss this one!
WLPC TenTALK by Martin Ericson: VoFi Phones and DFS Channels Things to consider.
This is how wi-fi actually works by @jimvajda Short and to the point.
802.11 Packet Capture Skillz To Pay The Bills by @WirelesssGuru
Engineering the wireless hospital: Mobility and connectivity Good read from the Wi-Fi Alliance.
The Hummingbird Effect: what does the wine press have to do with astronomy? Science + History = Kewl!
The IT Crowd: Moss Introduces Jen To The Internet Such a great show. This is one of my faves scenes
UPDATE: See the comment below by Andrew Von Nagy. It clarifies what I said about hidden SSIDs and DFS.
I'm a huge advocate of using DFS channels in most medium to large deployment scenarios. But, you should always validate your channel plan and make sure it doesn't cause issues with you WLAN. By that I mean verify that your devices actually do support DFS. It’s possible certain devices support DFS, but not ALL DFS channels. Checking manufacturer documentation, Google, or site like clients.mikealbano.com can help you figure that out.
Case in point: Hidden SSIDs. Most wireless folks recommend against using hidden SSIDs. It doesn't provide any security, requires more work to connect devices to, and some NIC drivers don't like hidden networks and won't, or have trouble, connecting to them.
There are practical reasons to hide an SSID - to avoid confusion between networks, or to simplify your network advertisement. But, security isn't one of them, the AP is still beaconing, clients probe more (so you're wasting airtime and announcing the SSID anyways), and the SSID is sent in plaintext in association requests anyway, so it's not that difficult to find them.
But, there's yet another reason to avoid hidden SSIDs - especially if you want to take advantage of DFS (Dynamic Frequency Selection) in your WLAN:
I'll admit to doing "little contemplation" on this. Fortunately, I don't run into hidden networks that much these days (thank goodness), but I've also spent little time considering the consequences of DFS and hidden networks. Using hidden networks on DFS channels can cause unforeseen connectivity issues.
Clients can't actively probe on DFS channels. Active Probing is when a client send a "Probe Request". Clients send probes on a channel to discover any potential APs. Since ACTIVE probing is not allowed on DFS channels, clients will do Passive Probes - which simply means they listen for beacons on a channel. Well, if they just happen to listen BETWEEN beacons, they’ll miss what they don’t see.
This also has implications for voice and roaming. If the clients can't probe for new APs then roaming times will be longer, and real-time data starts having issues. Many hospital deployments don't use DFS because of these issues.
Just food for thought. If you need frequency re-use (and these days who doesn't?) you'll need DFS. And DFS does not play well with hidden SSIDs. So, just stop hiding your SSIDs. Another thing you can do is mix your channel plan up so you don't have all DFS in an area. Always have non-DFS channel options available in case the device doesn’t have enough time to find the channel, or it doesn’t support it.
One final note, if roaming is important, you should be using 802.11r and devices that support it. And in conjunction with 11r use 11k/v to help speed up channel discovery. Of course, make sure your infrastructure and your devices support these features, and test them thoroughly to insure there are no compatibly issues when enabling them.
UPDATE: See the comment below by Andrew Von Nagy. It clarification hidden SSIDs and DFS.
Actually, that isn't correct. Clients can't initiate transmissions on DFS channels, which prohibits most of the benefits of probing... namely faster discovery of the APs operating on the channel. But hidden SSIDs have no impact on this. Once a client hears a beacon on the channel by a "master" device (that must conform to radar scanning regulations) then it is safe for a client to probe.
So the real issue is two fold with DFS and client scanning:
1) Longer initial AP discovery time due to waiting until it hears a beacon (102.4ms intervals) instead of probing immediately (discover within just one or a few ms), and
2) Longer scanning time when roaming, especially for latency sensitive applications such as voice.
Whether or not the beacon populates the SSID IE field is irrelevant.