Is it OK to associate 1 wireless bridge to 2 APs? (fwd)
Ed
plug at 0x1b.com
Tue Apr 14 11:13:23 MST 2009
regardless of your setup, you might want to see how it is done in the
OpenBSD world - if you want to set up a group of AP for a wider area
of wireless coverage, OpenBSD uses 'hostapd' and looking at it's man
page might give you some ideas about the problems you will have to
face with your setup.
http://www.openbsd.org/cgi-bin/man.cgi?query=hostapd&sektion=8&apropos=0&manpath=OpenBSD+Current&arch=i386
-best wishes
On Tue, Apr 14, 2009 at 10:32 AM, kitepilot at kitepilot.com
<kitepilot at kitepilot.com> wrote:
> Hello world:
> I'm resending this because I haven't seen it pop in the list and I had some
> server issues after we got hit by a BIG storm.
> Apologies if I sent it twice.
> ET
>
>
>
> ---------- Forwarded message ----------
> From: "kitepilot at kitepilot.com" <kitepilot at kitepilot.com>
> To: Main PLUG discussion list <plug-discuss at lists.plug.phoenix.az.us>
> Subject: Is it OK to associate 1 wireless bridge to 2 APs?
> Date: Mon, 13 Apr 2009 05:59:35 -0400
>
> Hello there:
> This question makes many assumptions, most of which I have no real knowledge
> of, so feel free to jump at any statement.
>
> I have a "tree" of APs all with the same ESSID. The reasons, valid or
> invalid, are beyond the scope of the question, but feel free to challenge
> the wisdom... :)
> Long story short, I'm ditching the whole idea, but that's another post.
>
> The issue is that I can see the MAC address of one client,
> registered in the arp table (associated) to 2 different APs SIMULTANEOUSLY.
>
> Now, the question is:
> Is it OK for a bridge to associate to 2 APs simultaneously?
> Is that reflecting other problems?
> Will it become a performance issue (loop)?
> THANKS!
> Enrique
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
More information about the PLUG-discuss
mailing list