Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
04-21-2004, 10:44 AM
|
#1
|
LQ Newbie
Registered: Mar 2004
Location: So Cal
Distribution: Laptop:Slackware 9.1 Desktop: Mandrake 9.2 Other: Knoppix STD .01
Posts: 9
Rep:
|
Kismet Problems :need help with kismet.conf source
I have the madwifi driver and im trying to run kismet but i get this error
Server options: none
Client options: none
Starting server...
Waiting for server to start before startuing UI...
Will drop privs to qbann4 (1001) gid 0
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
Source 0 (atheros_source): Enabling monitor mode for madwifi_g source interface ath0 channel 6...
Source 0 (atheros_source): Opening madwifi_g source interface ath0...
Spawned channelc control process 4292
Dropped privs to qbann4 (1001) gid 0
Allowing clients to fetch WEP keys.
Logging networks to Kismet-Apr-21-2004-1.network
Logging networks in CSV format to Kismet-Apr-21-2004-1.csv
Logging networks in XML format to Kismet-Apr-21-2004-1.xml
Logging cryptographically weak packets to Kismet-Apr-21-2004-1.weak
Logging cisco product information to Kismet-Apr-21-2004-1.cisco
Logging gps coordinates to Kismet-Apr-21-2004-1.gps
Logging data to Kismet-Apr-21-2004-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 /usr/local/etc/ap_manuf
Reading client manufacturer data and defaults from /usr/local/etc/client_manuf
FATAL: Dump file error: Unable to open dump file Kismet-Apr-21-2004-1.dump (Permission denied)
Sending termination request to channel control child 4292...
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 4292 to exit...
Kismet exiting.
does any one know the real source line for madwifi plz help ?
|
|
|
04-21-2004, 12:38 PM
|
#2
|
Senior Member
Registered: Jan 2002
Location: Southern California
Distribution: Slackware
Posts: 1,880
Rep:
|
Looks like Kismet is erroring because it can't write to the log file: "(FATAL: Dump file error: Unable to open dump file Kismet-Apr-21-2004-1.dump (Permission denied)"
Try setting the user ID to your normal user account in kismet.conf:
suiduser=username
|
|
|
04-21-2004, 03:39 PM
|
#3
|
LQ Newbie
Registered: Mar 2004
Location: So Cal
Distribution: Laptop:Slackware 9.1 Desktop: Mandrake 9.2 Other: Knoppix STD .01
Posts: 9
Original Poster
Rep:
|
i tried my reguler user account it didnt work
|
|
|
04-21-2004, 04:07 PM
|
#4
|
Senior Member
Registered: Jan 2002
Location: Southern California
Distribution: Slackware
Posts: 1,880
Rep:
|
The only other thing I can think of is that the interface has to be up. I can't remember the exact error. So, iwconfig ath0 up, then run kismet.
Still, I'd focus on the permissions message. Does running Kismet as root produce the same error?
|
|
|
04-24-2004, 03:09 PM
|
#5
|
Member
Registered: Oct 2003
Location: Ireland
Distribution: Mandrake 9.2
Posts: 32
Rep:
|
root
I would say to try running kismet as root
|
|
|
04-24-2004, 09:16 PM
|
#6
|
Member
Registered: Oct 2003
Distribution: Slackware
Posts: 388
Rep:
|
>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.
|
|
|
04-26-2004, 05:12 PM
|
#7
|
LQ Newbie
Registered: Mar 2004
Location: So Cal
Distribution: Laptop:Slackware 9.1 Desktop: Mandrake 9.2 Other: Knoppix STD .01
Posts: 9
Original Poster
Rep:
|
well fixed thanks for the help anyways.
|
|
|
All times are GMT -5. The time now is 06:38 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|