Slashdot Mirror
Intel's 802.11A Wireless: 5x Faster
Jaben writes: "Intel today released the first 802.11A wireless LAN devices which offer more than a fivefold increase in speed over the current 802.11B. as soon as more devices get onto the market this new technology will really make wireless a possible alternative instead of a neat item to play with."
It's not speed that makes wireless a toy. It's the cost! I don't consider an 11mbps wireless connection a "toy" and if it wasn't for the costs associated, I'd jump on right now.
Come on, seriously... alot of us are still on 10mbps connections to the Internet. 11mbps is far from a toy, and the speed bump will be nice but that's NOT the issue. 54mbps, 11mbps... who cares! what about the cost!?
i agree that 802.11a, at 54Mbps, is quite powerful, but i think the consumer would prefer an easier upgrade path: 802.11a requires entirely different hardware from 802.11 because it uses 5GHz instead of 2.5GHz. seeing as 99% of us cannot hose a 10Mbps ethernet for more than a few minutes at a time, i don't think the extra speed is going to justify to the consumer the cost of re-buying all the expensive hardware (new base station, new cards, new range-extender antennas, etc).
who knows, the market will decide. but i don't see it catching on in the next two years, at least.
"[T]his new technology will really make wireless a possible alternative instead of a neat item to play with."
Excuse me, but an 11 megabit wireless connection isn't quite worthless just yet. How many home users, even with DSL or cable modems, are pushing this limit? And how many offices are still using 10baseT LANs, or 10baseT hubs on even faster LANs? To all these users, 802.11b is still 10% overkill. Will 400% overkill make us any happier or more productive?
Plus, 802.11a is much more power-hungry, making it a decidedly unattractive choice for wireless PDAs. What say ye?
Slashdot needs a fact checker.
IPSec. Why waste your time with anything else? I really want a guide for getting Linux with FreeSwan to talk to FreeBSDs IPSec (using racoon?). There are a number of guides to getting IPSec working on Windows 2000, FreeBSD, OpenBSD, etc... Here are a few links:
How to setup IPsec interoperable for Linux, OpenBSD and PGPNet
Replacing WEP With IPsec
Why does IPSec with Linux seem like such a hack? FreeSwan is pretty annoying - why don't they just get IPSec into the kernel and go from there? Instead there appears to be a megapatch. It just makes me nervous. It's probably ok but man... Also, while I'm bitching, IPSec is a bit of a pain - or at least the implementations are. It doesn't need to be this complicated.
Unless you happen to be some kind of alien (or corporate) super-genius, you can't just take a 5 GHz antenna, slap it onto a 2.4 GHz transmitter, repackage it, and call it 802.11a.
First off, the componants for a 5GHz transmitter need to be (and are) smaller than the componants for a 2.4GHz system. This is why 2.4GHz phones and 802.11b cards have effective antennas within such a small form factor, and this is also why 11a cards have greater range. The antenna that can be fit into a Type II or CF slot would provide approx. a 10 dB gain (or double the effective radiated power) of the 2.4 antenna. (Besides that, a 5 GHz signal can be sent from a 2.4 GHz antenna with a little shrinking for that gain.)
The reason the transmitter is smaller is that the signal is much more easily affected by the environment, and by shrinking the distances between componants (and the componants themselves) one reduces that possibility.
In addition, the hardware has to be capable of handling the increased thoroughput. If you put a 100baseTX card on a Cat4 based network, it ain't gonna get you full bandwidth; likewise, a 10baseT on a Gigabit Ethernet connection can't do squat. 11a's guts are different from 11b's.
Also... about security in wireless: Let's make this clear. Any form of broadcast-based system, be it wired (like Ethernet) or wireless (802.11x), IS VULNERABLE TO EAVESDROPPING. Security has to be made application-level, like IPsec, SSL, SSH, and not hardware level. Especially if everyone has access to (sufficiently similar) hardware.
I used to be someone else. Now I'm someone better.
Real life is underrated.
It doesn't have to be secure (think IPsec), but I'm sure that everyone can see major benfits of making a technology that openly broadcasts data more secure.
I don't.
Picture this:
I have an incoming connection, a router, and a wireless network. I have several hosts on the wireless network. The router uses IPsec to communicate with the internal hosts, accepts only hosts with known keys, and ignores all other connections.
What is the advantage of having the wireless protocol itself have the overhead of a separate, redundant security layer? Why would you want the separate software complexity of configuring and tracking allowed-host lists for two protocol layers instead of one?
Down that path lies having every last protocol layer being complicated by trying to do a job which is handled satisfactorily by every other one. Far better to have a single layer which does security and Does It Right than to complicate 802.11 (or any other low-level protocol) by adding complex functionality which can be handled somewhere else.
Further, consider: If 802.11 has security built into it, then whenever that security is broken, 802.11 (and the hardware that uses it) needs to be changed; same for every other low-level layer. Much better to have only one higher-level layer to keep current/secure (and have to swap out the router and install new endpoint drivers in my theoretical example, but not have to replace the wireless hardware).