Kismet Wireless

Kismet Forums

 

Posted by:sauravb
Subject:Unable to capture any packet
Date:06:49:14 12/02/2008

> > > Hi,
> > >
> > > I am not able to capture any packet using kismet-2006-04-R1.
> > >
> > > My setup is -
> > >
> > > Gateworks BSP 0.7
> > > Buildroot
> > > madwifi-r3008
> > > Linux-2.6.21.4
> > > Senao radios
> > ...
> > > Please note that I used the same kismet version successfully with -
> > > madwifi-0.9.2
> > > Debian sarge 3.0
> > > Linux-2.6.18
> > >
> > > With the OS migration it is no more working.
> > > I can not change the kismet version as I have some enhancements on it for my project.
> >
> >
> > You have two choices :
> > A) Either revert back to the previous system setup that worked.
> > B) Port your changes to the current kismet version. The one you are using, which probably are 2005-04-R1 since there isn't a 2006-04-R1 release, is atleast 4 releases behind. Changes and fixes for the various releases are listed here : http://www.kismetwireless.net/CHANGELOG
> >
> > Dutch
> Dutch, thanks for the reply.
> But with kismet-2007-10-R1 I am getting segmentation fault.
> Is anybody on this forum using kismet-2007-10-R1 with buildroot?
>
> **********************************************************************************************
>
> [root@saurav]# ./kismet_server -f kismet.conf
>
> Using alternate config file: kismet.conf
>
> Will drop privs to saurav (1001) gid 1001
>
> No specific sources given to be enabled, all will be enabled.
>
> Enabling channel hopping.
>
> Enabling channel splitting.
>
> Dropped privs to saurav (1001) gid 1001
>
> WARNING: Disabling GPS logging.
>
> Logging networks to Kismet.network
>
> Logging networks in CSV format to Kismet.csv
>
> Logging networks in XML format to Kismet.xml
>
> Logging cryptographically weak packets to Kismet.weak
>
> Logging cisco product information to Kismet.cisco
>
> Tracking probe responses and associating probe networks.
>
> Reading AP manufacturer data and defaults from /home/saurav/ap_manuf
>
> Reading client manufacturer data and defaults from /home/saurav/client_manuf
>
> Segmentation fault
>
> ***********************************************************************************************
> Please let me know.
>
> Thanks & Regards,
> Saurav

If I run only "kismet_server --help" then also I am getting segmentation fault.
Anybody using kismet-2007-10-R1 with buildroot?
Please let me know.

Thanks & Regards,
Saurav

*******************************************************************************
[root@saurav mnt]# ./kismet_server --help
Usage: ./kismet_server [OPTION]
Most (or all) of these options can (and should) be configured via the
kismet.conf global config file, but can be overridden here.
-I, --initial-channel <n:c> Initial channel to monitor on (default: 6)
Format capname:channel
-x, --force-channel-hop Forcibly enable the channel hopper
-X, --force-no-channel-hop Forcibly disable the channel hopper
-t, --log-title <title> Custom log file title
-n, --no-logging No logging (only process packets)
-f, --config-file <file> Use alternate config file
-c, --capture-source <src> Packet capture source line (type,interface,name)
-C, --enable-capture-sources Comma separated list of named packet sources to u
se.
-l, --log-types <types> Comma separated list of types to log,
(ie, dump,cisco,weak,network,gps)
-d, --dump-type <type> Dumpfile type (wiretap)
-m, --max-packets <num> Maximum number of packets before starting new dum
p
-q, --quiet Don't play sounds
-g, --gps <host:port> GPS server (host:port or off)
-p, --port <port> TCPIP server port for GUI connections
-a, --allowed-hosts <hosts> Comma separated list of hosts allowed to connect
-b, --bind-address <address> Bind to this address. Default INADDR_ANY
-r, --retain-monitor Leave card in monitor mode on exit
-s, --silent Don't send any output to console.
-N, --server-name Server name
--daemonize Background server in daemon mode
-v, --version Kismet version
-h, --help What do you think you're reading?
Segmentation fault
[root@saurav mnt]#
********************************************************************************


Reply to this message