Security Basics mailing list archives
Re: Wireless range limiting
From: RB <aoz.syn () gmail com>
Date: Wed, 16 Apr 2008 22:53:09 -0600
On 4/16/08, Nico Darrow <ndarrow () airdefense net> wrote: Speak of the devil.
Here's my recommendation. If you want to limit the range of an AP, then just disable it's lower bitrates.
Interesting suggestion - reducing your effective range by increasing sensitivity to signal strength and interference doesn't necessarily operate on the principle of least astonishment, but for some it might be effective. For the non radio-heads out there, this approach won't reduce your visibility to clients, just their ability to associate with your AP from a distance.
slower B clients with longer transmit windows), but you also get out of reach of most script kiddies with their 802.11b prism2 chipset ;-P
You're at least one major revision behind (two if you consider Orinoco really was the last 11b darling, after Prism), the great majority of kiddie cards have been replaced with 11a/g Atheros chipsets.
Remember nothing beats a good Wireless IDS/IPS :-P
Says the guy that works for a wireless IDS/IPS company. How's that WEP 'cloaking' doing for you guys, you ever run that and your IPS bit through the ISM non-interference clause?
Current thread:
- Wireless range limiting Charles Hardin (Apr 16)
- RE: Wireless range limiting Nathan Sherlock (Apr 16)
- Re: Wireless range limiting Joshua Wright (Apr 16)
- RE: Wireless range limiting Nico Darrow (Apr 16)
- Re: Wireless range limiting RB (Apr 17)
- RE: Wireless range limiting Nico Darrow (Apr 16)
- Re: Wireless range limiting RB (Apr 16)
- Re: Wireless range limiting Kurt Buff (Apr 16)
- Re: Wireless range limiting Jeremy Bennett (Apr 16)
- RE: Wireless range limiting Oguz Tekeli (Apr 17)
- RE: Wireless range limiting Patterson, Michael (Apr 16)
- RE: Wireless range limiting Eggleston, Mark (Apr 16)