Notices

lxp,

Thank you very much, I look forward to the response.

I should add that I did install Titan's power kernel to work with monitor mode, and so far I've seen no issues with the power kernel.

However, at times I have noticed that when I run Kismet I am unable to pick up any wireless networks... running 'ifconfig' shows wlan0 in promiscuous mode, but doesn't show any traffic flow. After closing Kismet I am unable to connect to any wireless networks also. I'm guessing this is an issue with the driver, I would say that 70% of the time Kismet works well.

How can I use Kismet to crack my WEP connection key?
It is MY OWN network that I want to use to test, I have just had trouble finding a good simple (novice friendly) guide that works on the N900.

Can anyone help?

It is intended that you couldn't connect to any wireless network while running Kismet because you couldn't put your wifi card into two different modes like monitor and managed at the same time (at least with the current wl1251 driver).

How did you close Kismet?
As I already have mentioned in this thread it wouldn't work if you close Kismet through the X button. Try to close it by Ctrl+C or even better through the menu.

1. You wouldn't want to do WEP cracking until packet injection is working for the wl1251 chip.
2. If you have troubles with YOUR WEP network, press the reset button on the ap and configure it for WPA
3. If you really want to do WEP cracking, go to a different platform e.g. a notebook with a decent wifi chip or external wifi card.
4. If you still want to go for WEP cracking on the N900 yet, use a software which is designed for it like aircrack-ng. But remember 1., so either you have a high traffic WEP network or you will have to capture pakets for a very very long time.
5. If you are really crazy you can also use Kismet for WEP cracking on the N900. There is an untested plugin out called kismet-ptw. I wouldn't recommend using this plugin, especially on the N900 as it will cause a huge system load and will drain your battery.

[QUOTE=lxp;662324]It is intended that you couldn't connect to any wireless network while running Kismet because you couldn't put your wifi card into two different modes like monitor and managed at the same time (at least with the current wl1251 driver).

lxp,

I understand that I should not be able to connect to any wireless networks while running Kismet, what I meant is that at times Kismet cannot see any wireless networks at all while running, or it groups all networks it sees into "AutoGroup". A reboot of the N900 usually fixes this strange. issue.

How do you run Kismet? As user or root? Do you run the Kismet server through the client or have you started it manually?

If you want you can contact me through IRC so we may find the cause of your problem faster. (server: irc.freenode.net channel: #kismet nick: lxp)

lxp,

Please see the screenshot for a visual on the issue I am referring to. Notice Kismet says there are 13 networks, yet I only get two AutoGroup entries. I know for a fact that there are at least 7 different Cisco wireless networks (at the place where I took the screenshot). There are also numerous wireless clients around. It may be important to note that when the screenshot was taken I was not associated with any wireless access points (I rebooted and then took the screenshot). I was running Kismet as root. If I enable the Client List within the Kismet UI I am able to see the MAC addresses and Manufacturer information for various wireless clients around my area. I run the Kismet server through the client UI via the normal Kismet UI start-up process.

Please let me know if you can shine some light on this.

...and closing Kismet via the UI produces the below message. I'm not sure if this is normal.

mail_e36,

Can you please run kismet_server separately and send me the output of it.
I would recommend running the following command:
This will start the Kismet server and create the file kismet.log while also letting you view the output of it on terminal.
In a second terminal start Kismet as usual, it should automatically connect to the running server instance.
It would also be good if you can send me your dmesg output. You can put it into a file with e.g.
Please also keep the other Kismet logfiles like Kismet-*.pcapdump, ... as they might be useful for further debugging, but I don't need them right now.

It is normal at least for now.

Did anyone tested the patch from this website http://david.gnedt.eu/blog/2010/05/1...-for-the-n900/ ? It is supposed to give the ability of putting the device in monitor mode......I couldn't get it to work...