How To Get Kismet Work With C3000?

[hkamuro]

I have tried to use kismit with C3000 but cannot get it work.

When I run the kismit_server, it did not have any error message:

-----------------------------------------------------------------------------
Suid priv-dropping disabled.  This may not be secure.
No enable sources specified, all sources will be enabled.
Source 0 (prism2source): Using prism2 to capture packets.
Source 0 (prism2source):  Attempting to enter monitor mode.
Enabling monitor mode for a prism2 card on wlan0 channel 6
message=lnxreq_wlansniff
  enable=true
  channel=6
  prismheader=no_value
  wlanheader=no_value
  keepwepflags=no_value
  stripfcs=no_value
  packet_trunc=no_value
  resultcode=success
Source prism2source: Created child capture process 893
Capture child 893 (prism2source): Capturing packets from Prism/2 (DEPRECATED)
Enabling channel hopping.
Disabling channel splitting.
Allowing clients to fetch WEP keys.
WARNING:  Disabling GPS logging.
Logging networks to Kismet-Dec-09-2004-1.network
Logging networks in CSV format to Kismet-Dec-09-2004-1.csv
Logging networks in XML format to Kismet-Dec-09-2004-1.xml
Logging cryptographically weak packets to Kismet-Dec-09-2004-1.weak
Logging cisco product information to Kismet-Dec-09-2004-1.cisco
Logging data to Kismet-Dec-09-2004-1.dump
Writing data files to disk every 300 seconds.
Mangling encrypted and fuzzy data packets.
Reading AP manufacturer data and defaults from /usr/local/etc/ap_manuf
Reading client manufacturer data and defaults from /usr/local/etc/client_manuf
Dump file format: wiretap (local code) dump
Crypt file format: airsnort (weak packet) dump
Kismet 3.0.1 (Kismet)
Logging data networks CSV XML weak cisco
Listening on port 2501.
Allowing connections from 127.0.0.1/255.255.255.255
Registering builtin client/server protocols...
Registering requested alerts...
Registering builtin timer events...
Enabling packet source 0 (prism2source)...
Gathering packets...

--------------------------------------------------------------------------------------

However, it just stop at Generating packets without any response. I am sure it has wireless AP around here, as my friend's C860 can detect AP with the same config from me.

Anyone has idea?

- Ken

[orange]

I dont got a C3k (but will get mine soon    )

have you tryed this ?

plz let us know if it works

[hkamuro]

I have tried the command line method before.

However, when I type "cardctl scheme CardResume",
it return "loctl(): Device or resource busy" problem.

But I am sure the Wireless CF is ok as I can connect to the wireless network normally.

- Ken

[devster]

Command line method doesnt work for me, either.

No success with kismet on the C3000, although my CF works fine.

When I get some more time I'll continue bashing away on it ...

[hkamuro]

Finally I make it work.
Please make sure the following in kismet.conf:

source=prism,wlan0,prism

I have tried source=prism_legacy,wlan0,prism but cannot success. After changed prism_legacy to prism, it is working.

[Smokin]

 I have tried to get Kismet working on the C3000 with sharp rom, linksys wcf12, please help.
Here is what I've done:

installed via package manager:
kismet 2004-10-R1
kismet-qt 2.0

modified:
kismet.conf
source=prism2,wlan0,prism2source

followed (http://www.timekiller.org/howtos/kismet-5600.html?22-DEC-2003)
to create:
kis_script.sh
but, under Network and Config was unable to
check 'Non-Spec ESS-ID:"ANY"
and
select TCP/IP at the same time with network account "Kismet"

changed kismet icon to run kis_script.sh

1) Here is what happens when I run kismet_qt from termianl(with out the wcf12 card light on):
"can't connect to server" and when  I exit the terminal says:

QLbirary open failed: /home/QtPalmtop/lib/libqsfepj.so, libkke.so.1: cannot load shared object file: no such file or directory
eth0: unkown interface: no such device
wlanctl-ng: no such device
Found a script hopper

2) When I try and run from the desktop via the icon kismet_qt loads up and then kicks me out

3) When I run kismet_server from terminal I get:
segmentation fault

Please help!!

[orange]

hi Smokin

first of all I had no luck with this Version of Kismet I use this

then the next thing I found very helpfull was this "How to run Kismet on a SL-6000" cuz one thing that is missing in the howto on here is that you have to make your wireless connection in ad-hoc (this prevents it from timing out)

[Smokin]

Thanks Orange,
Works like a charm. Any clue as to why the kismet 2004 doesn't work on the c3000?

[devster]

awesome !!!    ... using V3 it finally works... yep, Ive been unable to get 2004 working either... I spend many weeks trying to get 2004 working...

anyway, apart from a few diffs in the guide (for example, some of the paths change when you are root on the C3000) , it works like a charm.

[Kerensa]

I used the instructions here, trying both to install and not install the files other than kismet V3 and kismet-qt. In both cases when I install kismet V3 I get an error that something went wrong with the ipk and then the installation does not occur.

Could there be other libraries that I am missing? Suggestions would be welcome.

Thank you,
Kerensa

* Update* Got it installed (it needed a library a bit different from the one mentioned). Got the kismet.conf edited, now playing with the app itself. This is a learning experience!

[mammothrept]

Can you be more specific?  I've tried getting Kismet to work on my C3000 and no success yet.

