Kismet localhost:2501 connection problems...

servo888 · Apprentice Joined: 22 Feb 2004 Posts: 293

Hello,

I've been trying to get Kismet to work on my laptop. I have a Linksys WCF12 (orionco driver) running in a 64bit envoirment (amd64). Anyways, I'm having two problems. After loading the kismet server the harddrive led turns solid, and my system starts to lag, and when I try to connect to the server with something like kismet_client I get a "FATAL: Could not connect to localhost:2501" error.

The application is masked, but I did read of some reports (from google) that people have been able to run kismet in a 64bit envoirment.

specs:
2.6.7 kernel, AMD64 3400, Linksys WCF12 card,

Any help would be loved,

-servo

korz · Posted: Wed Jun 30, 2004 10:34 pm Post subject:

Hi, i have exactly the same problem (see system output) and wasn't able to solve it. Hope to find answers here, too.
Machine is an P III 650 Notebook with an Orinoco Gold PCMCIA Card.
Thanks!

Server options: none
Client options: none
Starting server...
Waiting for server to finish starting before startuing UI...
Will drop privs to korz (1000)
No enable sources specified, all sources will be enabled.
Source 0 (orinocosource): Using pcap to capture packets from eth1
Source 0 (orinocosource): Attempting to enter monitor mode.
Enabling monitor mode for an orinoco card on eth1 channel 6
Source orinocosource: Created child capture process 6991
Dropped privs to korz (1000)
Enabling channel hopping.
Disabling channel splitting.
Allowing clients to fetch WEP keys.
WARNING: Disabling GPS logging.
Logging networks to Kismet-Jul-01-2004-1.network
Logging networks in CSV format to Kismet-Jul-01-2004-1.csv
Logging networks in XML format to Kismet-Jul-01-2004-1.xml
Logging cryptographically weak packets to Kismet-Jul-01-2004-1.weak
Logging cisco product information to Kismet-Jul-01-2004-1.cisco
Logging data to Kismet-Jul-01-2004-1.dump
Writing data files to disk every 300 seconds.
Mangling encrypted and fuzzy data packets.
Reading AP manufacturer data and defaults from /etc/kismet/ap_manuf
Capture child 6991 (orinocosource): Capturing packets from libpcap device eth1
Reading client manufacturer data and defaults from /etc/kismet/client_manuf
FATAL: Dump file error: Unable to open dump file Kismet-Jul-01-2004-1.dump (Permission denied)
Starting UI...
FATAL: Could not connect to 127.0.0.1:2501.
Client exited, terminating...
Done. Run kismet_unmonitor or eject and re-insert your card (or restart your
pcmcia services) to return your card to normal operation.

korz · Posted: Wed Jun 30, 2004 11:13 pm Post subject:

I think, i found the problem:
Kismet started after i have changed into the homedirectory of the user, i entered in kismet.conf as suiduser (suiduser=foobar => run kismet in /home/foobar).
Cheers

dgtaro · Posted: Sun Jul 11, 2004 1:59 am Post subject:

Is there a GUI for kismet???

DiskBreaker · Apprentice Joined: 07 Oct 2003 Posts: 224

Kismet already has a very nice ncurses GUI.

If you want some more clicky-clicky, you could try Wellenreiter, it has a GTK GUI:

Gentoo Bug #14600 with ebuilds.
http://www.wellenreiter.net/

dgtaro · Posted: Thu Jul 15, 2004 8:15 pm Post subject:

DiskBreaker · Apprentice Joined: 07 Oct 2003 Posts: 224

warravenfk2001 · n00b Joined: 25 Apr 2005 Posts: 3 Location: Kentucky

i messed with gkismet for a bit and found it to be buggy. i'm not sure but it seems that you have to run it in conjunction with kismet. and when i did that, kismet would crash all the time. when i would run it by itself it would run on forever. so.. i'm not sure if gkismet is the perfect choice. I'm sticking w/ ncurses GUI for now, till i find something nicer

_________________
Toshiba 1415-S173 1.8 GHz Celeron, 512MB RAM, 30GB HDD, Gforce4, linux-2.6.11-gentoo-r6