Bonjour à tous,

Ca faisait un petit temps que j'avais pas réinstallé kismet, et je ne me rappel pas avoir
rencontré de problèmes la dernière fois.

Voilà ce qui arrive lorsque je tente de le lancer...
[macwire@localhost root]$ su -c "kismet"
Password: 
Launching kismet_server: /usr/bin/kismet_server
Will drop privs to macwire (500) gid 500
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 (MyWlan): Enabling monitor mode for iwl3945 source interface wlan0 channel 6...
Source 0 (MyWlan): Opening iwl3945 source interface wlan0...
Spawned channel control process 3652
Dropped privs to macwire (500) gid 500
Will attempt to put networkmanager to sleep...
Allowing clients to fetch WEP keys.
WARNING:  Disabling GPS logging.
SSID cloak file did not exist, it will be created.
FATAL: Could not open SSID track file '/home/macwire/ssid_map' for writing: Permission denied
Sending termination request to channel control child 3652...
WARNING: Error disabling monitor mode: mode set ioctl failed 16:Device or resource busy
WARNING: MyWlan (wlan0) left in an unknown state.  You may need to manually
         restart or reconfigure it for normal operation.
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 3652 to exit...
Trying to wake networkmanager back up...
WARNING: Failed to connect to DBUS system, will not be able to control networkmanager: Failed to connect to socket /var/run/dbus/system_bus_socket: Permission denied
WARNING: Failed to send 'wake' command to networkmanager via DBUS, NM may still be inactive.Kismet exiting.
Done.
Désolé pour le texte mais entre des permissions refusée et des warning par ci par là, il m'est difficile de trier l'information qui vous sera utile 🙂

Pour info dans le kismet.conf, j'ai modifier deux lignes

suiduser=macwire
et
source=iwl3945,wlan0,MyWlan

Pour MyWlan je ne vois vraiment pas ce que c'est j'ai juste copié ce que j'ai vu sur un site mais j'ai donc recopier bêtement un truc, si quelqu'un peu m'expliquer ce que c'est ?!
Ma petite idée c'est que c'est un alias

Merci et bonne journée
Je up déjà

J'ai tenter de désactiver selinux pour tester mais apparemment ce n'est pas ça non plus.

quelqu'un pourrais m'éclairer ?
Merci
7 jours plus tard
je suis le seul qui n'est pas en vacances ou qwé 😃
Salut.

Si t'as pas de réponses, c'est que les gens ne savent pas te répondre,..
Maintenant pour ton problème, regarde les messages d'erreur, tu as des problèmes de droits d'accès à tes fichiers...
Essaye plutôt : 
$ su -
# kismet
bonjour eddy,

je suis content que tu me réponde ! 🙂

Voilà avant de répondre à ta suggestion

j'ai essayé un d'activer le mode monitoring de ma carte ce qui donne ceci :
airmon-ng start wlan0


Found 4 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!

PID    Name
1463    avahi-daemon
1464    avahi-daemon
1668    NetworkManager
1675    wpa_supplicant


Interface    Chipset        Driver

wlan0        Intel 3945ABG    iwl3945 - [phy0]
                (monitor mode enabled on mon0)
Ensuite je fais un kismet en root et cela donne:
[root@localhost ~]# kismet
Launching kismet_server: /usr/bin/kismet_server
Will drop privs to macwire (500) gid 500
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 (iwl3945): Enabling monitor mode for iwl3945 source interface wlan0 channel 6...
Source 0 (iwl3945): Opening iwl3945 source interface wlan0...
Spawned channel control process 2864
Dropped privs to macwire (500) gid 500
Will attempt to put networkmanager to sleep...
Allowing clients to fetch WEP keys.
WARNING:  Disabling GPS logging.
Logging networks to /var/log/kismet/Kismet-Aug-01-2009-1.network
Logging networks in CSV format to /var/log/kismet/Kismet-Aug-01-2009-1.csv
Logging networks in XML format to /var/log/kismet/Kismet-Aug-01-2009-1.xml
Logging cryptographically weak packets to /var/log/kismet/Kismet-Aug-01-2009-1.weak
Logging cisco product information to /var/log/kismet/Kismet-Aug-01-2009-1.cisco
Logging data to /var/log/kismet/Kismet-Aug-01-2009-1.dump
Writing data files to disk every 300 seconds.
Mangling encrypted and fuzzy data packets.
Tracking probe responses and associating probe networks.
WARNING:  Unable to open '/etc/kismet/ap_manuf' for reading (Permission denied), AP manufacturers and defaults will not be detected.
WARNING:  Unable to open '/etc/kismet/client_manuf' for reading (Permission denied), client manufacturers will not be detected.
Using network-classifier based data encryption detection
Not tracking duplicate IVs
Putting networkmanager to sleep...
Dump file format: wiretap (local code) dump
Gathering packets...
Launched client, pid 2910
Launching kismet_client: /usr/bin/kismet_client
FATAL:  Could not connect to localhost:2501.
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...
Didn't see any weak encryption packets, unlinking weak file
Sending termination request to channel control child 2864...
Waiting for channel control child 2864 to exit...
WARNING: Error disabling monitor mode: mode set ioctl failed 16:Device or resource busy
WARNING: iwl3945 (wlan0) left in an unknown state.  You may need to manually
         restart or reconfigure it for normal operation.
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...
Kismet exiting.
Done.
Donc networkmanager pose des problème de conflits ainsi que les autres cités également.
D'après toi comment dois je procéder ?

Un grand merci
12 jours plus tard
c'est bon résolu,
j'ai désactiver networkmanager et ça roule
sorry du dérangement 🙂
De rien,

bon à savoir par rapport à NM....

++