-
Notifications
You must be signed in to change notification settings - Fork 927
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors in wesside-ng with different drivers #306
Comments
Modified by misterx on 18 Aug 2007 17:42 UTC |
Comment by misterx on 18 Aug 2007 17:42 UTC I tried several revision of madwifi-ng, from 6ec2922 to aircrack-ng/aircrack-ng@ and I get the same result with all revision; madwifi-ng is not the cause of the problem. |
Comment by misterx on 18 Aug 2007 17:42 UTC There was something wrong with my install, I succeeded make it working with aircrack-ng/aircrack-ng@. I'm trying to find which revision of madwifi-ng caused this issue (and what change made this error happen). I'm quite close to it: 2f2ca10 works but 8e7d42f doesn't work anymore. |
Comment by misterx on 18 Aug 2007 17:42 UTC Here is the changeset: http://madwifi.org/changeset/2487 |
Comment by misterx on 18 Aug 2007 17:42 UTC Here is a quick and dirty patch before the real fix: http://patches.aircrack-ng.org/madwifi-ng-aircrack-ng/aircrack-ng@fc1c00846b12aa600af4dea860e607b6175ed108-dirty_wesside-ng_fix.patch |
Comment by misterx on 18 Aug 2007 17:42 UTC These 2 files were recorded with another computer.
There's no problem with both packets but there's something wrong in the way madwifi-ng reports packets sent (success or failure) or in wesside-ng. |
Comment by derdely on 18 Aug 2007 17:42 UTC Anyone help me with the patch, when i attempt to patch i get the following: madwifi-ng# patch -Np1 -i ../madwifi-ng-aircrack-ng/aircrack-ng@fc1c00846b12aa600af4dea860e607b6175ed108-dirty_wesside-ng_fix.patch
|
Comment by misterx on 18 Aug 2007 17:42 UTC derdely, such question is a patching problem, not related at all to this issue. So please use the forum or specify the path to if_ath.c (from where you are). |
Comment by Edster on 18 Aug 2007 17:42 UTC You also get this with patched Hostap (kernel 2.6.20 version) under Intel. |
Modified by misterx on 18 Aug 2007 17:42 UTC |
Comment by anonymous on 18 Aug 2007 17:42 UTC Hello, I had opened ticket 332 with this problem and that one is closed due to same as this ticket. Is the problem also solved for the alfa with rt73 .. |
Comment by misterx on 18 Aug 2007 17:42 UTC no, there's nothing for rt73 because we were not aware of the problem before you posted the ticket. |
Comment by hirte on 18 Aug 2007 17:42 UTC i think the problem is, that on recent madwifi-ng driver revisions the ack frames are broken, they aren't 10 but 8 byte in size (lacking the last 2 bytes of the receiver mac). so wesside never gets an ack. i think this is what causes this error. on ralink, i think you never get acks at all. it works with aircrack-ng/aircrack-ng@ tho, as i used it successfully without the errors mentioned above. could be the same issue, which is described in ticket #334. |
Comment by misterx on 18 Aug 2007 17:42 UTC |
Comment by zarren2 on 18 Aug 2007 17:42 UTC Managed to fix this with some mods to the madwifi drivers heres a link to the drivers |
Comment by anonymous on 18 Aug 2007 17:42 UTC Replying to zarren2@hotmail.co.uk:
Change the hxxp to http because I can't post URL's my card is a netgear wg511t |
Comment by Carlos on 18 Aug 2007 17:42 UTC got the same problem with rt61 and ipw2100 |
Comment by anonymous on 18 Aug 2007 17:42 UTC http://www.mediafire.com/?4xmdjmyn9xc New approach to the problem check out these drivers and let me know how you get on at my blog. hXXp://drgr33nsblog.blogspot.com/ |
Comment by anonymous on 18 Aug 2007 17:42 UTC Replying to anonymous:
Wrong driver sorry |
Comment by misterx on 18 Aug 2007 17:42 UTC It should be fixed with latest revision (trunk) of madwifi-ng. |
Comment by anonymous on 18 Aug 2007 17:42 UTC Replying to misterx:
kernel panic with latest revision ??? |
Comment by misterx on 18 Aug 2007 17:42 UTC I think we talked earlier on irc. I don't have any kernel panic (with a 2.6.18). You should report it to madwifi (but first, check if there's no existing ticket). |
Comment by zarren2 on 18 Aug 2007 17:42 UTC No it wasn't me you were talking to :D But I got them working it was my fault :D Cheers misterx |
Comment by trevelyn on 18 Aug 2007 17:42 UTC hi, i patched in directory and it patched okay with: |
Comment by misterx on 18 Aug 2007 17:42 UTC It's a bug tracker, not something to post like a forum. Please use a forum trevelyn. For everybody having issues with wesside-ng, try using madwifi-ng revision 2834, it should fix problems (or use airdriver-ng in 1.0-dev to install madwifi-ng). |
Comment by zarren2 on 18 Aug 2007 17:42 UTC lol @ trevelyn misterx Still get kernel panic with 2834.Been playin around for weeks ??? I havent tryed using airdriver-ng to install thanks I will try that later and if it still freezes I will post a new ticket. I'm using kernel 2.6.22.9 and I've tryed 2.6.20 on slackware 12. |
Comment by zarren2 on 18 Aug 2007 17:42 UTC Ok used airdriver-ng to install drivers and it works but takes ages and very temperamental with guessing ip. And getting [15:42:19] ERROR Max retransmists for (68 bytes):=db:eb:17 (rate=0) After looking into this more it looks like my card just freezes for about 20 seconds and then kicks in again? It patched the drivers but I cannot find where airdriver-ng puts them ??? I think Iwill stick to my drivers untill 0.9.3.4 is stable :D |
Comment by anonymous on 18 Aug 2007 17:42 UTC Sorry for the double posts airdriver installs 2438. |
Comment by misterx on 18 Aug 2007 17:42 UTC IT'S NOT A FORUM. |
Comment by anonymous on 18 Aug 2007 17:42 UTC I can appreciate that misterx! but I was replying to your suggested solutions that both didn't work for me. I will check to see if there is a open ticket over at the madwifi site and if not I will post one. |
Comment by anonymous on 18 Aug 2007 17:42 UTC anyone got a fix for rt73 yet? ERROR Max retransmists for (30 bytes): etc etc on alfa AWUS036s |
Comment by anonymous on 18 Aug 2007 17:42 UTC Same problems using the HostAP driver installed with airdriver-ng. Is a fix available for prism chipsets? |
Comment by dgc on 18 Aug 2007 17:42 UTC rt73, same problem so far, only tried on 1 BSSID, will keep testing |
Comment by anonymous on 18 Aug 2007 17:42 UTC Got same problem with zd1211rw |
Comment by anonymous on 18 Aug 2007 17:42 UTC Same problem with IPWRAW Intel 3945. Sometimes get kernel panic. My hardware+driver Injects perfectly if you might think that I didn't set up my gear correctly. |
Modified by misterx on 18 Aug 2007 17:42 UTC |
Comment by anonymous on 18 Aug 2007 17:42 UTC Since injection support was fixed in madwifi-ng trunk, everything works fine except wesside-ng. This is with a modified no-ack patch applied to aircrack-ng/aircrack-ng@. Quite a bit of "max retransmits" errors, however:
|
Comment by anonymous on 18 Aug 2007 17:42 UTC Ignore previous post, updated to aircrack-ng current trunk and issue disappeared. |
Comment by anonymous on 18 Aug 2007 17:42 UTC a mi tambien me da el error: "ERROR Max retransmists for (30 bytes)" no se mucho ingles y soy novato en linux pero necesito hacer que me funcione, mi tarjeta es wl-167G USB2.0 y uso el Back Track 3, porfavor necesito los pasos concretos para solucionar el fallo si es posible contestar en spanish. |
Comment by anonymous on 18 Aug 2007 17:42 UTC wesside sadly still not working: wesside-ng -i mon0 -v xx:xx:xx:9C:27:1E the ERROR output continues infinitely |
Modified by misterx on 18 Aug 2007 17:42 UTC |
Comment by Joe on 18 Aug 2007 17:42 UTC Not working here with AWUS036h either. ERROR max retransmists How do I fix this? I'm using BackTrack 4 final. The card seems to be working other than that.. and the injection test with aireplay works too. What gives? |
Reported by darkAudax on 18 Aug 2007 17:42 UTC
madwifi-ng svn aircrack-ng/aircrack-ng@ works correctly. When you try svn ee0555a, you get the following (also happen with rt73):
Other people on the IRC have reported the same symptom.
The text was updated successfully, but these errors were encountered: