View previous topic :: View next topic |
Author |
Message |
JanErik Guru
![Guru Guru](/images/ranks/rank_rect_3.gif)
Joined: 28 Oct 2002 Posts: 488 Location: Finland
|
Posted: Fri Jul 16, 2004 8:11 pm Post subject: Kismet problem, cannot connect to localhost:2501 |
|
|
I have emerged kismet 3.0.1-r1.
First I run "/etc/initd/kismet start" as root.
Then I try to start "kismet" as a normal user (jskata). It is supposed to be done like that, am I right?
But I get this error message:
Code: | bash-2.05b$ kismet
Server options: none
Client options: none
Starting server...
Will drop privs to jskata (1001)
Source 0 (orinocosource): Using pcap to capture packets from eth0
Source 0 (orinocosource): Attempting to enter monitor mode.
Waiting for server to finish starting before startuing UI...
Enabling monitor mode for an orinoco card on eth0 channel 6
Interface doesn't accept private ioctl...
monitor (8BE8): Operation not permitted
SIOCSIFFLAGS: Permission denied
SIOCSIFFLAGS: Permission denied
Source orinocosource: Created child capture process 6622
Dropped privs to jskata (1001)
Enabling channel hopping.
Disabling channel splitting.
Allowing clients to fetch WEP keys.
Using metric measurements.
WARNING: Disabling GPS logging.
Logging networks to Kismet-Jul-16-2004-1.network
Logging networks in CSV format to Kismet-Jul-16-2004-1.csv
Logging networks in XML format to Kismet-Jul-16-2004-1.xml
Logging cryptographically weak packets to Kismet-Jul-16-2004-1.weak
Logging cisco product information to Kismet-Jul-16-2004-1.cisco
Logging data to Kismet-Jul-16-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
Reading client manufacturer data and defaults from
/etc/kismet/client_manuf
Dump file format: wiretap (ethereal libwiretap) 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 (orinocosource)...
Gathering packets...
Shutting down source 0 (orinocosource)...
Didn't detect any networks, unlinking network list.
Didn't detect any networks, unlinking CSV network list.
Didn't detect any networks, unlinking XML network list.
Didn't detect any Cisco Discovery Packets, unlinking cisco dump
Didn't capture any packets, unlinking dump file
Didn't see any weak encryption packets, unlinking weak file
Waiting for capture child 6622 to terminate...
Kismet exiting.
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. |
I have tried using either 127.0.0.1 or localhost in /etc/kismet config files. |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
JPMRaptor Guru
![Guru Guru](/images/ranks/rank_rect_3.gif)
![](images/avatars/518942103409c3fbe53c05.jpg)
Joined: 04 Oct 2002 Posts: 410 Location: Maryland
|
Posted: Fri Jul 16, 2004 10:25 pm Post subject: |
|
|
After starting the kismet server check that it is running with "ps ax". I've had problems running it with the init script. Instead I've run it by running the command in the init script directly. _________________ Underwater photo gallery
New pictures, Oct 2005 |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
JanErik Guru
![Guru Guru](/images/ranks/rank_rect_3.gif)
Joined: 28 Oct 2002 Posts: 488 Location: Finland
|
Posted: Sat Jul 17, 2004 3:11 pm Post subject: |
|
|
I think it is running. But there appears to be problems shutting it down, because after I run "/etc/init.d/kismet stop" the process is still there. |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
Willem Hendriks n00b
![n00b n00b](/images/ranks/rank_rect_0.gif)
Joined: 20 Nov 2003 Posts: 7
|
Posted: Sun Jan 30, 2005 4:19 pm Post subject: |
|
|
try to cd to /tmp as root and then start kismet_server:
( i don't know why kismet_server needs to be started from specific dirs..., thats why /etc/init.d/kismet start don't work i think)
bash-2.05b# cd /tmp/
bash-2.05b# kismet_server
and start kismet_client iso. kistmet
bash-2.05b$ kismet_client
(2005.01.R1) |
|
Back to top |
|
![](templates/gentoo/images/spacer.gif) |
|