Problems with Elsa Airlancer MC-11 Wifi card and Prism2 v2

[beltrixx]

Hi,

I've been trying to configure my wireless PCMCIA card (Elsa Airlancer MC-11, white edge connector) to use WPA + TKIP instead of WEP. According to the prism2v2 docs & manuals, which I've read thoroughly, this card should be compatible.

I've set up my DSL router to use WPA instead of WPA2 and TKIP instead of AES. Wifi signal is in b+g+n mode.

I've also set up the network device in Geneseis to use Devs:Networks/Prism2.device, Unit 0.
I've also set up other required things such as gateway (192.168.1.1), DNS (8.8.8.8 and 9.9.9.9), Netmask, IP etc

I can bring the network interface online and offline from within Genesis without problems, but when it comes to surf the web (i.e. http://aminet.net) it takes MINUTES to load the page. I don't think that's normal...

I have another PCMCIA network card, which is wired and works great (Fiberline FL-4680) so, although I know the connectivity matter may not be urgent, is driving me nuts ... (I wanted to get rid of all the wires).

I use Cardpatch, Cardreset from s-s file and load WirelessManager from within my User-Startup file.

I'm also attaching info from WirelessManager verbose option as well as my wireless.prefs file, may be they can help in finding the issue.


Kind regards,

Manel (beltrixx)

WirelessManager log :

Initializing interface 'prism2.device:0' conf 'ENV:Sys/Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Sys/Wireless.prefs' -> 'ENV:Sys/Wireless.prefs'
Reading configuration file 'ENV:Sys/Wireless.prefs'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=12):
     XX XX XX XX XX XX XX XX XX XX XX XX               JAZZTEL_xxxx    
PSK (ASCII passphrase) - hexdump_ascii(len=12): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='JAZZTEL_xxxx'
*** [wpa_sm_init] sm->pmksa=0x855860c ***
Own MAC address: 00:02:2d:3f:89:b8
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Added interface prism2.device:0
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
BSS: Start scan result update 1
New scan results available
Selecting BSS from priority group 0
Try to find WPA-enabled AP
Try to find non-WPA AP
No suitable network found
Setting scan request: 5 sec 0 usec
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
CTRL-EVENT-TERMINATING - signal 12 received
Removing interface prism2.device:0
No keys have been configured - skip key clearing
State: SCANNING -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout

Wireless.prefs :

network={
   ssid="JAZZTEL_xxx"
   psk="mypassword"
}

[Aardvark]

Just a guess, but perhaps the CPU is too busy with WPA encryption.

[beltrixx]

Originally Posted by Aardvark

Just a guess, but perhaps the CPU is too busy with WPA encryption.

Maybe, but according to prism2v2 documentation, my PCMCIA card supports h/w accelerated WPA encription. Having a look at these lines at the very beginning of my log file :



Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized


Make me think of a problem related directly to connectivity, authentication or similar. Prism2v2 documentation states that these PCMCIA adapters (Lucent / Agere firmware with white edge connectors) do not require firmware update but, on the contrary, they have a bug that disallows connection to certain modern routers... maybe this is my case, I don't know...


Thanks!