Two SSID's with the same network names ...

[Michael Duffy]

Hi Brian,

Yes it is a network architecture problem, I will be changing (hiding)
the SSID's in the next few days and adding WEP and whatnot after I
have had a play around with them, but as I have just taken them out of
the box they both have a default SSID and both issue the same IP's
(Naturally running that out of the box config).

This presented me with the problem of being able to connect to an
individual AP as generally an SSID is how the AP is 'known' as you
mentioned.

Yes I could always just configure one at a time but I'm now more
interested in conflicting SSID's, and selecting the one I want instead
of the closest, than a quick configuration. :)

The AP's haven't been set up as bridges and don't have an ethernet
bridge between them so when you connect to them individually (by
turning one off or disconnecting an aerial etc) they act like two
separate networks, just with identical SSID's ...

Mike.

On Tue, 30 Nov 2004 08:55:55 -0400, Brian Lloyd
<brian at greenflashnetworks.com> wrote:
> 
> 
> 
> On Nov 30, 2004, at 8:39 AM, Michael Duffy wrote:
> 
> > Hello,
> >
> > I have two WLAN's operating on individual private networks with the
> > same SSID, unfortunately the driver will only select the hub with the
> > strongest signal. I can see multiple network name entries for the
> > SSID's in the "Network Name" dropdown box but when I select the second
> > entry it just re-connects me back to the first hub (My basestation ID
> > also reports the MAC address from the first basestation).
> 
> This is very strange.  Identical SSIDs implies that the two APs connect
> to the same network and are functionally interchangeable.  This does
> not sound like the case for you.  Why would you do this and not choose
> a different SSID?
> 
> > Is there any way to input the basestation MAC addr instead of the SSID
> > into the setup or to maybe restrict the channel to control which hub I
> > can connect to ?
> 
> Well, that is the purpose of the SSID.
> >
> > With the exception of this slight problem, the driver works
> > fantastically ...
> 
> Well, this does not sound like a driver problem but rather one of
> network architecture.
> 
> Brian Lloyd                     Green Flash Networks, Inc.
> President                       6501 Red Hook Plaza
> brian at greenflashnetworks.com    Suite 201
> +1.340.998.9447                 St. Thomas, VI 00802
> 
>