Wireless LAN failure

I have a PCMCIA wireless LAN card NL-2511CD PLUS EXT2 which I cannot get
to connect to our LAN:

The following info I can provide:

uname -srm

QNX 6.3.0 x86pc

pin

Sock Func Type Flags PID Base Size IRQ
1 0 Network C—I-±-------- None 0x300 64 5
1 Empty ----MF---------- None
2 Empty ----MF---------- None
2 Empty ----MF---------- None

mount -T io-net -o verbose=2,key1=0x3F2D799A55,default_key=1

/lib/dll/devn-prism.so

ifconfig en1 10.1.0.10/9

sloginfo

Time Sev Major Minor Args
Feb 22 11:09:20 5 14 0 tcpip starting
Feb 22 11:09:20 3 14 0 Using pseudo random generator. See
“random” option
Feb 22 11:10:02 2 10 0 prism_write_rid(long preamble) failed: -1
Feb 22 11:10:02 5 10 0 PRISM (prism)
Feb 22 11:10:02 5 10 0 Vendor … 0x0
Feb 22 11:10:02 5 10 0 Device … 0x0
Feb 22 11:10:02 5 10 0 Revision … 0x0
Feb 22 11:10:02 5 10 0 I/O port base … 0x300
Feb 22 11:10:02 5 10 0 Interrupt … 0x5
Feb 22 11:10:02 5 10 0 MAC address … 00026f 353b06
Feb 22 11:10:02 5 10 0 PRIIdentity CompId 21 - Variant 0 -
MajVer 1 - MinVer 1
Feb 22 11:10:02 5 10 0 PRISupRange PriRole 0 - PriId 3 -
PriVariant 1 - PriBottom 4 - PriTop 4
Feb 22 11:10:02 5 10 0 STAIdentity CompId 31 - Variant 9 -
MajVer 1 - MinVer 4
Feb 22 11:10:02 5 10 0 STASupRange StaRole 0 - StaId 4 -
StaVariant 1 - StaBottom 1 - StaTop 9
Feb 22 11:10:02 2 10 0 devn-prism: Tx Disconnected Error.
Feb 22 11:10:03 2 10 0 devn-prism.so: Reset card
Feb 22 11:10:03 2 10 0 prism_write_rid(long preamble) failed: -1
Feb 22 11:10:03 5 10 0 prism_info_event(): RID_LINK_STATUS →
ASSOC_FAILED
Feb 22 11:10:04 5 10 0 prism_info_event(): RID_LINK_STATUS →
ASSOC_FAILED
Feb 22 11:10:06 5 10 0 prism_info_event(): RID_LINK_STATUS →
ASSOC_FAILED
Feb 22 11:10:07 5 10 0 prism_info_event(): RID_LINK_STATUS →
ASSOC_FAILED
Feb 22 11:10:09 5 10 0 prism_info_event(): RID_LINK_STATUS →
ASSOC_FAILED
Feb 22 11:10:10 5 10 0 prism_info_event(): RID_LINK_STATUS →
ASSOC_FAILED
Feb 22 11:10:12 5 10 0 prism_info_event(): RID_LINK_STATUS →
ASSOC_FAILED

nicinfo -r en1

PRISM (prism) 802.11 Wireless Ethernet Controller

Physical Node ID … 00026F 353B06
Current Physical Node ID … 00026F 353B06
Current Operation Rate … 11.00 Mb/s half-duplex
Active Interface Type … Unknown
Maximum Transmittable data Unit … 1514
Maximum Receivable data Unit … 1514
Hardware Interrupt … 0x5
I/O Aperture … 0x300 - 0x33f
Promiscuous Mode … Off
Multicast Support … Enabled

Station Name … DCAM
Network Name (SSID) … non-spec
Channel: … 11
BSS Type … BSS

Packets Transmitted OK … 1
Bytes Transmitted OK … 42

Packets Received OK … 1
Bytes Received OK … 0

Transmits succeeded after retry … 0
CRC errors … 14

Setting verbose to 3 or 4, crashes io-net.

Perhaps somebody out there has a solution.

Francois

You haven’t specified an SSID on the command line, that is why you cannot
connect to your access point.

“Francois Joubert” <sommerfj@webmail.co.za> wrote in message
news:dthabd$p6a$1@inn.qnx.com

I have a PCMCIA wireless LAN card NL-2511CD PLUS EXT2 which I cannot get
to connect to our LAN:

The following info I can provide:

uname -srm

QNX 6.3.0 x86pc

pin

Sock Func Type Flags PID Base Size IRQ
1 0 Network C—I-±-------- None 0x300 64 5
1 Empty ----MF---------- None
2 Empty ----MF---------- None
2 Empty ----MF---------- None

mount -T io-net -o verbose=2,key1=0x3F2D799A55,default_key=1

/lib/dll/devn-prism.so

ifconfig en1 10.1.0.10/9

sloginfo

