Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've been trying to run kismet and nothing really happens. It's able to get my card into monitor mode but I don't really know what's up. I'm running fedora 10 with atheros 5007 chipset and just installed kismet from the repository. What is the difference between the kismet server and kismet client. Do I have both of them? Do both of them run when i do "sudo kismet"? here is the output after doing "sudo kismet":
Launching kismet_server: /usr/bin/kismet_server
Will drop privs to kismet (494) gid 491
No specific sources given to be enabled, all will be enabled.
Non-RFMon VAPs will be destroyed on multi-vap interfaces (ie, madwifi-ng)
Enabling channel hopping.
Enabling channel splitting.
NOTICE: Disabling channel hopping, no enabled sources are able to change channel.
Source 0 (wifi): Enabling monitor mode for ath5k source interface wlan0 channel 6...
Source 0 (wifi): Opening ath5k source interface wlan0...
Spawned channel control process 3099
Dropped privs to kismet (494) gid 491
Will attempt to put networkmanager to sleep...
Allowing clients to fetch WEP keys.
WARNING: Disabling GPS logging.
Logging networks to /var/log/kismet/Kismet-Dec-24-2008-3.network
Logging networks in CSV format to /var/log/kismet/Kismet-Dec-24-2008-3.csv
Logging networks in XML format to /var/log/kismet/Kismet-Dec-24-2008-3.xml
Logging cryptographically weak packets to /var/log/kismet/Kismet-Dec-24-2008-3.weak
Logging cisco product information to /var/log/kismet/Kismet-Dec-24-2008-3.cisco
Logging data to /var/log/kismet/Kismet-Dec-24-2008-3.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/kismet/ap_manuf
Reading client manufacturer data and defaults from /etc/kismet/client_manuf
Using network-classifier based data encryption detection
Not tracking duplicate IVs
Putting networkmanager to sleep...
Dump file format: wiretap (local code) dump
Crypt file format: airsnort (weak packet) dump
Kismet 2008.05.R1 (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...
Launched client, pid 3101
Launching kismet_client: /usr/bin/kismet_client
NOTICE: configdir '/root/' does not exist, making it.
FATAL: Could not make configdir: File exists
Didn't see any weak encryption packets, unlinking weak file
Sending termination request to channel control child 3099...
Waiting for channel control child 3099 to exit...
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.
Trying to wake networkmanager back up...
What is happening here? Also I can't get my card back out of managed mode any insight there?
Please post your thread in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place. This thread is being closed because it is a duplicate.