----- Original Message -----
From: "DonChicago" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, May 19, 2002 10:58 PM
Subject: Fw: [BAWUG] Wap11 AP Client Mode


>
>
>  I can verify that a BR340 (AKA BR500) in AP mode will allow multiple
WAP11
> AP Client mode MAC addresses to associate and pass traffic.

I should add that the MAC addresses of nodes on the WAP11 Ethernet LAN show
up in the Cisco BR340 AP Mode Association table with their local WAP11 MAC
address listed as their Parent nodes.


> > ----- Original Message -----
> > From: "Dan Lanciani" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Sunday, May 19, 2002 5:05 PM
> > Subject: Re: [BAWUG] Wap11 AP Client Mode
> >
> >
> > > John Foust <[EMAIL PROTECTED]> wrote:
> > >
> > > |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.
> > >
> > > Moreover, a BR340 (aka BR500) in AP mode will allow a WAP11 to
register
> > > all its client MAC addresses (at least as reported here).  An AP4800E
> > > running bit-for-bit the same firmware as the BR340 will not.  This
> > supports
> > > the theory that it is a deliberate block based on the bridge/AP
cookie.
> > >
> > > Someone on eBay was offering an APxxxx->BRxxx conversion, though he
did
> > not
> > > respond to my email asking if he had to change the hardware.  Assuming
> > this
> > > isn't just a scam to steal access points, the cat may be out of the
> bag...
> > >
> > > Dan Lanciani
> > > ddl@danlan.*com
> > > --
> > > general wireless list, a bawug thing <http://www.bawug.org/>
> > > [un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless
> >
>
> --
> general wireless list, a bawug thing <http://www.bawug.org/>
> [un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless

--
general wireless list, a bawug thing <http://www.bawug.org/>
[un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless

Reply via email to