Kismet on the 6000 Options

[thomasbernie]

I'm buying for the first one to figure out how to make Kismet play. Everything installs OK and seems to be in the right place, but no receive. I wonder how far off OZ is?

[BarryW]

Anybody try the new kismet_2005.01.R1_arm.ipk from kismetwireless? I got it to install but when I try to run it it gives me a bus error...

[cvmiller]

Anybody try the new kismet_2005.01.R1_arm.ipk from kismetwireless?  I got it to install but when I try to run it it gives me a bus error...

No, I haven't. I was about to thought (thanks for the update). The 2004 version of kismet also gave a bus error, so there is something wrong there.

Craig...

[adf]

there was a post on uclx compression and bus errors on the 3000 a day or two ago. maybe this is related? I think it said kismet was uclx compressed, but that the issue with bus errors is genrally a lack of decompression space. maybe permanently uncompress the bin?

[cvmiller]

there was a post on uclx compression and bus errors on the 3000 a day or two ago. maybe this is related?  I think it said kismet was uclx compressed, but that the issue with bus errors is genrally a lack of decompression space.  maybe permanently uncompress the bin?

Thanks for the tip. That did the trick. I uncompressed the kismet binary (and kismet-ui) using uclx -d and now the lastest kismet runs quite well!

Thanks again,

Craig...

[ken]

Thanks for the tip. That did the trick. I uncompressed the kismet binary (and kismet-ui) using uclx -d and now the lastest kismet runs quite well!

what did you use for the "source=" line?

It would seem that there's a number of changes from the 2003 version to the 2005 version of kismet, and "prism2, wlan0, prism2source" no longer is valid.

I'm not sure if it's correct or not, but I'm using

"wlanng,wlan0,prism2source" which seems to work.

[cvmiller]

Thanks for the tip. That did the trick. I uncompressed the kismet binary (and kismet-ui) using uclx -d and now the lastest kismet runs quite well!

what did you use for the "source=" line?

It would seem that there's a number of changes from the 2003 version to the 2005 version of kismet, and "prism2, wlan0, prism2source" no longer is valid.

I'm not sure if it's correct or not, but I'm using

"wlanng,wlan0,prism2source" which seems to work.

Yes, there are changes, as I also discoverd that prism2 was no longer a valid choice. I am also using "wlanng, wlan0, sniffer" for my source. (the last field, sniffer, can be any string). With this setting Kismet successfully detects my AP at home, and it caught a couple of Network probe frames (from a nearby PC) at work.

I hope this helps,

Craig...

[ken]

ok, that takes care of one aspect. I've been trying to do it all from the console, and haven't gotten very far yet.

The first part of the problem is to get the interface up. I've discovered that I can do a:

usbctl on 1

and that'll turn it on. I'm still trying to get it to go in "mode monitor" that I keep reading about. No luck so far.

[cvmiller]

ok, that takes care of one aspect.  I've been trying to do it all from the console, and haven't gotten very far yet.

The first part of the problem is to get the interface up.  I've discovered that I can do a:

usbctl on 1

and that'll turn it on.  I'm still trying to get it to go in "mode monitor" that I keep reading about.  No luck so far.

Yes, doing it all from the console is a little trickier than the GUI, but it can still be done. BTW, I have a AdHoc network setup in my Zaurus (GUI) that I just fire up before running Kismet and that works pretty well. However if you want to do it all from the console you need to do a bit more typing:
usbctl on 1
sleep 1
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
ifconfig wlan0 1.1.1.1 up

Then start kismet. After you are done with Kismet, turning off the interface is a bit easier:
usbctl off 1

I have run Kismet this way, while accessing my Zaurus via ethernet (a CF card) and it works fine, just not as portable ;-)

I hope this helps,

Craig...

[ken]

usbctl on 1
sleep 1
wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
ifconfig wlan0 1.1.1.1 up

wow. I don't think I'd ever guess the rest of it! That seems to take care of the interface.

I noticed if I left in the "cisco,gps" part in logtypes that it'd complain about cisco things, so I took that out. It works great in the kismet GUI, just have to play more to get the kismet console part going. Something about "Error opening terminal: vt100" - which I think is because it's trying to open that kind of session in my bash shell. It's getting close!

Thanks for the hints thus far.

[cvmiller]

It works great in the kismet GUI, just have to play more to get the kismet console part going.  Something about "Error opening terminal: vt100" - which I think is because it's trying to open that kind of session in my bash shell.  It's getting close!

Thanks for the hints thus far.

Ken,

Hmm, are you starting this as root? Here's a script I have that I use to start kismet, called, not surprizingly start_kismet (in /usr/local/bin)

CODE

#!/bin/sh

export TERMINFO=/usr/share/terminfo
export TERM=linux

kismet_hopper &
sleep 2
kismet

I have been using this script for previous versions of Kismet (which is where I got the kismet_hopper part). I just added the TERM info with this version. I am using qkonsole for my terminal program, and I'll warn you that the lines drawn on the terminal (to separate the areas of the UI) don't look like lines, but I hadn't bothered me enough to seek a solution.

I suppose if you wanted you could add all the bring the interface up, and then shut it down afterwards in this script as well, just never needed to (since I use the GUI to bring up my AdHoc interface config).

I hope this helps,

Craig...

[ken]

Hmm, are you starting this as root? Here's a script I have that I use to start kismet, called, not surprizingly start_kismet (in /usr/local/bin)
[code]
#!/bin/sh

export TERMINFO=/usr/share/terminfo
export TERM=linux

ahhhhhh! It was complaining of having to use vt100. ok, that certainly explains it then. I had looked at the TERM and it was showing vt100, so I was thinking, what did I do wrong, it has the vt100 that it's complaining about, why is it complaing that it doesn't have that. I hadn't known that it did NOT want vt100.

That solves it! Much appreciate - kismet comes right up now.

[cvmiller]

ahhhhhh!  It was complaining of having to use vt100.  ok, that certainly explains it then.  I had looked at the TERM and it was showing vt100, so I was thinking, what did I do wrong, it has the vt100 that it's complaining about, why is it complaing that it doesn't have that.  I hadn't known that it did NOT want vt100.

That solves it!  Much appreciate - kismet comes right up now.

Ken,

Glad to hear you are having success. Actually if you _want_ to use vt100 you can, just change 'linux' to 'vt100' in my script. I think the real complain was that it didn't know where to get the terminfo. I changed mine to vt100 just to see if it would fix the "line drawing" problem, and it didn't. But Kismet works. I switched it back to 'linux' because I like the color output (vt100 was only b&w).

Let me know if you get sound working (I lack /usr/bin/play).

Happy sniffing,

Craig...

[pelendur]

Glad to hear you are having success. Actually if you _want_ to use vt100 you can, just change 'linux' to 'vt100' in my script. I think the real complain was that it didn't know where to get the terminfo. I changed mine to vt100 just to see if it would fix the "line drawing" problem, and it didn't. But Kismet works. I switched it back to 'linux' because I like the color output (vt100 was only b&w).

Let me know if you get sound working (I lack /usr/bin/play).

Happy sniffing,

Craig...

The line drawing problem can be easily fixed by changing the simpleborders option in kismet_ui.conf to true, i.e. simpleborders=true. As for sound, the kismet_3.0.1c-20031228_arm.ipk mentioned earlier in this thread has /usr/bin/play and the various required sound files. You should be able to extract those files from the ipk. Hope this helps.

Patrick