Negative. I use wlan driver selector applet, and everything is working fine. You just don't need to use "injection on" button if You loaded bleeding edge drivers already, but doing so doesn't hurt anyway.

Also, i would like to mention that some instructions from post 1 are incorrect. Yea, i know that this were mentioned many times before, but not in "concluded" form, so i post this here, to avoid another 213424 posts about injection not working:

1. Fake authentication doesn't create ARP. It creates ACK, but that doesn't help You. If You used "injection" (or manually aireplay-ng) and captured ARP, then You re-send it with MAC set to same as client, from whom You captured ARP, access point will accept them.

2. AFAIK the only real usage of fake auth on fAircrack (considering options that are possible now using GUI) is to check if access point got MAC filtering. It won't generate any ARP to replay - as stated in point 1 - at best it can make collecting IV's little easier (on some routers), but I'm not 100% sure about that. But, they're not skyrocketing, by any means.

3. On most situations, ARP is generated only, when new client authenticate to router by "legal" way (no fake auth), So, only possible solution to generate ARP on demand (to re-inject it) is just like with WPA handshake - force client to deauth. I've tested it countless times, with every possible configuration, and only deauthenticating client, while already running aireplay-ng (we're talking about using fAircrack GUI), generate ARP and start re-injecting it. Without that, You must wait quietly until someone connect to given router. Keep in mind, that powersaving idle features of wlan cards != deauthentication. Such a machine is still connected and authenticated, but traffic is suspended to almost 0. Same apply for our precious IVs

As for now, deauthentication doesn't want to work in fAircrack, so You must google correct syntax to use it from terminal No big deal thought.

---

Correct me if I'm wrong, but aireplay-ng activated via fAircrack work only in real time, i.e. all ARP's captured are lost when we close injection window? It would be great to add possibility to store them for future. It's little annoying, if You have to run everything from terminal, if You want to catch ARP and use it on hour better suiting Your needs.

Maybe they should be stored under "decrypt" tab, just as caps and keys, keeping them as default, then deleting on demand? Would be great if name contains not only AP ssid, but also MAC of client whom ARP was originated. Then, on "Access Point" page, we would have another button, called "injection via stored ARP".

What do You think, StefanL?

//Edit

As for repos and maintaining, I would love to help, but I'm as clueless as You Ho ever, it seems that I must start learning it - it's another situation in past few days, where I can't provide useful support, cause lack of knowledge about packaging for maemo

Mentalist Traceur gone much further and he's already maintaining aircrack-ng package - I'm 100% sure that he will be glad to help, thought.