Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to run aircrack on an inspiron 600m with ipw2200.
I've installed the injection patch for the wireless driver. After installing Aircrack, I attempted to replace ipw2200.ko, with no success. I received an error "unknown symbol in module." A quick Google search shows a lot of other people on a variety of distros receiving the same error, but I've yet to find any information on a fix for it, or even a bug report.
I successfully installed the patch to enable packet injection for the driver. I was understanding that after I installed the patch for the wifi driver, before installing aircrack, that ifconfig would reveal a new interface, rtap0. No such luck - interface doesn't exist. The firmware is copied to the appropriate hotplug directory - I don't see any problem, but I can't get the patch to work.
Last edited by beer.h; 09-03-2007 at 09:06 PM.
Reason: make post more coherent
Problem solved. ID10T error. I was using the wrong release of the driver.
I've seen this posted on a lot of other forums, so if you get it, you might want to check that you're not using ipw2200-1.2.0 (stable release). You have to use 1.2.1 for this to work.
I've read in a magazine that the next Intel 2200 driver which will be based on mac80211 (the stack from devicescape) will do this by default. Are you talking of this driver (which is still in git repository, not in the mainstream) or the standard ipw2200 that exist since a long time?
I've read in a magazine that the next Intel 2200 driver which will be based on mac80211 (the stack from devicescape) will do this by default.
Are you saying it will inject without a patch? Is this the sourceforge driver?. I see the ipw2200-1.2.2 came out in mid July. Still going to have to alter the TX_POWER setting as this is a "MUST".
Last edited by Junior Hacker; 09-04-2007 at 06:18 AM.
What!? the tx_power can also be tweaked? I thought this was hardcoded in the blob to not be harmfull to human beings? That could be good if this is possible. Prepare some headache tablets!
Unfortunatly I don't have the magazine here, it's at my home in France and I'm now in Germany..
It's page 6 here: http://www.ed-diamond.com/feuille_lmag96/index.html
If you read french, in very small letters
And yes it's the mag from mid July so I think we are talking of the same thing. I'm surprised it's on sourceforge as it is now based on mac80211 while the others were on ieee80211
From memory you have to pull the git of the wireless maintainer in Linux. I think this driver will be integrated in the 2.6.23, so it could be already there in the 2.6.23-rc5.
Maybe there is more information in Wireless subforum on how to get the latest development tree.
Yup
I can read french. And yes, on the same page of that forum thread, Jo Shmo shows how to crank up the TX_POWER through the driver. I can crack WEP in three minutes off the street with an RXQ of 60 with the higher TX_POWER. One could always have two modules hanging around and switch them out if one is concerned about health.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.