Kismet Wireless

Kismet Forums


Posted by:sfreire
Subject:Atheros 5212 - Fatal - Now ok!
Date:12:55:47 18/05/2006

OK fellows, i have defined a user Kismet and start Kismet as sudo from kismet's home, all work fine.

Thanks !

> > > Hi all, anyone have some idea about the following error ?
> >
> > > FATAL: Failed to retrieve list of private ioctls 7:Argument list too long
> >
> > Sigh, once again:
> >
> > Install the latest kismet if you expect the latest drivers to work.
> >
> > -m
> Thanks dragorn ! i passed that error,
> now i have the follow:
> FATAL: Dump file error: Unable to open dump file Kismet-May-12-2006-1.dump (Permission denied)
> where the kismet try write thats files ?
> look the output ...
> sh-2.05b$ sudo ./kismet
> Server options: none
> Client options: none
> Starting server...
> Waiting for server to start before starting UI...
> Will drop privs to sfreire (1001) gid 1001
> No specific sources given to be enabled, all will be enabled.
> Enabling channel hopping.
> Enabling channel splitting.
> Source 0 (Atheros): Enabling monitor mode for madwifi_g source interface wifi0 channel 6...
> NOTICE: Created Madwifi-NG VAP kis1
> WARNING: wifi0 appears to be using Madwifi-NG. Some versions of the Madwifi-NG drivers have problems in monitor mode, especially if non-monitor VAPs are active. If you experience problems, be sure to try the latest versions of Madwifi-NG and remove other VAPs
> Source 0 (Atheros): Opening madwifi_g source interface kis1...
> Spawned channelc control process 3716
> Dropped privs to sfreire (1001) gid 1001
> Allowing clients to fetch WEP keys.
> WARNING: Disabling GPS logging.
> Logging networks to
> Logging networks in CSV format to Kismet-May-12-2006-1.csv
> Logging networks in XML format to Kismet-May-12-2006-1.xml
> Logging cryptographically weak packets to Kismet-May-12-2006-1.weak
> Logging cisco product information to
> Logging data to Kismet-May-12-2006-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
> Using network-classifier based data encryption detection
> FATAL: Dump file error: Unable to open dump file Kismet-May-12-2006-1.dump (Permission denied)
> Sending termination request to channel control child 3716...
> Waiting for channel control child 3716 to exit...
> Kismet exiting.

Reply to this message