|
Written by Devin Akin
|
|
Tuesday, 04 December 2007 |
|
What good is a piece of networking equipment if the end user can't effeciently operate it? By 'operate' I mean install, correctly configure, and make on-going changes to. Hardware and software platforms in the WLAN industry have grown outrageously complex trying to meet the ever-growing demands of today's enterprise. Sometimes organizations buy equipment based solely on specs, and soon thereafter develop a serious case of buyer's remorse due to useability problems. Let's take the WLAN controller as an example. |
|
|
Written by Brett Creasy
|
|
Wednesday, 21 November 2007 |
|
What is the primary focus of a security professional? To protect something of value. And just as important, to explain why it needs protecting and how to go about doing so in a reasonable manner. It never fails that the lynch pin in any enforceable security policy is upper management, and making them understand the need to secure something and the reward of doing so. Try asking for a new security tool or even policy and you will likely get the ROI (Return On Investment) question - and it's a valid one too. So how do we go about doing so? |
|
|
Written by Devin Akin
|
|
Wednesday, 14 November 2007 |
|
1. The technology works.
With all of the vendors racing to be first, there's already a significant number of successful enterprise 802.11n deployments that prove that the technology actually works. This is, of course, on top of all of the certification testing completed by the Wi-Fi Alliance. I've tested a number of client adapters (Mini-PCIe, CardBus, USB, etc) and a small number of enterprise 802.11n APs. They work. |
|
|
Written by Devin Akin
|
|
Monday, 05 November 2007 |
|
I was just sitting here reflecting on 802.11 indoor mesh networks. The main problem with using mesh nodes (those APs that are connected to the network wirelessly) is the degraded throughput for client stations. When stations transmit to the mesh node, it has to repeat the traffic to its upstream mesh node. This continues until the traffic arrives at the mesh portal - an AP connected to the wired infrastruture. |
|
|
Written by Devin Akin
|
|
Wednesday, 31 October 2007 |
|
Trust me, there are many reasons to wait. I just thought I'd share a "quick 5" with you. I've been playing with 802.11n gear now for quite a while, and I deal with these issues quite a bit. I've been talking to quite a number of people about the "why / why not" of 802.11n implementation, and here are some that are pretty common. Enjoy. |
|
|
Written by Devin Akin
|
|
Tuesday, 16 October 2007 |
|
I'm sure that by now you've read the early 802.11n deployment documentation by various vendors. It's pretty much a consensus in these documents that there are a small set of ways to deploy an 802.11n upgrade to an 802.11a/g network. As a precursor, it is highly recommended by most vendors to use 5 GHz for the bulk of 802.11n deployments due to more available channels and bandwidth. |
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 Next > End >>
|
| Results 21 - 30 of 67 |
