Wireless Networks Causing Headaches For Businesses
ElvaWSJ writes "Wi-Fi was supposed to reduce complications, not create new ones. But in many offices Wi-Fi has been a headache. Like all radio signals, Wi-Fi is subject to interference. Its low power — less than even a typical cellphone — means that walls and cabinets can significantly reduce signal strength. Wi-Fi also creates networks that are more open than wired ones, raising security issues. And Wi-Fi has caused problems for virtual private networks. Some VPNs require a lot of processing power. If a wireless access point — at home, at the office, or on the road — isn't robust enough, a user often gets bumped off the connection."
Duh?
Make sure there are some bloody data ports where they are useful. The gods know how many office conference rooms I have walked into where there are two power/data/phone outlets on the far ends of the room behind heavy credenzas, instead of in the middle of the room accessible from the table top. Otherwise just blanket the place with WiFi and suck it up.
Not really, if you are a business that is deploying wifi as a solution to allow laptop users to move around fine, however if it is cheap solution to installing hard wired cables to each desk then someone needs to be re-informed about the pitfalls.
Wifi should be a supplement for larger areas with changing configurations (meeting rooms, conference rooms, etc) not as a replacement for a typical wired setup. Unless you plan on constantly rearranging your cubes, there's no reason to do that. Also you should think of the two networks as being completely separate and treat the wireless network as a public access point (i.e. force VPN access to the wired portion of your network).
I see the problem coming in where people think it's a wired replacement.
------
"And may your days be long upon the earth."
News at 11.
:)
I used to do wireless mesh network algorythm development and we had (with 802.11b) acceptable, AES encrypted, coverage of a motor factory (think *lots* of wire and EM) with nodes running on 200mhz arm systems and 64mb of ram. No problems with VOIP either. You just need to do some (ok, expensive) system design and there's no reason why it wont work. In the demo system the nodes updated their routing tables using a ropey bash script even
Expecting that off the shelf gear can magically set itself up is the problem, not the protocol itself (which can be worked around in many interesting ways).
Think of the Children; Sleep with your Sister
gee i wonder why its crap ? 1) To keep the cost down. Even 'commercial-grade' access points use inexpensive components to help keep the costs down to the point that people can afford them. Compare the cost of ham radio -- and then consider if you would buy a WAP that had that amount tacked on the sale price.
2) Government regulation. Governments around the world regulate these 2.4 GHz-range frequencies and given the number of devices in the range, transmitter power is kept necessarily low by regulation.
3) To keep the equipment from interfering with other devices such as cellphones, 2.4Ghz-range walkie talkies, and countless other devices that use this frequency range. See #2.
My blog