ieee80211 install problems
Attempting to install ieee80211. I get the following errors when issuing the make command....
Any help much appreciated. Jon. [root@localhost ieee80211-1.2.18]# make Checking in /lib/modules/2.6.24 for ieee80211 components... make -C /lib/modules/2.6.24/build M=/usr/src/ieee80211-1.2.18 modules make[1]: Entering directory `/usr/src/linux-2.6.24' CC [M] /usr/src/ieee80211-1.2.18/ieee80211_module.o /usr/src/ieee80211-1.2.18/ieee80211_module.c: In function ‘ieee80211_init’: /usr/src/ieee80211-1.2.18/ieee80211_module.c:268: error: ‘proc_net’ undeclared (first use in this function) /usr/src/ieee80211-1.2.18/ieee80211_module.c:268: error: (Each undeclared identifier is reported only once /usr/src/ieee80211-1.2.18/ieee80211_module.c:268: error: for each function it appears in.) /usr/src/ieee80211-1.2.18/ieee80211_module.c: In function ‘ieee80211_exit’: /usr/src/ieee80211-1.2.18/ieee80211_module.c:297: error: ‘proc_net’ undeclared (first use in this function) make[2]: *** [/usr/src/ieee80211-1.2.18/ieee80211_module.o] Error 1 make[1]: *** [_module_/usr/src/ieee80211-1.2.18] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.24' make: *** [modules] Error 2 |
Quote:
|
Hi Hangdog...
Well my ultimate goal is to get connected wirelessly with my IPW2200 card. Research so far has indicated that I have to install the ieee80211 subsystem, IPW2200 drivers, IPW2200 firmware, as well is removing old versions of the ieee80211 subsystem from the kernel. The above problem occurred whilst trying to "make" ieee80211. I'm running Fedora 8 with a 2.6.24 kernel. thanks... |
Ok, you almost certainly don't need to replace the existing ieee80211 subsystem to use the ipw2200 drivers. I wish Intel would remove that suggestion because ieee80211 hasn't been needed to be replaced for quite a bit.
Now with that said, the 2.6.24 kernel introduced a new wireless stack and to be honest I don't know if the new stack will work with the ipw2200 drivers. Just try installing the drivers and firmware with a stock kernel and see if that works. |
Quote:
|
The mac80211 is the new one. It is based on the code that Devicescape release a couple of years ago, so you may have seen it referred to as the devicescape stack or d80211.
|
Thanks for clearing this up! :) Lets see if I get my 3945ABC card running on my T60 soon...
|
That really shouldn't be much of a problem. The iwl3945 driver is in the kernel (2.6.24 and later) or if you have an earlier kernel, Intel puts out a patch to add the mac80211 stack. I've been using that approach without a problem for quite some time now.
|
Normally,
All I do for my ipw2200 is download the firmware version 3 and unpack it, copy all files ending in .fw to /lib/firmware and reboot. Then configure a connection. But Traditionally, if I want to use aircrack-ng and inject data, I would have to make some changes to the ipw2200 driver using the source code to enable packet injection. And it is usually advised to install the latest ieee802.ll source, during the 'make' step you are advised to remove the old. But, but! I was also told some time back that the ipw2200 drivers with the kernel would not need to be reconfigured to allow packet injection when the new mac802.11 is included. I tripped on this thread because I Googled the same error as I just upgraded to the 2.6.24-1 kernel with Debian Lenny and was going through the same steps to compile my own ipw2200 module. Now that someone pointed out the 2.6.24 kernel has the mac802.11, I'm gonna remove the kernel, re-install it to get the mac802.11 stuff back as it's already been removed, and try packet injection without doing anything. If it works, I'll leave the 802.11 source replacement out, but still compile my own ipw2200 module so I can jack up my transmission power up by 50%, (so I can crack wep encryption from half a block away). |
Quote:
And what exactly is the point of posting this kind of crap? You've been around long enough to know that LQ frowns on this kind of behavior and quite frankly, your post seems to be nothing more than bragging on your l33t h4X0r skills. |
Hangdog42
Knowledge is power. Some of the links I provide are from forums, easily accessible to/by anyone. This is where I got my knowledge on this topic of "needing to compile your own driver". Just thankful that a large number of society is kind enough to share their knowledge with me and the rest of the world, it is only fair that I return the favor. You want to go around painting a false picture of yourself, that's your choice. I make it very clear who I am, and that's my choice, so lump it. It takes all kinds to make this world go around, and if you can accept this reality, you'll fare better in the long run. And don't for once try and convince me or any other readers that you're different, because all you'll accomplish is to frame that portrait and put it on display and have more readers see behind the mask. Because every other reader is no different from you and I. We are all equal, and that's reality. OH! And my reasons for needing to crack wep from half a block away are very much legitimate. Unfortunately, I can't let the cat out of the bag, you'll have to speculate as to what the legitimate reason is. Your post tends to show me you have narrow vision, and you're not helping the OP with his/her question, rather, you're on a head hunt, and your testosterone level may be a little high. I am Jon's Liver I was able to circumvent that error you're getting by changing proc_net to init_net.proc_net wherever it occurs in the ieee80211_module.c file. But then ran into another error. I will submit the cure when I find it, if you find it first, submit it please. |
Quote:
|
Quote:
Quote:
Quote:
Quote:
|
Hangdog42
Quote:
In this country, retailers are asked to point out the dangers of using wireless networks to customers wishing to set one up. What packets are sent in all directions are up for grabs by anyone to do with as they please, legally. |
Quote:
Quote:
The FACT JACK is that this thread was originally about getting the ipw2200 driver working, and the thread was heading in that direction until you decided to start bragging about how l33t you are. Aircrack has nothing to do with getting the ipw2200 working. Noting. Nada. Zip. Bupkis. Get over yourself. |
All times are GMT -5. The time now is 10:18 PM. |