SME Manual Connection Issue

Tony59711

Other Parts Discussed in Thread: WL1271, OMAP3530

Hi,

I have problems re-connecting, when in "SME Manual" connection mode:

Scenario 1:
/ s a (waited 5 secs)
/ m d 1
/ c c Bambini1 (Connects successfully)
/ c c Bambini2 (Failed - required a reset of the target, for a new manual connection)

Trying to associate with SSID 'Bambini1'
OK
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with SSID 'Bambini1'
Authentication with 00:00:00:00:00:00 timed out.

Scenario 2:
/ s a (waited 5 secs)
/ m d 1
/ c c Bambini1 (Connects successfully)
/ c d
/ c c Bambini1 (Failed - required a reset of the target, for a new manual connection)

Trying to associate with SSID 'Bambini1'
OK
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with SSID 'Bambini1'
Authentication with 00:00:00:00:00:00 timed out.

I'm using:
HW: OMAP3530 w/ Wl1271
SW: "AM35x-OMAP35x-PSP-SDK-03.00.01.06" (Linux omap3evm 2.6.32 #1 Fri Oct 29 17:13:17 IST 2010 armv7l unknown) and "v3.00.01.06-WL6.1.6.0-Linux-x86-Install" (WiLink_Driver_6.1.0.0.144_NOCCX; Firmware version: Rev 6.1.0.0.335).

Thanks in advance,
Tony.

over 14 years ago

0 Salma Ali over 14 years ago

Intellectual 260 points

Hi Tony,

When you try to connect in SME Manual Mode, you first need to perform scan every time you want to connect to the AP. If you try to connect without scanning then it does not connect.

So the procedure is

/m d 1

/a s

/a t

/c c AP

**Refer the below logs for your reference.

Regards

Salma

\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
m
.../Management> connect moDe, Channel, Rate, Mode, Frag, rTs, Preamble, sLot, rAdio on/off, Info, siGnal, snr ratiO, tX_power_table, tx_power_dBm_div10, 802_11d_h/, beacoN/, adVanced/
d
Current mode = SME Manual
0 - SME Auto, 1 - SME Manual
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
c
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
d
OK
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
c
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
c brady
14
Trying to associate with SSID 'brady'
OK

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
d
OK
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
a
.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/
s
Application scan started
t
Application scan stopped
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
c
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
c
15
Trying to associate with SSID ''
OK
Associated with 00:25:9c:bb:01:cf
CTRL-EVENT-CONNECTED - ConnecTIWLAN: 4221.622638: ************ NEW CONNECTION ************
tion to 00:25:9c:bb:01:cf compleTIWLAN: 4221.630513: -- SSID = brady
ted (reauth) [id=15 id_str=]
TIWLAN: 4221.636831: -- BSSID = 0-25-9c-bb-1-cf
TIWLAN: 4221.643699: ****************************************
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
c
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
d
OK
c brady
16
Trying to associate with SSID 'brady'
OK

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
d
OK
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
a
.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/
s
Application scan started
t
Application scan stopped
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
c
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
c brady
17
Trying to associate with SSID 'brady'
OK
Associated with 00:25:9c:bb:01:cf
CTRL-EVENT-CONNECTED - ConnecTIWLAN: 4250.841827: ************ NEW CONNECTION ************
tion to 00:25:9c:bb:01:cf compleTIWLAN: 4250.849699: -- SSID = brady
ted (reauth) [id=17 id_str=]
TIWLAN: 4250.856015: -- BSSID = 0-25-9c-bb-1-cf
TIWLAN: 4250.862911: ****************************************

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/

0 Tony59711 over 14 years ago in reply to Salma Ali

Prodigy 120 points

Hi Salma,

It works! Thanks a lot for the support.

Regards,
Tony.

0 Tony59711 over 14 years ago in reply to Tony59711

Prodigy 120 points

Hi Salma,

I noticed that in the previous version (WiLink_Driver_6.1.3.01.5), it's possible to do connection/re-connection in "SME Manual mode" - scanning only at the beginning.

E.g.:
/ m d 1
/ a s (wait 5 secs)
/ a t
/ c b
/ c c AP1 (Connects successfully)
/ c c AP2 (Connects successfully)
/ c c AP1 (Connects successfully)

So the question is:
1) Is the above mentioned procedure a bug in "WiLink_Driver_6.1.3.01.5" - (therefore, the bahavior is changed in "WiLink_Driver_6.1.0.0.144_NOCCX")?
2) Put differently, how's "SME Manual" connection and re-connections (regardless of the Wilink version) expected to work?

