Active Topics
-
Error after installing Leste on sdcard (13)
to Maemo 7 / Leste by Maemish - 3 hrs, 9 mins ago -
TLS 1.2 for N9 is ready (29)
to MeeGo / Harmattan by smatkovi - 11 hrs, 58 mins ago -
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 3 days, 21 hrs ago -
Maemo repository (3)
to Community by torsen - 4 days, 13 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 6 days, 17 hrs ago - more...
 |
|
2010-06-11
, 19:04
|
|
Posts: 1,030 |
Thanked: 792 times |
Joined on Jun 2009
|
#72
|
Kismet will capture any and all traffic "on the wire". Data, beacons, management frames, including wpa handshakes if they take place.
|
|
2010-06-11
, 19:14
|
|
Posts: 146 |
Thanked: 39 times |
Joined on May 2010
|
#73
|
thank you!
i try to capture some data but no luck with handshakes. i will try some more.
i try to capture some data but no luck with handshakes. i will try some more.
|
|
2010-06-11
, 19:20
|
|
Posts: 1,463 |
Thanked: 1,916 times |
Joined on Feb 2008
@ Edmonton, AB
|
#74
|
Originally Posted by Crogge
Looks promising, but is it safe to use this app on Titans V37 on FW 1.2 already? Thanks in advance for a reply.
Originally Posted by mail_e36
Sometimes it doesn't work on the first try, but I've never had to restart the device. ctrl-c and then launching again has always worked.
Is anyone running the latest Power Kernel 2.6.28.10power37 with the latest Kismet, do you experience problems?
I'll try it right now... and it worked, first try.
Maybe you should try returning to stock frequencies/voltages and see if that helps.
|
|
2010-06-11
, 20:09
|
|
Posts: 146 |
Thanked: 39 times |
Joined on May 2010
|
#75
|
no problem with power kernel 2.6.28.10power37 so far
|
|
2010-06-12
, 10:56
|
|
Posts: 9 |
Thanked: 3 times |
Joined on Jan 2010
|
#76
|
Hello
I run 2.6.28.10power37 kernel overklocked ideal to 700 MHz.
Also have PR1.2 and latest kismet.
I have to run as root, when I do I see many networks and packets coming on them.
Diff between you and me I have never ran an older power kernel and never reflashed.
I run 2.6.28.10power37 kernel overklocked ideal to 700 MHz.
Also have PR1.2 and latest kismet.
I have to run as root, when I do I see many networks and packets coming on them.
Diff between you and me I have never ran an older power kernel and never reflashed.
|
|
2010-06-14
, 00:22
|
|
Posts: 502 |
Thanked: 366 times |
Joined on Jun 2010
@ /dev/null
|
#77
|
Ok as requested by lxp, I hereby report my findings on kismet with almost latest stuff.
PR1.2 firmware: flashed without using OTA method. eMMC remains stock.
kernel: 2.6.28.10power37. No other kernel hack patches added on.
wireless power management: off (disabled completely via wlancond with settings from one AP profile).
The issue seems to be with bluetooth co-existance. I originally had my bluetooth turned on but in hidden mode and the results from both kismet and airodump-ng only showed probes (along with autogroup probe under kismet) but no APs except when I physically raised the height of the n900 I was only able to pick up one or two (along with physically rotating n900). However whilst constantly on the move I was not able to pick up any APs only probes.
The issue was later solved by turning off bluetooth completely which resulted in perfectly working kismet along with airodump-ng.
Thanks again to lxp (lxp1 on #kismet at irc.freenode.net) for the help
(edit) It was interesting to note however, during bluetooth module being turned on and set to hidden mode, the wireless module device being in managed mode (not monitor mode), it was able to pick up far more APs with active probing. (/edit)
Last edited by tuxsavvy; 2010-06-14 at 00:29.
PR1.2 firmware: flashed without using OTA method. eMMC remains stock.
kernel: 2.6.28.10power37. No other kernel hack patches added on.
wireless power management: off (disabled completely via wlancond with settings from one AP profile).
The issue seems to be with bluetooth co-existance. I originally had my bluetooth turned on but in hidden mode and the results from both kismet and airodump-ng only showed probes (along with autogroup probe under kismet) but no APs except when I physically raised the height of the n900 I was only able to pick up one or two (along with physically rotating n900). However whilst constantly on the move I was not able to pick up any APs only probes.
The issue was later solved by turning off bluetooth completely which resulted in perfectly working kismet along with airodump-ng.
Thanks again to lxp (lxp1 on #kismet at irc.freenode.net) for the help
(edit) It was interesting to note however, during bluetooth module being turned on and set to hidden mode, the wireless module device being in managed mode (not monitor mode), it was able to pick up far more APs with active probing. (/edit)
Last edited by tuxsavvy; 2010-06-14 at 00:29.
|
|
2010-06-14
, 15:19
|
|
Posts: 393 |
Thanked: 67 times |
Joined on Feb 2010
|
#78
|
tuxsavvy,
It seems like you have solved my mystery! Indeed when I test Kismet with Bluetooth DISABLED it seems to run perfectly, but when Bluetooth is on (even in "hidden mode") I only get probes.
I certainly agree the problem is with Bluetooth and Kismet co-existence. While this would be great to fix, we can certainly live with turning off Bluetooth before running Kismet. Lxp should document this, though.
Thanks!
It seems like you have solved my mystery! Indeed when I test Kismet with Bluetooth DISABLED it seems to run perfectly, but when Bluetooth is on (even in "hidden mode") I only get probes.
I certainly agree the problem is with Bluetooth and Kismet co-existence. While this would be great to fix, we can certainly live with turning off Bluetooth before running Kismet. Lxp should document this, though.
Thanks!
Originally Posted by tuxsavvy
Ok as requested by lxp, I hereby report my findings on kismet with almost latest stuff.
PR1.2 firmware: flashed without using OTA method. eMMC remains stock.
kernel: 2.6.28.10power37. No other kernel hack patches added on.
wireless power management: off (disabled completely via wlancond with settings from one AP profile).
The issue seems to be with bluetooth co-existance. I originally had my bluetooth turned on but in hidden mode and the results from both kismet and airodump-ng only showed probes (along with autogroup probe under kismet) but no APs except when I physically raised the height of the n900 I was only able to pick up one or two (along with physically rotating n900). However whilst constantly on the move I was not able to pick up any APs only probes.
The issue was later solved by turning off bluetooth completely which resulted in perfectly working kismet along with airodump-ng.
Thanks again to lxp (lxp1 on #kismet at irc.freenode.net) for the help
(edit) It was interesting to note however, during bluetooth module being turned on and set to hidden mode, the wireless module device being in managed mode (not monitor mode), it was able to pick up far more APs with active probing. (/edit)
|
|
2010-06-16
, 20:07
|
|
Posts: 393 |
Thanked: 67 times |
Joined on Feb 2010
|
#79
|
Lxp,
If you find a few minutes free you may want to update your website to reflect the below information. Knowing this would have saved me tons of time
If you find a few minutes free you may want to update your website to reflect the below information. Knowing this would have saved me tons of time
Originally Posted by mail_e36
tuxsavvy,
It seems like you have solved my mystery! Indeed when I test Kismet with Bluetooth DISABLED it seems to run perfectly, but when Bluetooth is on (even in "hidden mode") I only get probes.
I certainly agree the problem is with Bluetooth and Kismet co-existence. While this would be great to fix, we can certainly live with turning off Bluetooth before running Kismet. Lxp should document this, though.
Thanks!
|
|
2010-06-16
, 20:55
|
|
Posts: 50 |
Thanked: 444 times |
Joined on Apr 2010
@ Austria
|
#80
|
Originally Posted by mail_e36
I have documented it now in my blog.
Lxp,
If you find a few minutes free you may want to update your website to reflect the below information. Knowing this would have saved me tons of time
A big thanks to tuxsavvy who greatly helped solving this problem.
| The Following User Says Thank You to lxp For This Useful Post: | ||
kismet cand capture handsake data pack?