Group: comp.os.linux.networking
From: inuY4sha@email.it
Date: Thursday, March 27, 2008 4:23 AM
Subject: Wireless tools

I'm having A LOT of troubles with wireless tools, wireless extensions
and uCLinux with kernel 2.4.19-uc1;
From what I see after I modprobe the module for setting up the
wireless interface, if I type iwconfig I get the following data:

# iwconfig
.....
Warning: Driver for device wlan0 has been compiled with an ancient
version
of Wireless Extension, while this program support version 11 and
later.
Some things may be broken...

wlan0 IEEE 802.11-DS Nickname:""
Access Point: 02:00:00:00:00:00 Bit Rate=281.147 Mb/s
Sensitivity=282145732/0
RTS thr=281147292 B Fragment thr=281147292 B
Power Management:on
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 invalid crypt:0 invalid misc:0

Now if I give the command "iwconfig wlan0 mode ad-hoc" for instance
the result is that the 1st byte of the Access Point address changes
from 02 to 01 (and back to 02 with "iwconfig wlan0 mode managed").
This led me to think that the structures defined in wireless
extensions were not aligned probably due to version mismatching.

So I checked the linux/include/linux/wireless.h in kernel source files
and I found the line

#define WIRELESS_EXT 13

while atm I'm crosscompiling iwtools using a "wireless.h" file with
the line

#define WIRELESS_EXT 17

The first thought.I had was to find a wireless_tools.13.tar.gz version
of the wirless tools... but... I couldn't find any!

So I tried to replace linux/include/linux/wireless.h (version 13) with
the version 17. As a result when trying to compile the kernel I got an
error in this file linux/include/net/iw_handler.h stating that the
structure iw_event was being redefined; to avoid the issue I
*commented* the following lines in the file iw_handler.h

317 struct iw_event
318 {
319 __u16 length; /* Lenght of this stuff */
320 __u16 event; /* Wireless IOCTL */
321 union iwreq_data header;/* IOCTL fixed payload */
322 char extra[0]; /* Optional IOCTL data */
323 };

and was able to compile the kernel and the modules.
Again, after having switched to the brand new kernel and modules, I
got the same problem ... so I wonder how can I solve it ?

Thanks for your time ! I hope you can help me with this, because I've
got no clues about the solution.

Cheers
RM

Safety Articles | Usenet Groups | Usenet News | Bluegrass