Kismet Problems

I'm trying to get Kismet running, and I keep getting an error. I'm running FC4 on an IBM T41 with the ibm abg card and madwifi. I have airsnort installed, but don't know if it's tied into kismet, as i've never used this before and am trying to figure this out. I'm running kismet as root. If i try as user, it fails much earlier with permissions issues (as root, i get the permission issue with the DUMP file).

Quote:

---

Server options: none
Client options: none
Starting server...
Waiting for server to start before starting UI...
Will drop privs to Josh (500) gid 500
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
Source 0 (Levin): Enabling monitor mode for madwifi_g source interface ath0 channel 6...
Source 0 (Levin): Opening madwifi_g source interface ath0...
Spawned channelc control process 4172
Dropped privs to Josh (500) gid 500
Allowing clients to fetch WEP keys.
WARNING: Disabling GPS logging.
Logging networks to Kismet-Sep-21-2005-1.network
Logging networks in CSV format to Kismet-Sep-21-2005-1.csv
Logging networks in XML format to Kismet-Sep-21-2005-1.xml
Logging cryptographically weak packets to Kismet-Sep-21-2005-1.weak
Logging cisco product information to Kismet-Sep-21-2005-1.cisco
Logging data to Kismet-Sep-21-2005-1.dump
Writing data files to disk every 300 seconds.
Mangling encrypted and fuzzy data packets.
Tracking probe responses and associating probe networks.
Reading AP manufacturer data and defaults from /etc/ap_manuf
Reading client manufacturer data and defaults from /etc/client_manuf
Using network-classifier based data encryption detection
FATAL: Dump file error: Unable to open dump file Kismet-Sep-21-2005-1.dump (Permission denied)
Sending termination request to channel control child 4172...
WARNING: Sometimes cards don't always come out of monitor mode
cleanly. If your card is not fully working, you may need to
restart or reconfigure it for normal operation.
Waiting for channel control child 4172 to exit...
Kismet exiting.

---

So, tried moving kismet_server.pid to home/Josh/kismet...then I get this error:

Quote:

---

No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
Source 0 (Levin): Enabling monitor mode for madwifi_g source interface ath0 channel 6...
FATAL: Failed to set private ioctl 'mode': Operation not permitted

---

First off, you have to run kismet as root. The config specifies to which user it switches after the root-requiring things have been done. Secondly, have you looked at kismet's config? I'm fairly certain that you have to specify where the dump and log files go from there. It was a while ago when I first set my kismet up, so I can't remember exactly what I had to setup. I'll take a look at my config when I get on my lappie if you can't figure it out. 8)

>i tried my reguler user account it didnt work
Saying "it didn't work" is usually unhelpful, say exactly what happened, if it produced to same error as before then say "it produced the same error as before".

Set kismet to change to your normal userid and start it in your normal users home directly not in /root. You have to be the root user when you start it (unless you installed it suid root) but you have to be in a directory your normal user can write to.

mine works now....gud luck