Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

Wireless Basics

The smoke-filled room

Although I'd heard almost a year ago that a solution to WLAN security was imminent, months passed with only announcements of proprietary WLAN security systems from various vendors such as Funk, Symbol, Proxim and others. These systems incorporated pieces (and variations of pieces) of 802.11i, but were all aimed at enterprise-level WLANs and required authentication servers as part of their solutions. No one seemed to be interested in solving the residential / SOHO WLAN security problem.

As it turns out, the suspense of waiting for the IEEE to grind through its standards process was too much for some of the WLAN chip and equipment vendors to take, and they took matters into their own hands, forming a task group. From what I can gather, this group had the IEEE and Wi-Fi Alliance's blessing since the same companies participate in both organizations. The group gave the IEEE a way to let its standards-making process play out, while taking some of the heat off by getting a forward-compatible subset of the eventual 802.11i standard out into the market.

As reported by eWEEK and Computerworld a few months ago, the task group came up with something that was going to be called SSN (Safe Secure Networks, or Simple Secure Network... you decide!). But SSN looks like it was only going to address the WEP weakness part of the problem by blessing and deploying a protocol called TKIP (more on this shortly). This would still have left the authentication part of the WLAN security problem to be battled out in the market among the various proprietary solutions already being sold.

However somewhere in the past month or so, the authentication piece of the puzzle fell into place by taking the 802.1x and EAP pieces from the 802.11i toolbox, and adding them to TKIP. All that remained was to come up with a catchy(?) name that had the Wi-Fi branding in it... and voila, Wi-Fi Protected Access was born!

More Basics

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

Hi all.Decided to do a M&M config on my 87U. Was on 384.11_2 and flashed the same firmware back on. Followed the M&M instructions to the letter. Also ...
Having read through many reviews in Wifi Products, I noticed that most reviews are focused on coverage and throughput. However there isn't much covera...
I have an RT-AC86U router running the 384.11_2 firmware. I have it set to reboot every morning at 4 AM and I am experiencing failures to reboot. I’ve ...
I am trying to buy a used AC68U off Ebay. The front picture does not state "RT-AC68U Dual Band" next to the Asus logo. Instead it reads "AC1900 Dual B...
The Register reports that it is possible to crash network-facing Linux servers, PCs, smartphones and tablets, and gadgets, or slow down their network ...

Don't Miss These

  • 1
  • 2
  • 3