[Prism54-devel] [Bug 92] Can't get on a not announced essid when the access point also announces a other essid

[bugzilla-daemon at mcgrof.com]

http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=92





------- Additional Comments From margitsw at t-online.de  2004-07-28 11:51 -------
To get up to date, here is E-Mail ro Robbert/Stefan :
Well, unfortunately I can't reproduce this.
Two AP's , Open SSID on Chan 6, Hidden on chan 11.
Config to OPEN :
eth1      Scan completed :
          Cell 01 - Address: 00:09:5B:D0:34:BC
                    ESSID:""
                    Mode:Master
                    Encryption key:off
                    Channel:11
                    Quality:33/0  Signal level:-67 dBm  Noise level:-100 dBm
          Cell 02 - Address: 00:09:5B:42:79:00
                    ESSID:"OPEN"
                    Mode:Master
                    Encryption key:off
                    Channel:6
                    Quality:26/0  Signal level:-74 dBm  Noise level:-100 dBm

Now a change to SSID HIDDEN :

eth1      Scan completed :
          Cell 01 - Address: 00:09:5B:D0:34:BC
                    ESSID:"HIDDEN"
                    Mode:Master
                    Encryption key:off
                    Channel:11
                    Quality:26/0  Signal level:-62 dBm  Noise level:-88 dBm
          Cell 02 - Address: 00:09:5B:42:79:00
                    ESSID:"OPEN"
                    Mode:Master
                    Encryption key:off
                    Channel:6
                    Quality:10/0  Signal level:-78 dBm  Noise level:-88 dBm

And the iwevents :
10:49:56.454438    eth1     New Access Point/Cell address:00:09:5B:42:79:00
10:55:41.491321    eth1     Set ESSID:"OPEN"
10:55:42.777971    eth1     Custom driver event:Authenticate request to 
00:09:5B:42:79:00  : ACCEPTED  (00)
10:55:42.780208    eth1     Custom driver event:Associate request to 
00:09:5B:42:79:00  : ACCEPTED  (00)
10:55:42.781516    eth1     New Access Point/Cell address:00:09:5B:42:79:00
10:56:46.054102    eth1     Set ESSID:"HIDDEN"
10:56:47.340594    eth1     Custom driver event:Authenticate request to 
00:09:5B:D0:34:BC  : ACCEPTED  (00)
10:56:47.344621    eth1     Custom driver event:Associate request to 
00:09:5B:D0:34:BC  : ACCEPTED  (00)
10:56:47.345238    eth1     New Access Point/Cell address:00:09:5B:D0:34:BC

I can freely change the SSID at will with no problem.
Next step would be configure WEP on the Open.
(Although I don't think that will change anything)
(Added 28/07 - No it doesn't)
Actually, reading the Cisco docs,  it seems that the secondary  ssid is not 
meant
for this purpose.  In the examples, they use it for bridges.
Also  in the examples, they show configs for this scenario that you have, 
however, they
do not use the secondary ssid.
Not sure, but I think the problem is maybe that the MAC address and therefore 
the BSSID
is the same. I can't see how we can influence this as the firmware determines 
how to react.
The driver just processes the events.

I'll leave the bug open in case anybody has a bright idea.

Margit



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.