I used the instructions here, trying both to install and not install the files other than kismet V3 and kismet-qt. In both cases when I install kismet V3 I get an error that something went wrong with the ipk and then the installation does not occur.

Could there be other libraries that I am missing? Suggestions would be welcome.

Thank you,
Kerensa

* Update* Got it installed (it needed a library a bit different from the one mentioned). Got the kismet.conf edited, now playing with the app itself. This is a learning experience!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=66830\"][{POST_SNAPBACK}][/a][/div]

[Kerensa]

These are the steps that ended up working for me. I could not get the script that starts the card to work, but i intend to keep playing with it. Did anyone get a similar script to work?

1) Obtain Kismet, Kismet-qt, libpcap, and libstdc++ from:
•   http://members.cox.net/skoorb/libpcap0_0.7.2_arm.ipk
•   libstdc++2.10.glibc2.2 from the feed at http://cacko.biz/cacko/feed
•   http://zaurususergroup.com/feed/kismet_3.0...0031228_arm.ipk
•   http://prdownloads.sourceforge.net/kismet-...t_2.0.0_arm.ipk

2) Setup a network connection
Name: AdHoc for Kismet

Config
ESS-ID: any
Network type: Ad-Hoc

TCP/IP
Select 'Specify' IP Address: 10.1.0.2
Subnet Mask: 255.0.0.0
Gateway: 10.1.0.1
DNS 10.1.0.1

3) edit /usr/local/etc/kismet.conf
So that it includes:
source=prism2,wlan0,prism2source

4) Next make kismet_qt run as root

5) Connect to the network service you created and then launch kismet

[DoTheDog]

Hey All, I realize this is an old thread however, I seem to be having a problem with kismet on my c3100.  I got it all installed etc. and I can run kismet IF I am connected to my AP at home. The problem comes when I try to connect to the ad-hoc network "Kismet" as seen here: http://www.users.on.net/~hluc/myZaurus/custom.html#kismet

When I click to connect to the Kismet ad-hoc network, I get a long pause while it is "initializing", however, if I start kismet while doing this I get a number of errors basically saying there is no such device. If I do an ifconfig while it is in this state I only get a lo device showing.  The funny thing is if I connect to my wireless AP, I can run kismet command line, and from the Qt menu (if I start the kismet-server command line first) and it picks up my AP as well as a neighbor's.

I am wondering if it is an ad-hoc network connection problem with the z? I wrote another post here: https://www.oesf.org/forums/index.php?showtopic=14659&hl=
but didn't get a response.

Anyone else run into this?

[Cresho]

kismet solution for c1000 and c3100

install-all to internal drive:

    * libstdc6_1.2.2_arm.ipk
    * libpcap - [libpcap0_0.7.2_arm.ipk
    * kismet3 - [kismet_3.0.1c-20031228_arm.ipk
    * kismet-qt - [kismet-qt_2.0.0_arm.ipk

hold down the kismet icon in applications and checkmark "start with root" and remove checkmark on "magnify".

su and use zeditor or your favorite editing program and change variables in /usr/local/etc/kismet.conf

change with zeditor or your favorite as su or root and change the variables in

the code looks like this combined
_____________________________________________________________
# source=cisco,eth0,ciscosource
# Other common source configs:
# source=prism2,wlan0,prism2source
# source=prism2_avs,wlan0,newprism2source
source=orinoco,eth0,orinocosource

to

this

# source=cisco,eth0,ciscosource
# Other common source configs:
source=prism2,wlan0,prism2source
# source=prism2_avs,wlan0,newprism2source
# source=orinoco,eth0,orinocosource
_____________________________________________________________
look deep but you will find it.


Once that is done create a network profile as follows:
_____________________________________________________________
      Account
        Name: kismet
 
      Config
        Non-Spec ESS-ID: "ANY" (unticked)
        ESS-ID: any
        Network Type: 802.11 Ad-Hoc

      WEP
        Key Type: Disabled

      PPoE
        Use PPoE Authentication (unticked)

      WEB Auth
        Use WEB Authentication (unticked)

      TCP/IP
        Obtain TCP/IP information Automatically (unticked)
        IP Address: 10.1.0.2
        Subnet Mask: 255.0.0.0
        Gateway: 10.1.0.1

      DNS
        Auto-detect name servers (unticked)
        Primary DNS: 10.1.0.1
        Secondary DNS:
        Default domain: (leave empty)

      Proxy
        No proxy
_____________________________________________________________

now start up kismet and it will lock up.....wait no more than probably a minute and it will say that it cannot connect to server.  click on quit and then hit config tab in kismet.  change scheme to socket and click on save and close kismet.  click the icon connection manager in the taskbar and connect to kismet.  Once it says "connected", go to applications tab and start up kismet.  Give it a few seconds and you have your results.

after all that mess, all you need to to from now on is...
Connect to this network which is kismet and then start Kismet.  that is all.


i found a problem though, if you cannot connect after to your regular wifi, just eject cf wifi and reinsert it.  I dont know what causes this problem. or reboot as well if it fails.




Tutorial done by cresho@earthlink.net

[DoTheDog]

Cresho, that is an awesome guide! I actually used your guide to setup kismet.  The problem I have is that when I try to connect to the "kismet" ad-hoc network, I never connect and a wlan0 device is not created. kismet works if I connect with an access point first. I'm wondering if it is a hardware problem.  What wifi card are you using?