On an OMAP-L137 embedded system running runs Arago Linux 2.6.37,
QCOM LR802UKN2 USB wireless adapter is installed.
Wireless support is provided by latest Ralink rt5370sta.ko driver rel 2.3.0.5,
according to the driver configuration rt2870sta.dat file; no iwconfig call are used to further configure the driver.
It is possible to connect the system in adhoc WEP: reciprocal pinging and TCP/IP sockets can be safely estabilished,
however when connection is lost, it is not possible to restore it.
The problem arises when the other network node issues disconnection/reconnection,
or when the system itself exits/returns radio coverage.
I tried WEP adhoc connection of the OMAP-L137 system to a WIN 7 STA
In my testing,
I can estabilish a functional WEP adhoc connection between:
an WIN 7 STA
and
the Linux STA supported by LR802UKN2, provided with rt5370sta.ko driver rel 2.3.0.5.
Functional means that the two STA can ping each other.
Please note that WEP connection request is commanded by the WIN 7 STA, through the WIN 7 wireless user interface
Here I repeat the relevant settings on my rt2870sta.dat file
AuthMode=OPEN
EncrypType=WEP
WPAPSK=
DefaultKeyID=1
Key1Type=1
Key1Str=12345
Key2Type=1
Key2Str=
Key3Type=1
Key3Str=
Key4Type=1
Key4Str=
The problem arises when the WIN 7 STA decides to disconnect from Linux STA.
When WIN 7 STA disconnects from Linux STA, all is O.K.:
reciprocal pings cease,
iwpriv ra0 connStatus returns “disconnected”.
When WIN 7 STA reconnects to Linux STA (of course with the very same password ),apparently all is O.K :
WIN 7 wireless user interface disappears
iwpriv ra0 connStatus still returns “connected”,
but after a substantial amount of time (20 s),
WIN 7 STA user interface appears again, indicating a possible error in security key matching….
After such substantial amount of time,
iwpriv ra0 connStatus changes from “Connected” to “Disconnected”.
and obviously reciprocal pinging is NOT resumed.
Please note that this not a WIN 7 STA error, because:
1)Restarting Linux STA (ifconfig ra0 down, then ifconfig ra0 192.168.3.72 up) solves the problem.
2) Restarting (disable, then enable) WIN 7 STA does not solve the problem.
3)The problem never occurs if testing is performed with two WIN 7 STA identically configured as in our WIN 7/ Linux testing
Any insight on the problem is welcome.
Thank you for your attention.