See the logs - for details:

Fullscreen 1212.SME_Manual_Connection_Log.txt Download

Using: WiLink_Driver_6.1.3.01.5
---------------------------------

Connection established with supplicant
user_main, start
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit

\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
m
.../Management> connect moDe, Channel, Rate, Mode, Frag, rTs, Preamble, sLot, rAdio on/off, Info, siGnal, snr ratiO, tX_power_table, tx_power_dBm_div10, tx_poWer_level, 802_11d_h/, beacoN/, adVanced/
d 1
d
Current mode = SME Manual
0 - SME Auto, 1 - SME Manual
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
c
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
b
BssId List: Num=0
         MAC        Privacy Rssi  Mode    Channel    SSID

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
a
.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/
s
SNCN_START_APP_SCAN
prw673 to verify
General Scan Parameters driver side:

desired ssid len: 0
scan type: 1
band: 0
probe request number: 3
probe request rate: 0
 number of channels: 14
Channel number 1

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 1

Channel number 2

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 2

Channel number 3

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 3

Channel number 4

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 4

Channel number 5

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 5

Channel number 6

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 6

Channel number 7

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 7

Channel number 8

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 8

Channel number 9

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 9

Channel number 10

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 10

Channel number 11

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 11

Channel number 12

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 12

Channel number 13

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 13

Channel number 14

mac addr:  255 255 255 255 255 255
Erly termination event: 0
Number of ap frames: 0
Max dwell time: 60000
Min dwell time: 30000
Power: 205
Channel: 14

Enter scanCncn_Start1ShotScan function
Number of chl before 14
Number of chanles in the verify function: 14
Number of chl after 14
scan ok
Application scan started

.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/

.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/
t
Application scan stopped
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
c
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
b
BssId List: Num=7
         MAC        Privacy Rssi  Mode    Channel    SSID
 00.15.70.9f.d0.40     1    -65  Infra      1        M-Wireless
 00.14.6a.ef.f2.50     0    -59  Infra      6        KorsarzII
 f8.66.f2.fe.a6.60     1    -70  Infra      5        AMS-Poland-WAP
 00.15.70.9f.de.50     1    -66  Infra      6        M-Wireless
 00.15.70.d0.8c.2c     1    -82  Infra      6        M-Wireless
 00.3a.98.a7.1d.20     1    -62  Infra      8        AMS-Poland-WAP
 00.14.6a.ef.f2.00     0    -73  Infra     13        Korsarz

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
Authentication with 00:00:00:00:00:00 timed out.
Trying to associate with SSID 'korsarz_______Korsarz'

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
connect Korsarz
**Error: 'connect'**

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
connect Korsarz
9
Trying to associate with SSID 'Korsarz'
OK
Associated with 00:14:6a:ef:f2:0************ NEW CONNECTION ************
0
CTRL-EVENT-CONNECTED - Connec-- SSID  = Korsarz
tion to 00:14:6a:ef:f2:00 comple-- BSSID = 0-14-6a-ef-f2-0
ted (auth) [id=9 id_str=]
****************************************

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
connect KorsarzII
10
Trying to associate with SSID 'KorsarzII'
OK
Associated with 00:14:6a:ef:f2:5************ NEW CONNECTION ************
0
CTRL-EVENT-CONNECTED - Connec-- SSID  = KorsarzII
tion to 00:14:6a:ef:f2:50 comple-- BSSID = 0-14-6a-ef-f2-50
ted (reauth) [id=10 id_str=]
****************************************

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
connect Korsarz
11
Trying to associate with SSID 'Korsarz'
OK
Associated with 00:14:6a:ef:f2:0************ NEW CONNECTION ************
0
CTRL-EVENT-CONNECTED - Connec-- SSID  = Korsarz
tion to 00:14:6a:ef:f2:00 comple-- BSSID = 0-14-6a-ef-f2-0
ted (reauth) [id=11 id_str=]
****************************************

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
connect KorsarzII
12
Trying to associate with SSID 'KorsarzII'
OK
Associated with 00:14:6a:ef:f2:5************ NEW CONNECTION ************
0
CTRL-EVENT-CONNECTED - Connec-- SSID  = KorsarzII
tion to 00:14:6a:ef:f2:50 comple-- BSSID = 0-14-6a-ef-f2-50
ted (reauth) [id=12 id_str=]
****************************************

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
d
OK

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
connect Korsarz
13
Trying to associate with SSID 'Korsarz'
OK
Associated with 00:14:6a:ef:f2:0************ NEW CONNECTION ************
0
CTRL-EVENT-CONNECTED - Connec-- SSID  = Korsarz
tion to 00:14:6a:ef:f2:00 comple-- BSSID = 0-14-6a-ef-f2-0
ted (reauth) [id=13 id_str=]
****************************************

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
connect KorsarzII
14
Trying to associate with SSID 'KorsarzII'
OK
************ NEW CONNECTION ************
-- SSID  = KorsarzII
-- BSSID = 0-14-6a-ef-f2-50
****************************************
Associated with 00:14:6a:ef:f2:50
CTRL-EVENT-CONNECTED - Connection to 00:14:6a:ef:f2:50 completed (reauth) [id=14 id_str=]

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
connect Korsarz
15
Trying to associate with SSID 'Korsarz'
OK
Associated with 00:14:6a:ef:f2:0************ NEW CONNECTION ************
0
CTRL-EVENT-CONNECTED - Connec-- SSID  = Korsarz
tion to 00:14:6a:ef:f2:00 comple-- BSSID = 0-14-6a-ef-f2-0
ted (reauth) [id=15 id_str=]
****************************************

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
connect KorsarzII
16
Trying to associate with SSID 'KorsarzII'
OK
Associated with 00:14:6a:ef:f2:5************ NEW CONNECTION ************
0
CTRL-EVENT-CONNECTED - Connec-- SSID  = KorsarzII
tion to 00:14:6a:ef:f2:50 comple-- BSSID = 0-14-6a-ef-f2-50
ted (reauth) [id=16 id_str=]
****************************************

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/

