Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
Wireless Networking Hardware IT

802.11n Draft 2.0 Approved by Working Group 105

[Geeks Are Sexy] writes "Yes folks, the 802.11 Working Group has finally approved Draft 2.0 of the 802.11n spec, bringing us a step closer to its final form. 'With the positive vote from the 802.11n Working Group, the Wi-Fi Alliance will now begin officially certifying equipment as being compliant with Draft 2.0. That's an important step, as official Draft 2.0-compliant gear is guaranteed to be fully compatible with the final 802.11n standard.'"
This discussion has been archived. No new comments can be posted.

802.11n Draft 2.0 Approved by Working Group

Comments Filter:
  • by EvanED ( 569694 ) <[moc.liamg] [ta] [denave]> on Wednesday March 14, 2007 @04:13PM (#18353325)
    The people who work on these separate things are two different groups of people probably. The ones you want working on crypto stuff are your theoretical comp sci people and mathematicians. The ones you want working on the next 802.11 standard are your electrical engineers. It's not like one group is really diverting resources from the other.

    There are ways to reasonably secure your network, so people who know and care will still be able to take advantage of n when it's finalized.

    (This is over-simplified of course, but the overall point remains.)
  • by gad_zuki! ( 70830 ) on Wednesday March 14, 2007 @04:19PM (#18353429)
    >MORE packets per second on these networks,

    That makes no sense. WPA (using TKIP) changes keys every x packets, not x seconds. Usually under 10,000. WPA using AES/CCMP is even more difficult (if not impossible) to crack. WPA and WPA2 are just fine for wireless networks at 108mpbs. Hell, I'd be happy just to see people migrate away from WEP with this new release of products.

    The real vulnerability is still weak passwords. Wireless devices could do more to enforce better passwords and limit the amount of tries per minute per mac.
  • by gstoddart ( 321705 ) on Wednesday March 14, 2007 @04:25PM (#18353533) Homepage

    I think for most people using WiFi for Web surfing, G is plenty good enough. Most uplink speeds aren't anything close to what G offers anyway, and most people would be hard-pressed to flood a 54Mbps WiFi connection with Web traffic.

    But, people don't only use their networks for web traffic.

    I know quite a few people who have wireless media players integrated into their stereos. If you're streaming your A/V stuff over your network, or copying files about between your computers, bandwidth is *good*.

    I know when I'm backing up data from my work laptop to my FreeBSD file server over wireless, I sometimes wish it was faster.

    Once your wireless runs most of your lan, there are lots of reasons why more local bandwidth is a thing you may want. Some people might have more local traffic that internet traffic.

  • by mastershake_phd ( 1050150 ) on Wednesday March 14, 2007 @04:30PM (#18353629) Homepage
    It will take a couple of months at least for certified equipment to appear.

    For Draft Certified equipment to appear? Isn't that kind of an oxymoron?
  • by gad_zuki! ( 70830 ) on Wednesday March 14, 2007 @04:30PM (#18353641)
    Wireless gaming is quite the little nightmare isnt it?

    Here are some things you can do. The goal is getting the ping to the wireless router to be 1ms (or less) consistantly. 2-4ms consistantly is okay but past that lots of problems creep in.

    1. Some wireless managers do something stupid every 30 or 60 seconds that causes lost packets and delays. The MS XP SP2 manager is one of these. I use the linksys manager that came with my card now.

    2. Find a free channel in you area. Or the one with the least amount of interference on one of the three non overlapping channels.

    3. Set your router to be either G or B only (pick one). Doing both adds some time slicing silliness that hurts latency. You might want to try both and see which one works out best for you.

    4. Get as close as possible to the router.

    5. Get a better antenna/chipset. You need a stellar connection with no interference.

    I finally got my desktop to ping the router at 1ms consistantly with no lost packets. Well, once in a great while. Its so much more effort than running an unslightly wire and the wireless still 'feels' slow on BF2. Other games that arent as network demanding may fare better. Now I just run a wire when I want to play just to be extra safe and leave wireless for when im not gaming.

    Lastly, an n-connection may not be at all faster in terms of latency. You may still have time slicing problems, weird interference issues, extra CPU usage, etc. Its not really like ethernet at all. Depending on the manufacturer and what the air interface is like near you it could be worse (latency wise) than running an old B router with a decent antenna.
  • Re:N already? (Score:3, Informative)

    by MindStalker ( 22827 ) <> on Wednesday March 14, 2007 @04:56PM (#18353965) Journal
    well we could just change the 802.11 part to something else. No biggie. BTW h,i,j,k,l,m were all used at SOME point. Some more than others.

    (Don't remember all of them myself I know i was an improved encryption scheme, j was japanesse support k was extra node hopping, etc.. all or most of which is going into n)
  • by Anonymous Coward on Wednesday March 14, 2007 @05:41PM (#18354617)
    I have a Macbook Core 2 Duo with the 802.11N enabler and an Airport Extreme using the 5 GHz band. It works beautifully. Though now I'm curious if the Extreme will be final spec compliant...
  • Re:N already? (Score:3, Informative)

    by Wesley Felter ( 138342 ) <> on Wednesday March 14, 2007 @06:22PM (#18355135) Homepage
    After z comes aa, ab, etc. 802.3 (Ethernet) is up to ay already.
  • by evilviper ( 135110 ) on Thursday March 15, 2007 @12:14AM (#18358129) Journal

    It will take a couple of months at least for certified equipment to appear.

    It might take a couple months for the packaging and documentation to be updated. If you can't wait, looking at each vendor's websites for firmware updates and attached notes should quickly tell you which currently available gear is going to be 100% compatible, and full-speed with (future) certified 802.11n gear.

If I had only known, I would have been a locksmith. -- Albert Einstein