Notices

some late answer - better late than never they say..

Your case should be working fine since version 1.12-2.
one limitation of "all common" (which comes from a limitation of aircrack) is that you cannot mix .cap and .ivs files.

Since Cleven doesn't provide a way to create ARP files or use them then it doesn't look relevant to me..

Mr Saturn I Have Also Asked Something Would Someone plzzz Help Me With Diss??????

I'll check that after getting back from current trip (so I'll get access to my router)


OK, I haven't been clear enough on this. I mean that, when You crack WEP password using package injection, You need ARP. If You can't craft one (using Cleven only, you can't obviously), the only way is to capture legit one from connected client, and re-send it (which is possible with Cleven - package injection option automatically listen fro ARP and inject it, when got at least one).

Now, when You got idle client connected to AP, it may take quite long time, until ARP packet is send - on situations, where proper power-saving is used, it may even never happen (until client start to actively use network). So, best way of getting legit ARP quickly, is to deauth client - it makes it automatically re-authenticate (and get out of power-saving mode, for a while), so ARP is send, and our rogue device capture and inject it.

Still, client aimed deauthentication is somehow hard to implement in Cleven, if I understand You correctly. Ho ever, in most cases, AP-targeted deauthentication works well (AP just deauth all connected clients). AFAIK, it is possible to implement it without much hassle (latest fAircrack got this, while it - just like Cleven - can't implement client-targeted deauth). So, it would be great, to have a nice little button in Cleven interface, to do just that - AP aimed deauthentication

---

If I remember correctly, some pages ago You've said, that You thought, that client MAC is always needed to send deauth packet, and I answered that aircrack can be used also without client MAC specified + I provided link to aircrack FAQ page, where was stated that this method is "less efficient", than client-aimed deauth. Still, AP-only targeted deauth seems to work in practice - I've yet to see a case, where I would be unable to do so.

Also, if I remember correctly, You acknowledged that and promised to include AP deauth option but, I may have messed something (mixed memories from different discussions, or whatsnot). So, in any case, glad to be of any help.

/Estel

@saturn....

could you update cleven so its compatible with KP49???
since pali upload KP49 to repository recently anyone who use cleven with KP49 will got warning that KP49 is not a compatible driver for cleven....
although the cleven still works (i still can crack my router) using KP49 the warning is really annoying every time we started cleven & when we configure the driver...

Even better, could You include option to disable this check on every startup? I recently found, that I'm using fAircrack more often than cleven, due to long startup time (due to unnecessary checks on every startup, I suppose - on first startup or on demand would be sufficient).

/Estel

Hi
Have just updated to the new cssu and power user kernal.
Cleven now gives warning
"The sytem did not find a known compatible kernal version for the injection drivers"
Is it possable to add the new kernal version to cleven?

Hi, please report if working with new power kernel the output of:

Hi, yes
2.6.28.10-power 49

please copy/paste output. Is there really a space before 49?

2.6.28.10-power49
NO space.