Regards,
Tony.

0 Shlomi Itzhak over 14 years ago in reply to Tony59711

TI__Guru 64245 points

Hi Tony,

Let me elaborate first the difference between SME manual mode and automatic mode.

The steps at which connection with an AP is applied include the followings:

1.1. Supplicant configures the following connection parameters:

•-> BSS Type – infrastructure-BSS, IBSS or Any.

•-> Security setting – The desired Encryption algorithm and Authentication type.

•-> BSSID (Optional) – The BSSID of the desired AP.

•-> SSID – The SSID of the desired BSS.

2.2. Initiate scan for compatible BSS’s on a pre-defined channels and bands.

3.3. Select the best BSS (high signal level).

4.4. Perform 802.11 Authentication with the selected BSS (infrastructure mode).

5.5. Perform 802.11 Association with the selected BSS (infrastructure mode).

6.6. Perform 802.11i Authorization with the selected BSS if the security settings require it (infrastructure mode).

7.7. If the previous succeeded, the connection established. If failed, then select a different BSS.

8. If there’s no different BSS to select then scan for different BSS.

Scan and Select (steps 2, 3, 8) are performed either by the driver, in Auto mode, or by the application, in Manual modes.

The connection operation (steps 4-7) is done by the driver with cooperation of the Supplicant in step 6.

Thus, when operating in Manual mode, you have to scan and select youself.

In the procedure you described, SME mode is configured to Manual after you scan.

You should initiate a scan just after you configure to Manual.

Hope it is clearer now.

Shlomi

0 sinoj issac over 14 years ago in reply to Shlomi Itzhak

Expert 2800 points

Hi Shlomi,

I appreciate you giving detailed information on SME connection modes.

Is it possible to use 'Manual' connection mode to associate with an Access Point having hidden SSID? After configuring SME mode to 'Manual', i did a scan and tried to connect to hidden SSID. It didn't work. If it is in 'Auto mode, it connects to the SSID.

Please see the below logs;

root@omap3evm:~/Demos/wlan# ./wlan_cu
Connection established with supplicant
user_main, start
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistancet
a
.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/
s
Application scan started
t
Application scan stopped
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistancet
c
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
b
BssId List: Num=4
         MAC        Privacy Rssi Mode    Channel    SSID
