mail_e36 | # 61 | 2010-06-01, 14:26 | Report

lxp,

As an update to my last post, since flashing my N900 and upgrading to PR 1.2 I no longer experience the the 'Autogrouping everything' problem.

The problem was likely linked to my highly modified instance of PR 1.1.

On a different note, what is your opinion on these Kismet plugins which have recently popped up for the N900 Kismet application? Have you tried any of them, have you had any luck with them?

Thanks again

lxp | # 62 | 2010-06-02, 16:29 | Report

I haven't tested any of the plugins because non of them are useful for myself. The following is only my opinion about the usability of the plugins.

kismet-plugin-autowep - Calculate WEP key for one specific access point type
Useful if you have a supported ap in range. See http://xkyle.com/2009/03/03/verizon-...ey-calculator/

kismet-plugin-btscan - Active Bluetooth scanning
I am pretty sure btscan will badly influence the wlan scanning results as it does ACTIVE bluetooth scanning.

kismet-plugin-dot15d4 - Support for 802.15.4 low-power network sensors, ...
Useless without special scanning hardware. Moreover the plugin seems to be incomplete.

kismet-plugin-ptw - Tries to brouteforce the WEP key for networks in range (using aircrack-ng code)
I think that plugin will cause enormous battery drain because of the high cpu usage.

kismet-plugin-spectools - Displays wireless spectrum discovered by spectrum analysers like the Wi-Spy (tm Metageek)
Useless without special scanning hardware.

---

Last edited by lxp; 2010-06-02 at 17:32.

hawaii | # 63 | 2010-06-09, 21:43 | Report

Just wanted to chime in here, for some reason offline mode is being enabled when kismet is invoked. I'm not sure if it's the server or the client.

This shouldn't happen.

lxp | # 64 | 2010-06-09, 23:42 | Report

This is part of expected behaviour, exactly speaking kismet_server should put wlancond in offline mode and the rest of the system shouldn't be affected. This should result in WLAN being unavailable while running kismet_server but GSM/UMTS should work as normal.

That hack is needed because wlancond interferes with monitor mode. Completely stopping and starting wlancond is error-prone, so I have decided to use the offline mode way.

The only problem I am aware of until now is if you exit Kismet through the X button it wouldn't restore the wlancond status. You should exit it using Ctrl+C as a workaround of that problem.
I also expect monitor mode will break if you manually change online/offline mode while using Kismet.

hawaii | # 65 | 2010-06-10, 02:38 | Report

GSM is dropped out for me. I'll do some more testing and report back

q6600 | # 66 | 2010-06-11, 13:28 | Report

hi
to do a handsake with n900 asuming thet you have clients on the network you need injetion?
i capture a .cap with one handshake but i got not passfrase in dictionari ( i use password.lst feom aircrack and password.lst from jack the reapper)
i do somting wrong or is just becose injection is not working with n900?

hawaii | # 67 | 2010-06-11, 13:36 | Report

Live injection without association does NOT work with the WL1251. Seems to be an issue with tertiary firmware AND drivers. Wait a while.

mail_e36 | # 68 | 2010-06-11, 14:07 | Report

Hello everyone,

It appears I spoke too soon in my previous posting when I said there is no problem under PR 1.2.

Indeed all the same problems I had with my customized PR 1.1 have now come back with PR 1.2 (I did a completely fresh flash of everything on my N900, not an upgrade from PR 1.1), including the problem which "AutoGroups" everything came back.

Additionally, at times when I start up Kismet it cannot even bind to the wireless interface, with the console reading "capture source 'wlan0' doesn't appear to use the set_prismhdr i control". Selecting "Close Console Window" persistently shows zero visible networks in areas of high network concentrations.

Sometimes a reboot resolves the problem, more often a reboot does not resolve the problem.

I am running Power Kernel 2.6.28.10power37, dated May 26th 2010. Do we suspect this to be a driver issue?

Has any experience similar issues?

Crogge | # 69 | 2010-06-11, 14:20 | Report

Looks promising, but is it safe to use this app on Titans V37 on FW 1.2 already? Thanks in advance for a reply.

mail_e36 | # 70 | 2010-06-11, 15:20 | Report

For more information, I have recently updated to the newest Power Kernel from the previous version, it is very possible that the problem with Kismet started showing up after upgrading to the latest Power Kernel (Power Kernel 2.6.28.10power37).

Here is the basic timeline (if it is of any help I installed PR 1.2 the day it was released, installed the newest available Power Kernel, and things were running smoothly, Kismet was working well. About a week after PR 1.2 is released Titan released his new version of the Power Kernel, I upgraded to it, and didn't check Kismet for a while. I finally had some time to try Kismet and I started experiencing the previously stated problems with Kismet.

This would lead me to suspect the new Power Kernel causing the issue to come back, but this is more of a hypothesis than a fact.

Is anyone running the latest Power Kernel 2.6.28.10power37 with the latest Kismet, do you experience problems?

Thanks