Rick:
Yes, by and large, that's all an AP is, a simple 5-minute
bridge. Leave it to Lucent to complicate things. :) Their access-points
also allow for something called "Wired Equivalent Privacy" which
essentially means you can 'name' your wireless-LAN at the access
point, and then only PCMCIA cards configured with the same 'LAN name'
get bridged. Or, for that matter, can even *detect* the access-point.
This is how my neighbors 802.11 LAN doesn't directly
interfere with my own -- he can't see my hosts and I can't see his.
I guess that's a feature of 802.11. :) Gawd help Bluetooth...
-Scott
PS: How's the PCMCIA thing shaking anyhow?
At 4:59 PM -0500 3/6/01, [EMAIL PROTECTED] wrote:
>On Tue, Mar 06, 2001 at 12:57:18PM -0800, Mike Noyes scribbled:
>> Scott C. Best, 2001-03-06 12:43 -0800
>> > Good question. My understanding up to now was that an AP
>> >was a layer-2 bridge from a wireless network into a wired LAN. At
>> >least, that's what my 802.11 AP does here in the garage.
>> WL-ACCESS is an Micro Access Point that performs as a transparent
>> Media Access Control (MAC) bridge between wired Local Area Networks,
>> and one or more WL-ACCESS wireless networks. Placed anywhere along
>> an Ethernet LAN, WL-ACCESS allows wireless station in their coverage
>> area to access transparently to the corporate network.
>
>So, a wireless access point is just a bridge, one of whose interfaces
>is a wireless interface.
>
>Why is there a _project_ for this? It's about five minutes of
>configuration (obviously, for somebody experienced) to make a
>Linux box with the apporpriate interfaces into a bridge.
>
>I hope that there's something I'm missing here, because if not,
>when I get my pcmcia support working, I'll make a
>pcmcia-ne2k -> WaveLan image just to bust their balls... ;)
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