00.26.cb.f3.ed.10     1    -45 Infra      8        Cisco
00.0e.38.62.63.f0     0    -54 Infra      8        ****
00.19.07.5a.c6.80     1    -60 Infra     11        ****
00.18.39.0e.e8.80     1    -45 Infra      6        Mistral_Wireless
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistancet
m
.../Management> connect moDe, Channel, Rate, Mode, Frag, rTs, Preamble, sLot, rAdio on/off, Info, siGnal, snr /
d
Current mode = SME Auto
0 - SME Auto, 1 - SME Manual
d 1
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistancet
a
.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/
s
Application scan started
t
Application scan stopped
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistancet
c
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
b
BssId List: Num=4
         MAC        Privacy Rssi Mode    Channel    SSID
00.26.cb.f3.ed.10     1    -45 Infra      8        Cisco
00.0e.38.62.63.f0     0    -59 Infra      8        ****
00.19.07.5a.c6.80     1    -60 Infra     11        ****
00.18.39.0e.e8.80     1    -45 Infra      6        Mistral_Wireless
c specialOne
2
Trying to associate with SSID 'specialOne'
OK
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistancet
m
.../Management> connect moDe, Channel, Rate, Mode, Frag, rTs, Preamble, sLot, rAdio on/off, Info, siGnal, snr /
d
Current mode = SME Manual
0 - SME Auto, 1 - SME Manual
d 0
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistancet
c
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
c specialOne
3
Trying to associate with SSID 'specialOne'
OK
Associated with 00:0e:38:62:63:f0
CTRL-EVENT-CONNECTED - ConnecTIWLAN: 3243.988136: ************ NEW CONNECTION ************
tion to 00:0e:38:62:63:f0 compleTIWLAN: 3243.994972: -- SSID = specialOne
ted (auth) [id=3 id_str=]
TIWLAN: 3244.001686: -- BSSID = 0-e-38-62-63-f0
TIWLAN: 3244.008339: ****************************************
..
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistancet
q

Thank you,

Sinoj

0 Shlomi Itzhak over 14 years ago in reply to sinoj issac

TI__Guru 64245 points

Hi Sinoj,

As far as i know, there is no limitation on hidden SSID while in manual mode.

It looks to me like a supplicant issue.

Is it possible for you to open a debug level at the supplicant and folow the command flow?

in addition, it is possible to open the debug at the WiLink driver level by recompiling with PRINTF_ROLLBACK definition in report.h file.

Could you also share what ap_scan is set to, in the wpa_supplicant.conf?

0 sinoj issac over 14 years ago in reply to Shlomi Itzhak

Expert 2800 points

Hi Shlomi,

I will try to enable debug and test it. Mean while, content of 'wpa_supplicant.txt' used earlier for testing is as follows;

ctrl_interface=/var/run/wpa_supplicant
update_config=1
ap_scan=1

Thanks,

Sinoj

0 Tony59711 over 14 years ago in reply to sinoj issac

Prodigy 120 points

Hi Shlomi,

Thanks for the answer.

You said "Thus, when operating in Manual mode, you have to scan and select youself". Agreed. However, "WiLink_Driver_6.1.0.0.144_NOCCX" (SME Manual mode) - requires manual scan (/ a s), each time a connection/re-connection is needed between an AP and STA, otherwise, it fails to connect. While "WiLink_Driver_6.1.3.01.5" (SME Manual mode) - requires manual scan, only once (at the beginning). Subsequent connections (still in SME Manual mode) connects successfully - without manual scan.

What is the reason for the change of SME Manual mode behavior from "WiLink_Driver_6.1.3.01.5" to "WiLink_Driver_6.1.0.0.144_NOCCX"?

Thanks,

Tony.

P.s.: See also question 1 above (the 4th post, counting from top to down).

0 Shlomi Itzhak over 14 years ago in reply to Tony59711

TI__Guru 64245 points

Hi Tony,

I don't believe it is related to the specific implementation of the driver.

When working in Manual, it depends whether the supplicant is is use or not.

If it is not in use, then the commands from the wlan_cu goes directly to the driver (via ioctl).

If it is in use, then the commands from the wlan_cu goes to the driver via the supplicant. In this case, a network block is created in the supplicant and the supplicant initiates an internal scan command to the driver. Maybe in the older version, the supplicant is used and thus an internal scan is applied.

Shlomi

Wi-Fi

Wi-Fi forum

SME Manual Connection Issue