Time Sev Major Minor Args
Feb 22 11:09:20 5 14 0 tcpip starting
Feb 22 11:09:20 3 14 0 Using pseudo random generator. See
“random” option
Feb 22 11:10:02 2 10 0 prism_write_rid(long preamble) failed: -1
Feb 22 11:10:02 5 10 0 PRISM (prism)
Feb 22 11:10:02 5 10 0 Vendor … 0x0
Feb 22 11:10:02 5 10 0 Device … 0x0
Feb 22 11:10:02 5 10 0 Revision … 0x0
Feb 22 11:10:02 5 10 0 I/O port base … 0x300
Feb 22 11:10:02 5 10 0 Interrupt … 0x5
Feb 22 11:10:02 5 10 0 MAC address … 00026f 353b06
Feb 22 11:10:02 5 10 0 PRIIdentity CompId 21 - Variant 0 -
MajVer 1 - MinVer 1
Feb 22 11:10:02 5 10 0 PRISupRange PriRole 0 - PriId 3 -
PriVariant 1 - PriBottom 4 - PriTop 4
Feb 22 11:10:02 5 10 0 STAIdentity CompId 31 - Variant 9 -
MajVer 1 - MinVer 4
Feb 22 11:10:02 5 10 0 STASupRange StaRole 0 - StaId 4 -
StaVariant 1 - StaBottom 1 - StaTop 9
Feb 22 11:10:02 2 10 0 devn-prism: Tx Disconnected Error.
Feb 22 11:10:03 2 10 0 devn-prism.so: Reset card
Feb 22 11:10:03 2 10 0 prism_write_rid(long preamble) failed: -1
Feb 22 11:10:03 5 10 0 prism_info_event(): RID_LINK_STATUS -
ASSOC_FAILED
Feb 22 11:10:04 5 10 0 prism_info_event(): RID_LINK_STATUS -
ASSOC_FAILED
Feb 22 11:10:06 5 10 0 prism_info_event(): RID_LINK_STATUS -
ASSOC_FAILED
Feb 22 11:10:07 5 10 0 prism_info_event(): RID_LINK_STATUS -
ASSOC_FAILED
Feb 22 11:10:09 5 10 0 prism_info_event(): RID_LINK_STATUS -
ASSOC_FAILED
Feb 22 11:10:10 5 10 0 prism_info_event(): RID_LINK_STATUS -
ASSOC_FAILED
Feb 22 11:10:12 5 10 0 prism_info_event(): RID_LINK_STATUS -
ASSOC_FAILED

nicinfo -r en1

PRISM (prism) 802.11 Wireless Ethernet Controller

Physical Node ID … 00026F 353B06
Current Physical Node ID … 00026F 353B06
Current Operation Rate … 11.00 Mb/s half-duplex
Active Interface Type … Unknown
Maximum Transmittable data Unit … 1514
Maximum Receivable data Unit … 1514
Hardware Interrupt … 0x5
I/O Aperture … 0x300 - 0x33f
Promiscuous Mode … Off
Multicast Support … Enabled

Station Name … DCAM
Network Name (SSID) … non-spec
Channel: … 11
BSS Type … BSS

Packets Transmitted OK … 1
Bytes Transmitted OK … 42

Packets Received OK … 1
Bytes Received OK … 0

Transmits succeeded after retry … 0
CRC errors … 14

Setting verbose to 3 or 4, crashes io-net.

Perhaps somebody out there has a solution.

Francois

Hugh Brown wrote:

You haven’t specified an SSID on the command line, that is why you cannot
connect to your access point.

This probably where the problem lies, I cannot set the ssid, no matter
what I do. I can get an ad-hoc communication going, with the ssid on the
other computer set to “non-spec”, but this link is unreliable in the
vicinty of other wireless networks.

Is there a feature on QNX that scans for available wireless networks as
can be done on Windows and Linux computers?

Francois

The SSID in nicinfo only gets updated once the device associates with an
access point. Until then it will display “non-spec”. Have you tried setting
your access point to a different channel? The driver doesn’t scan the
channels, this is done by the firmware on the wireless card.

“Francois Joubert” <sommerfj@webmail.co.za> wrote in message
news:dtjfk7$ac0$1@inn.qnx.com

Hugh Brown wrote:
You haven’t specified an SSID on the command line, that is why you
cannot
connect to your access point.


This probably where the problem lies, I cannot set the ssid, no matter
what I do. I can get an ad-hoc communication going, with the ssid on the
other computer set to “non-spec”, but this link is unreliable in the
vicinty of other wireless networks.

Is there a feature on QNX that scans for available wireless networks as
can be done on Windows and Linux computers?

Francois

Hugh Brown wrote:

The SSID in nicinfo only gets updated once the device associates with an
access point. Until then it will display “non-spec”. Have you tried setting
your access point to a different channel? The driver doesn’t scan the
channels, this is done by the firmware on the wireless card.

If I do not specify a channel number, I notice from nicinfo that the

channel number changes anyway as (I assume) the card scans the channels.
If I specify a channel number, it also ignores my number.

Is the perhaps a signal strength indication available? Perhaps I have an
antenna problem.

Let me first verify the total hardware setup by loading Windows and
check out the results.

Francois

Problem resolved, a silly one! The access point does MAC filtering. I
just had to supply the MAC address of the card.

Francois