|
Friday, April 12, 2002
|
|
|
Wireless networking is both my job and my hobby. I am especially interested in 802.11, which is like a wireless version of Ethernet.
By day, I'm a software engineer at AirWave Wireless. We offer software and tools for deploying, managing, and securing wireless networks. I really like the company, I believe in our product, and I get to play with wireless networks all day long. What could be better?
Outside of work, I do a lot with SfWireless. See pages related to CommunityNetworks.
Also see the WirelessFaq for some common questions about 802.11b.
For a complete list of pages in the wireless category, see CategoryWireless.
Why Authenticate?
by JasonLuther
CommunityNetworks are supposed to be free, right? So why would you need or want to authenticate users and devices that use the network?
These are the main reasons: accountability and liability, resource allocation, and network management.
Authentication brings up two other quesions: how much anonymity should be allowed, and how should authentication be implemented?
This is a quick summary of my personal views on the issue.
A simple, insecure hotspot:
8:50:56 AM
|
|
BAWUG - Outdoor Access Point Encloseure v1 - Matt Peterson http://www.bawug.org/howto/hacks/outdoor_intel2011/
- Overview
This hack allows me to store multiple access points in the open outdoors, while at the same time minimizing cable loss and protecting the expensive equipment. Inspiration and props from The Land Down Under to Geoff Watts and Ryan Armanasco. My hack goes a little bit further (Go US!, just kidding), continuing to use Power over Ethernet along with room for amplifier's, 1-wire weather station, and other goodies.
8:33:04 AM
|
|
|
|
© Copyright
2003
Jon Schull.
Last update:
11/10/03; 6:33:22 PM.
|
|
|