Kismet woes

[kic]

So I got kismet installed aind t seems to be running fine until I see this:

Error opening terminal: vt100.

I scoured kismet's forums for an answer and tried the suggestions, namely to do a export TERMINFO=/etc/terminfo and/or to put it in the profile. Well, no luck. So I tried doing a TERM=vt100 and stiil get the same thing.

I grabed an ipk for version 3.1.0 for OZ and have all of the dependencies installed. If i run kismet_server it appears to be fine and scanning, but doing plain ol' kismet gives me the error above.

Am I mising something completely obvious or skipping steps? (I have edited the .conf for the user and card/chipset.)

Suggestions/help would be appreciates. Thanks.

I should also add I'm running OZ 3.5.1 on an 860, just in case that's helpful.

[jorvic]

I've been running into the same thing. I've spent a bit of time playing with it but to no avail thus far. So if any of you have an idea it would be nice to hear

[jorvic]

Ok I got this to work on mine. I am running the same ROM as you however I am on a 5500. However some of this should help.


First make sure you have ncurses and the ncurses terminfo ipks from the feed installed.

Once you have that done you should be able to either put an entry in /etc/profile or add an enviroment variable from the prompt for TERMINFO=/mnt/ram/usr/share/terminfo (or wherever you installed your terminfo)
if you put it in your profile just put an export before it.

Go through and set up your two kismet conf files now.

If you added the TERMINFO into your profile go ahead and source it by . /etc/profile

if you put it in the terminal as an env variable just close the terminal and reopen to make sure it takes it


After that just run kismet and you will hopefully be good to go, if you still have problems just let us know





Now there might be better ways or some of the things I said might not be needed if so feel free to let me know


EDIT: If you want color with kismet make sure to use linux as your terminal instead of vt100

Jorvic

[kic]

Jorvic, thanks much for the info. I'm planning on wiping my Z today and reinstalling everything. Provided I don't end up doing something stupidthat results in bricking it, I was hoping to get kismet to work fully (the server works fine, as I demonstrated for some friends last night). This info ought to help a bunch to get things set straight.

And you can count on me being back if it doesn't work.

[kic]

Ok, here's what I have done.

I formatted and reinstalled OZ 3.5.1, installed the oz-compat libs, Opera, ncurses and ncurses-terminfo. So far so good. I then installed Kismet 3.1.0 (I believe), configured the kismet.conf (main changes were setting the user to root (too lazy to add another user), disable gps and sound, and set the adapter to hostap,wlan0,hostapsource). I then disabled sounds in the kismet_ui.conf file.

Next was to do a export TERMINFO=/usr/share/terminfo (where it is installed, I doublechecked), closed the terminal, opened a new terminal, and ran kismet. Once again, the server runs, but when it tries to start the client (at least I presume that is what it is doing), I get the exact same error that I posted before.

The card I'm using is the standard Ambicom WL1100C that everyone seems to have good luck with (in fact, normal network operations work fine, it's just kismet I'm struggling with). I did also try one of the prism2 options in kismet, but it didn't like the card, so reverting back to the hostap, etc fixed that.

I did try to add TERMINFO=/usr/share/terminfo to the /etc/profile, but when I tried to "run" it so that it would effect the change (by doing a ./etc/profile) I got a "permission denied" error. At that point I removed the entry and did the export, close, open deal as described above.

While overall everything is running better, I still find myself lost and hopelessly confused with kismet.

Further advice/suggestions would be greatly appreciated.

I'm fairly sure I covered everything I did, but please ask if you need more info for what I did or did not do.

(Also, I didn't see an option to change the terminal type in the kismet configuration file (to change from vt100 to linux) and didn't see a flag for it. Off to do more searching.)

[kic]

I'll be damned. It runs now. I don't know what I did (reboot?) but now it runs and the client is up and happy. And thus, so am I.

Still trying to figure out why Wellenreiter fails to install, but that's for another thread, I belive.

My thanks again.

[JohnKiniston]

Are you trying to install Wellenreiter from the http://www.vanille.de/feed/ feed or the http://www.openzaurus.org/official/testing/3.5.1/feed ?

I've got it installed and working from the http://www.openzaurus.org/official/testing/3.5.1/feed/ feed, I had to make one configuration change (wifi0 was selected for the interface and I needed wlan0)

Where are you getting your kismet ipkg from? I dont see it in the http://www.openzaurus.org/official/testing/3.5.1/feed/ feed.

[kic]

I'll be damned. I didn't even see Wellenreiter in the OZ feed. Looks like it installed and runs. I'll have to mess with it a little, but neato.

I don't remember where I got Kismet from, but all seems fine now. I still have a profile/variable issue to fix, but I can make it work when I want to now.

[altais]

Hello,
I hate people who do not RTFM and I do not want to be one of those people. So could someone please point me to where the is a guide on adding to the profile and basicly doing what is stated to fix this issue. I really need to get Kismet and all of the other tools listed on  IronGeek to work on my C750 using Opie 3.5.1. Any help would be greatly appreciated!