| View previous topic :: View next topic |
| Author |
Message |
farrioth
Apprentice
Joined: 23 Nov 2003
Posts: 282
Location: Auckland
|
 Posted: Sat Aug 14, 2004 11:32 pm Post subject: kismet problems |
 |
|
I am trying to get kismet to work with my prism54 card. This is what happens when I run kismet as root (with my card in monitor mode):
| Code: |
Server options: none
Client options: none
Starting server...
Waiting for server to finish starting before startuing UI...
Will drop privs to farrioth (1000)
Starting UI...
FATAL: Could not connect to localhost: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.
|
After kismet exits my computer hangs for about 30s.
Here is my /etc/kismet/kismet.conf:
| Code: |
version=3.0.1c
servername=Kismet
suiduser=farrioth
source=generic,eth0,prism54
enablesources=prism54
channelhop=true
channelvelocity=5
splitchannels=true
80211bchannels=1,2,3,4,5,6,7,8,9,10
80211achannels=36,40,44,48,52,56,60,64
tcpport=2501
allowedhosts=127.0.0.1
maxclients=5
alert=NETSTUMBLER,5/min,2
alert=WELLENREITER,5/min,2
alert=LUCENTTEST,5/min,2
alert=DEAUTHFLOOD,5/min,4
alert=BCASTDISCON,5/min,4
alert=CHANCHANGE,5/min,4
alert=AIRJACKSSID,5/min,2
alert=PROBENOJOIN,5/min,2
alert=DISASSOCTRAFFIC,5/min,2
alert=NULLPROBERESP,5/min,5
allowkeytransmit=true
writeinterval=300
sound=false
soundplay=/usr/bin/play
sound_new=/usr/share/kismet/wav/new_network.wav
sound_traffic=/usr/share/kismet/wav/traffic.wav
sound_junktraffic=/usr/share/kismet/wav/junk_traffic.wav
sound_alert=/usr/share/kismet/wav/alert.wav
speech=false
festival=/usr/bin/festival
speech_type=nato
speech_encrypted=New network detected, s.s.i.d. %s, channel %c, network encrypted.
speech_unencrypted=New network detected, s.s.i.d. %s, channel %c, network open.
ap_manuf=/etc/kismet/ap_manuf
client_manuf=/etc/kismet/client_manuf
metric=false
waypoints=false
waypointdata=%h/.gpsdrive/way_kismet.txt
alertbacklog=50
logtypes=dump,network,csv,xml,weak,cisco,gps
noiselog=false
corruptlog=true
beaconlog=true
phylog=true
mangledatalog=true
fuzzycrypt=prism2_legacy,wtapfile
dumptype=wiretap
dumplimit=0
logdefault=Kismet
logtemplate=%n-%d-%i.%l
configdir=%h/.kismet/
ssidmap=ssid_map
groupmap=group_map
ipmap=ip_map
|
Any help will be appreciated. |
|
| Back to top |
|
 |
geta
Apprentice
Joined: 10 May 2003
Posts: 153
|
| Posted: Sun Aug 15, 2004 5:42 pm Post subject: |
|
|
hi
start iwconfig and check if your card really is in Monitor mode. Secondly, is your wlan card really eth0?
I've had some other strange problems with Kismet. Updating to the latest unstable version in portage solved most of those problems for me:
| Code: | | ACCEPT_KEYWORDS="~x86" emerge kismet |
Cheers, geta
_________________
geta - pronounced: "djetta" |
|
| Back to top |
|
|
farrioth
Apprentice
Joined: 23 Nov 2003
Posts: 282
Location: Auckland
|
| Posted: Sun Aug 15, 2004 10:33 pm Post subject: |
|
|
I have updated to the latest version, reconfigured, and I get the following errors:
| Code: |
Server options: none
Client options: none
Starting server...
Waiting for server to start before startuing UI...
Will drop privs to farrioth (1000) gid 100
Enabling channel hopping.
Enabling channel splitting.
Starting UI...
FATAL: Could not connect to localhost:2501.
Kismet exited.
|
After kismet exits, my computer now hangs for about 2 minutes.
My card is eth0, and is in monitor mode.
| Code: |
eth0 IEEE 802.11b/g Mode:Monitor Channel:6
Access Point: 00:00:00:00:00:00 Bit Rate:54Mb/s Tx-Power=31 dBm
Sensitivity=20/200
Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
|
|
|
| Back to top |
|
|
geta
Apprentice
Joined: 10 May 2003
Posts: 153
|
| Posted: Tue Aug 17, 2004 11:39 am Post subject: |
|
|
you have to start kismet as "su" (same as ethereal). so in a console try:
su -c 'kismet'
I hope that is the solution to your problem, I can't recall what else I had to do.
Cheers, geta
_________________
geta - pronounced: "djetta" |
|
| Back to top |
|
|
farrioth
Apprentice
Joined: 23 Nov 2003
Posts: 282
Location: Auckland
|
| Posted: Wed Aug 18, 2004 4:37 am Post subject: |
|
|
| I presume you mean that kismet must be run as root, which I am doing. |
|
| Back to top |
|
|
geta
Apprentice
Joined: 10 May 2003
Posts: 153
|
| Posted: Wed Aug 18, 2004 7:04 pm Post subject: |
|
|
| farrioth wrote: | | I presume you mean that kismet must be run as root, which I am doing. |
Although its wrong, I do tend to use those words (su and root) synonymously.
One slightly tricky thing I stumbled over with kismet in gentoo, is that there are two config files and both have to be set up correctly (presuming you might not have seen one of them):
/etc/conf.d/kismet
/etc/kismet/kismet.conf
Must seem to you I'm making wild guesses. I did have the same error as you have, it's just that I can't remember all the things at once. Sorry 'bout that!
Cheers, geta
_________________
geta - pronounced: "djetta" |
|
| Back to top |
|
|
DawgG
l33t
Joined: 17 Sep 2003
Posts: 874
|
| Posted: Tue Oct 19, 2004 10:04 am Post subject: sources in kismet? |
|
|
one tricky thing is the definition of the sources in /etc/kismet/kismet.conf
i have a prism54 g card (prismGT _NOT_ prism2) , its definition is
| Code: |
source=prism54g,eth1,test2
|
in my experience this definition is quite delicate for kismet; it might help if you rename the source to something that's NOT a keyword at the same time.
i have never touched /etc/conf.d/kismet because i prefer to start kismet manually (this file is for starting kismet via init.d)
you should configure kismet_ui.conf, though.
are there any firewall-rules in place? i was wondering because the log says sth. about "connection to localhost refused" |
|
| Back to top |
|
|
r1k0d3r
n00b
Joined: 19 Oct 2004
Posts: 33
Location: on a radiowave
|
| Posted: Thu Oct 21, 2004 1:38 pm Post subject: |
|
|
i got a prism54 too, i use kismet 2004.4.R1 and my /etc/kismet/kismet.conf looks lik that for the driver to work:
source=prism54g,eth3,prism54g_source
note that only kismet v4 supports prism54g and you might want to update your version by
#ACCEPT_KEYWORDS="~x86" emerge kismet -u && etc-update
note that by default when you run kismet with root you need to stand in a path belonging to the user you have set in kismet.conf for kismet to write log files with the config user name
bless |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
