At 12:01 AM 5/19/2002 -0700, Walter Biggart wrote: >In the end it turned out that while the wap11 does support AP Client Mode, it only >does so with other wap11's.
I think it's more a question of the access point, not the WAP11. I've connected a WAP11 in APC mode to a Cisco 350 AP. At first I could "see" the WAP11 but no devices connected to it. I had to add a $80 Linksys router/firewall that was set to clone the MAC address of the WAP11. In this way, the Cisco AP thought there was only one device. The firewall fooled it. Cisco wouldn't dare do anything to undercut their bridge market, so the AP only passes one MAC address from a remote client. Think about it: with WAP11 in APC mode to a WAP11 AP, both the WAP11/APC and the devices behind it are all ping-able over the network. The WAP11/AP is flexible enough to handle N devices behind the WAP11/APC. Other APs may not. Offhand I'd guess this is a slight deviation from the spec, but it's a nice one. Mind you, an otherwise 801.11b compliant Cisco AP will recognize that a Cisco "workgroup bridge" has associated and it will pass up to eight MAC addresses. So a Cisco AP can be flexible enough when it wants to be. - John -- general wireless list, a bawug thing <http://www.bawug.org/> [un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless
