Notices

I don't use it either

What don't you use?

Enable/disable Injection driver buttons on the Monitor Tab of fAircrack; as far as I know the bleeding edge drivers have been part of Kernel Power since 46, I am running KP49 at the moment. Enable/disable is only for those people running the stock kernel.

Ok!
I followed this guide:
http://talk.maemo.org/showthread.php?t=68002
to enable monitor mode on N900, and Aircrack doesn't work if I don't enable those drivers.
As reguards fAircrack, I thought I had to enable them manually, too.
However, I click on enable injection and then enable monitor mode.

Enable injection loads the kernel modules for the bleeding edge wifi drivers as per your reference attached above; as I said before, it is not required for KP46 onwards, since they are part of the kernel already. Only required to do this in fAircrack if you have the stock kernel.

Pressing the Enable Monitor mode button in fAircrack essentially runs the following

So, in short, I don't need those drivers anymore?

I tried the commands:

ifconfig wlan0 down
iwconfig wlan0 mode monitor
ifconfig wlan0 up

and they work!

The commands I've always used:

airmon-ng stop ath0
airmon-ng start wlan0

don't seem to work, though.

EDIT: I have to use:
airmon-ng stop wlan0
airmon-ng start wlan0

and then use wlan0 as interface. I don't know why it creates the interface mon0, though.

Can't tell if you need them, since you haven't said what system you are running (stock or KP46+). fAircrack is working over the wlan0 interface. When you use airmon-ng to create the monitor interface instead of the ifconfig, iwconfig commands, you are creating the mon0 interface; hence fAircrack will not work (AFAIK, will look into this for a future release of fAircrack after the 0.46 release tomorrow). However, all your command line commands will work as long as you use mon0 for the interface.

I installed CSSU and this kernel:
http://maemo.org/packages/view/kernel-power-settings/

I'm talking about Aircrack from Xterminal. Well, if I use:
airmon-ng stop ath0
airmon-ng start wlan0
then, I use:
airodump-ng mon0
I can't see any network; if I use:
airodump-ng wlan0
it gives me an error... very long, I don't feel like writing it!
Ok, it starts with:
ioctl(SIOCSIWMODE) failed: Device or resource busy

I don't pretend to be an expert, though!

Can I ask you just a thing:
can you give a look at the commands I use, just to compare them to the ones used by fAircrack?
http://talk.maemo.org/showpost.php?p...postcount=1109

fAircrack 0.46 is going to be released?
It would be cool if Caffèlatte Attack could be implemented, just to see if it's faster than ARP Request Attack!

I may be totally wrong here, but AFAIK, they're not - due to increased power usage, while associated to AP and in standby mode. The fix for it would require osso-something, that is now waiting to get released in CSSU-Testing.

AFAIK (again), kernel-power just provide those drivers (for now, as later, they may be used by default), so they can be loaded without keeping them in some folder - isn't Cleven doing it this way?

Anyway, I've tested it a second ago, and while Monitor mode work without loading injection drivers, injection itself doesn't (surprise ). It starts, but doesn't inject anything, even when requirements (MAC from allowed list, ARP catched etc) are meet. No problem with Injection drivers under same conditions.

/Estel

// Edit

It may be worth to mention, that I've found how to finally *properly* fix a eons-old bug with icon. Just put faircrack.png it into '/usr/share/icons/hicolor/48x48/apps', then, in .desktop file, modify line icon=faircrack (*without* .png).

All the trick is that default icon path is '/usr/share/icons/hicolor/48x48/apps', so desktop looks there, unless specified otherwise (via icon path or something) in .desktop file.

This way, icon is displayed properly in desktop, but also in menu etc. I've fixed *every* program with wrong .desktop file and icon location on my device, this way.

One reminder - reboot is *mandatory* after this, or you'll be fooled by "no-icon". There are ways to restart things, but they don't work reliably (sometimes works, sometimes doesn't), so before You conclude "it doesn't work" - and switch it back to full icon path - reboot device.

/Estel

Estel,

Please run the following and report results with monitor mode enabled and injection disabled / enabled (using fAircrack):. Much appreciated, will do the same once I get back home and switch my AP to WEP again.