🌐kismet
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet is a powerful security tool designed to detect, monitor and analyze wireless networks. It is an open-source tool, available on multiple platforms, including Linux, Windows, and macOS, and provides a comprehensive suite of features for wireless network security analysis.
Kismet can be used to detect a wide range of wireless network protocols, including Wi-Fi, Bluetooth, ZigBee, and many others. It has a powerful packet capture engine that can capture and decode wireless network packets in real-time, allowing security professionals to identify vulnerabilities and potential attacks. Additionally, it can also identify and locate rogue access points that may be used for malicious purposes.
One of the key features of Kismet is its ability to track and log wireless network activity. It can store data on all detected wireless networks, including information about the devices connected to them and the packets being transmitted. This data can be used for analysis, identifying patterns and trends, and detecting potential security threats.
Kismet also provides advanced visualization tools, allowing security professionals to view wireless network activity in real-time. It includes a range of visualizations, including heat maps, graphs, and charts, which can be used to identify areas of network congestion, potential security risks, and other issues.
Another important feature of Kismet is its ability to support multiple wireless network adapters simultaneously. This makes it possible to monitor and analyze multiple networks at the same time, providing a comprehensive view of wireless network activity across an organization.
Kismet also includes advanced security features, such as encryption and authentication support, to help ensure the security of wireless network traffic. It can also be used to test the security of wireless networks, including testing for vulnerabilities and weaknesses in network configurations.
Overall, Kismet is a powerful and flexible security tool that can provide organizations with comprehensive visibility and control over their wireless network security. Its open-source nature, combined with its broad range of features and ease of use, makes it a popular choice for security professionals and IT administrators alike.
Screenshots
kismetkismet_client
:~# kismet_client -h
Usage: kismet_client [OPTION]
*** Generic Options ***
-h, --help The obviouskismet_drone
:~# kismet_drone -h
Usage: kismet_drone [OPTION]
Nearly all of these options are run-time overrides for values in the
kismet.conf configuration file. Permanent changes should be made to
the configuration file.
*** Generic Options ***
-f, --config-file Use alternate configuration file
--no-line-wrap Turn of linewrapping of output
(for grep, speed, etc)
-s, --silent Turn off stdout output after setup phase
--daemonize Spawn detatched in the background
*** Kismet Remote Drone Options ***
--drone-listen Override Kismet drone listen options
*** Packet Capture Source Options ***
-c, --capture-source Specify a new packet capture source
(Identical syntax to the config file)
-C, --enable-capture-sources Enable capture sources (comma-separated
list of names or interfaces)kismet_server Usage Example
Start the Kismet server, using the wireless interface as the capture source (-c wlan0) and use the external GPSD option (–use-gpsd-gps):
:~# kismet_server -c wlan0 --use-gpsd-gps
ERROR: Kismet was started as root, NOT launching external control binary.
This is NOT the preferred method of starting Kismet as Kismet will
continue to run as root the entire time. Please read the README
file section about Installation & Security and be sure this is what
you want to do.
INFO: Reading from config file /etc/kismet/kismet.conf
INFO: No 'dronelisten' config line and no command line drone-listen
argument given, Kismet drone server will not be enabled.
INFO: Created alert tracker...
INFO: Creating device tracker...
INFO: Registered 80211 PHY as id
Packages and Binaries:
kismet
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet works with Wi-Fi interfaces, Bluetooth interfaces, some SDR (software defined radio) hardware like the RTLSDR, and other specialized capture hardware.
This is a metapackage containing the kismet tools.
Installed size: 24 KB
How to install: sudo apt install kismet
Dependencies:
kismet-capture-linux-bluetooth
kismet-capture-linux-wifi
kismet-capture-nrf-51822
kismet-capture-nrf-52840
kismet-capture-nrf-mousejack
kismet-capture-nxp-kw41z
kismet-capture-rz-killerbee
kismet-capture-ti-cc-2531
kismet-capture-ti-cc-2540
kismet-capture-ubertooth-one
kismet-core
kismet-logtools
python3-kismetcapturebtgeiger
python3-kismetcapturefreaklabszigbee
python3-kismetcapturertl433
python3-kismetcapturertladsb
python3-kismetcapturertlamr
kismet-capture-common
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet works with Wi-Fi interfaces, Bluetooth interfaces, some SDR (software defined radio) hardware like the RTLSDR, and other specialized capture hardware.
This package contains the debconf files for setuid capture binaries.
Installed size: 43 KB
How to install: sudo apt install kismet-capture-common
kismet-capture-linux-bluetooth
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet works with Wi-Fi interfaces, Bluetooth interfaces, some SDR (software defined radio) hardware like the RTLSDR, and other specialized capture hardware.
This package contains the Kismet Linux Bluetooth capture helper.
Installed size: 177 KB
How to install: sudo apt install kismet-capture-linux-bluetooth
kismet_cap_linux_bluetooth
:~# kismet_cap_linux_bluetooth -h
kismet_cap_linux_bluetooth is a capture driver for Kismet. Typically it is started
automatically by the Kismet server.
kismet_cap_linux_bluetooth supports sending data to a remote Kismet server
usage: kismet_cap_linux_bluetooth [options]
--connect [host]:[port] Connect to remote Kismet server on [host] and [port]; by
default this now uses the new websockets interface built
into the Kismet webserver on port 2501; to connect using
the legacy remote capture protocol, specify the '--tcp'
option and the appropriate port, by default port 3501.
--tcp Use the legacy TCP remote capture protocol, when combined
with the --connect option. The modern protocol uses
websockets built into the Kismet server and does not
need this option.
--ssl Use SSL to connect to a websocket-enabled Kismet server
--ssl-certificate [certfile] Use SSL to connect to a websocket-enabled Kismet server
and use the provided certificate authority certificate
to validate the server.
--user [username] Kismet username for a websockets-based remote capture
source. A username and password, or an API key, are
required for websockets mode. A username and password
are ONLY used in websockets mode.
--password [password] Kismet password for a websockets-based remote capture source.
A username and password, or an API key, are required for
websocket mode. A username and password are ONLY used in
websockets mode.
--apikey [api key] A Kismet API key for the 'datasource' role; this may be
supplied instead of a username and password for websockets
based remote capture. An API key is ONLY used in websockets
mode.
--endpoint [endpoint] An alternate endpoint for the websockets connection. By
default remote datasources are terminated at
/datasource/remote/remotesource.ws
This should typically only be changed when using a HTTP proxy
homing the Kismet service under a directory. Endpoints
should include the full path to the websocket endpoint, for
example:
--endpoint=/kismet/proxy/datasource/remote/remotesource.ws
--source [source def] Specify a source to send to the remote
Kismet server; only used in conjunction with remote capture.
--disable-retry Do not attempt to reconnect to a remote server if there is an
error; exit immediately. By default a remote capture will
attempt to reconnect indefinitely if the server is not
available.
--fixed-gps [lat,lon,alt] Set a fixed location for this capture (remote only),
accepts lat,lon,alt or lat,lon
--gps-name [name] Set an alternate GPS name for this source
--daemonize Background the capture tool and enter daemon mode.
--list List supported devices detected
--autodetect [uuid:optional] Look for a Kismet server in announcement mode, optionally
waiting for a specific server UUID to be seen. Requires
a Kismet server configured for announcement mode.kismet-capture-linux-wifi
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet works with Wi-Fi interfaces, Bluetooth interfaces, some SDR (software defined radio) hardware like the RTLSDR, and other specialized capture hardware.
This package contains the Kismet Linux Wi-Fi capture helper.
Installed size: 238 KB
How to install: sudo apt install kismet-capture-linux-wifi
Dependencies:
debconf | debconf-2.0
kismet-capture-common
libc6
libglib2.0-0
libnl-3-200
libnl-genl-3-200
libnm0
libpcap0.8
libprotobuf-c1
libwebsockets17
kismet_cap_linux_wifi
:~# kismet_cap_linux_wifi -h
kismet_cap_linux_wifi is a capture driver for Kismet. Typically it is started
automatically by the Kismet server.
kismet_cap_linux_wifi supports sending data to a remote Kismet server
usage: kismet_cap_linux_wifi [options]
--connect [host]:[port] Connect to remote Kismet server on [host] and [port]; by
default this now uses the new websockets interface built
into the Kismet webserver on port 2501; to connect using
the legacy remote capture protocol, specify the '--tcp'
option and the appropriate port, by default port 3501.
--tcp Use the legacy TCP remote capture protocol, when combined
with the --connect option. The modern protocol uses
websockets built into the Kismet server and does not
need this option.
--ssl Use SSL to connect to a websocket-enabled Kismet server
--ssl-certificate [certfile] Use SSL to connect to a websocket-enabled Kismet server
and use the provided certificate authority certificate
to validate the server.
--user [username] Kismet username for a websockets-based remote capture
source. A username and password, or an API key, are
required for websockets mode. A username and password
are ONLY used in websockets mode.
--password [password] Kismet password for a websockets-based remote capture source.
A username and password, or an API key, are required for
websocket mode. A username and password are ONLY used in
websockets mode.
--apikey [api key] A Kismet API key for the 'datasource' role; this may be
supplied instead of a username and password for websockets
based remote capture. An API key is ONLY used in websockets
mode.
--endpoint [endpoint] An alternate endpoint for the websockets connection. By
default remote datasources are terminated at
/datasource/remote/remotesource.ws
This should typically only be changed when using a HTTP proxy
homing the Kismet service under a directory. Endpoints
should include the full path to the websocket endpoint, for
example:
--endpoint=/kismet/proxy/datasource/remote/remotesource.ws
--source [source def] Specify a source to send to the remote
Kismet server; only used in conjunction with remote capture.
--disable-retry Do not attempt to reconnect to a remote server if there is an
error; exit immediately. By default a remote capture will
attempt to reconnect indefinitely if the server is not
available.
--fixed-gps [lat,lon,alt] Set a fixed location for this capture (remote only),
accepts lat,lon,alt or lat,lon
--gps-name [name] Set an alternate GPS name for this source
--daemonize Background the capture tool and enter daemon mode.
--list List supported devices detected
--autodetect [uuid:optional] Look for a Kismet server in announcement mode, optionally
waiting for a specific server UUID to be seen. Requires
a Kismet server configured for announcement mode.kismet-capture-nrf-51822
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet works with Wi-Fi interfaces, Bluetooth interfaces, some SDR (software defined radio) hardware like the RTLSDR, and other specialized capture hardware.
This package contains the NRF51822 BTLE Sniffer capture helper.
Installed size: 165 KB
How to install: sudo apt install kismet-capture-nrf-51822
kismet_cap_nrf_51822
:~# kismet_cap_nrf_51822 -h
kismet_cap_nrf_51822 is a capture driver for Kismet. Typically it is started
automatically by the Kismet server.
kismet_cap_nrf_51822 supports sending data to a remote Kismet server
usage: kismet_cap_nrf_51822 [options]
--connect [host]:[port] Connect to remote Kismet server on [host] and [port]; by
default this now uses the new websockets interface built
into the Kismet webserver on port 2501; to connect using
the legacy remote capture protocol, specify the '--tcp'
option and the appropriate port, by default port 3501.
--tcp Use the legacy TCP remote capture protocol, when combined
with the --connect option. The modern protocol uses
websockets built into the Kismet server and does not
need this option.
--ssl Use SSL to connect to a websocket-enabled Kismet server
--ssl-certificate [certfile] Use SSL to connect to a websocket-enabled Kismet server
and use the provided certificate authority certificate
to validate the server.
--user [username] Kismet username for a websockets-based remote capture
source. A username and password, or an API key, are
required for websockets mode. A username and password
are ONLY used in websockets mode.
--password [password] Kismet password for a websockets-based remote capture source.
A username and password, or an API key, are required for
websocket mode. A username and password are ONLY used in
websockets mode.
--apikey [api key] A Kismet API key for the 'datasource' role; this may be
supplied instead of a username and password for websockets
based remote capture. An API key is ONLY used in websockets
mode.
--endpoint [endpoint] An alternate endpoint for the websockets connection. By
default remote datasources are terminated at
/datasource/remote/remotesource.ws
This should typically only be changed when using a HTTP proxy
homing the Kismet service under a directory. Endpoints
should include the full path to the websocket endpoint, for
example:
--endpoint=/kismet/proxy/datasource/remote/remotesource.ws
--source [source def] Specify a source to send to the remote
Kismet server; only used in conjunction with remote capture.
--disable-retry Do not attempt to reconnect to a remote server if there is an
error; exit immediately. By default a remote capture will
attempt to reconnect indefinitely if the server is not
available.
--fixed-gps [lat,lon,alt] Set a fixed location for this capture (remote only),
accepts lat,lon,alt or lat,lon
--gps-name [name] Set an alternate GPS name for this source
--daemonize Background the capture tool and enter daemon mode.
--list List supported devices detected
--autodetect [uuid:optional] Look for a Kismet server in announcement mode, optionally
waiting for a specific server UUID to be seen. Requires
a Kismet server configured for announcement mode.kismet-capture-nrf-52840
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet works with Wi-Fi interfaces, Bluetooth interfaces, some SDR (software defined radio) hardware like the RTLSDR, and other specialized capture hardware.
This package contains the NRF52840 BTLE Sniffer capture helper.
Installed size: 165 KB
How to install: sudo apt install kismet-capture-nrf-52840
kismet_cap_nrf_52840
:~# kismet_cap_nrf_52840 -h
kismet_cap_nrf_52840 is a capture driver for Kismet. Typically it is started
automatically by the Kismet server.
kismet_cap_nrf_52840 supports sending data to a remote Kismet server
usage: kismet_cap_nrf_52840 [options]
--connect [host]:[port] Connect to remote Kismet server on [host] and [port]; by
default this now uses the new websockets interface built
into the Kismet webserver on port 2501; to connect using
the legacy remote capture protocol, specify the '--tcp'
option and the appropriate port, by default port 3501.
--tcp Use the legacy TCP remote capture protocol, when combined
with the --connect option. The modern protocol uses
websockets built into the Kismet server and does not
need this option.
--ssl Use SSL to connect to a websocket-enabled Kismet server
--ssl-certificate [certfile] Use SSL to connect to a websocket-enabled Kismet server
and use the provided certificate authority certificate
to validate the server.
--user [username] Kismet username for a websockets-based remote capture
source. A username and password, or an API key, are
required for websockets mode. A username and password
are ONLY used in websockets mode.
--password [password] Kismet password for a websockets-based remote capture source.
A username and password, or an API key, are required for
websocket mode. A username and password are ONLY used in
websockets mode.
--apikey [api key] A Kismet API key for the 'datasource' role; this may be
supplied instead of a username and password for websockets
based remote capture. An API key is ONLY used in websockets
mode.
--endpoint [endpoint] An alternate endpoint for the websockets connection. By
default remote datasources are terminated at
/datasource/remote/remotesource.ws
This should typically only be changed when using a HTTP proxy
homing the Kismet service under a directory. Endpoints
should include the full path to the websocket endpoint, for
example:
--endpoint=/kismet/proxy/datasource/remote/remotesource.ws
--source [source def] Specify a source to send to the remote
Kismet server; only used in conjunction with remote capture.
--disable-retry Do not attempt to reconnect to a remote server if there is an
error; exit immediately. By default a remote capture will
attempt to reconnect indefinitely if the server is not
available.
--fixed-gps [lat,lon,alt] Set a fixed location for this capture (remote only),
accepts lat,lon,alt or lat,lon
--gps-name [name] Set an alternate GPS name for this source
--daemonize Background the capture tool and enter daemon mode.
--list List supported devices detected
--autodetect [uuid:optional] Look for a Kismet server in announcement mode, optionally
waiting for a specific server UUID to be seen. Requires
a Kismet server configured for announcement mode.kismet-capture-nrf-mousejack
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet works with Wi-Fi interfaces, Bluetooth interfaces, some SDR (software defined radio) hardware like the RTLSDR, and other specialized capture hardware.
This package contains the Kismet nRF MouseJack capture helper.
Installed size: 169 KB
How to install: sudo apt install kismet-capture-nrf-mousejack
Dependencies:
debconf | debconf-2.0
kismet-capture-common
libc6
libprotobuf-c1
libusb-1.0-0
libwebsockets17
kismet_cap_nrf_mousejack
:~# kismet_cap_nrf_mousejack -h
kismet_cap_nrf_mousejack is a capture driver for Kismet. Typically it is started
automatically by the Kismet server.
kismet_cap_nrf_mousejack supports sending data to a remote Kismet server
usage: kismet_cap_nrf_mousejack [options]
--connect [host]:[port] Connect to remote Kismet server on [host] and [port]; by
default this now uses the new websockets interface built
into the Kismet webserver on port 2501; to connect using
the legacy remote capture protocol, specify the '--tcp'
option and the appropriate port, by default port 3501.
--tcp Use the legacy TCP remote capture protocol, when combined
with the --connect option. The modern protocol uses
websockets built into the Kismet server and does not
need this option.
--ssl Use SSL to connect to a websocket-enabled Kismet server
--ssl-certificate [certfile] Use SSL to connect to a websocket-enabled Kismet server
and use the provided certificate authority certificate
to validate the server.
--user [username] Kismet username for a websockets-based remote capture
source. A username and password, or an API key, are
required for websockets mode. A username and password
are ONLY used in websockets mode.
--password [password] Kismet password for a websockets-based remote capture source.
A username and password, or an API key, are required for
websocket mode. A username and password are ONLY used in
websockets mode.
--apikey [api key] A Kismet API key for the 'datasource' role; this may be
supplied instead of a username and password for websockets
based remote capture. An API key is ONLY used in websockets
mode.
--endpoint [endpoint] An alternate endpoint for the websockets connection. By
default remote datasources are terminated at
/datasource/remote/remotesource.ws
This should typically only be changed when using a HTTP proxy
homing the Kismet service under a directory. Endpoints
should include the full path to the websocket endpoint, for
example:
--endpoint=/kismet/proxy/datasource/remote/remotesource.ws
--source [source def] Specify a source to send to the remote
Kismet server; only used in conjunction with remote capture.
--disable-retry Do not attempt to reconnect to a remote server if there is an
error; exit immediately. By default a remote capture will
attempt to reconnect indefinitely if the server is not
available.
--fixed-gps [lat,lon,alt] Set a fixed location for this capture (remote only),
accepts lat,lon,alt or lat,lon
--gps-name [name] Set an alternate GPS name for this source
--daemonize Background the capture tool and enter daemon mode.
--list List supported devices detected
--autodetect [uuid:optional] Look for a Kismet server in announcement mode, optionally
waiting for a specific server UUID to be seen. Requires
a Kismet server configured for announcement mode.kismet-capture-nxp-kw41z
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet works with Wi-Fi interfaces, Bluetooth interfaces, some SDR (software defined radio) hardware like the RTLSDR, and other specialized capture hardware.
This package contains the Kismet NXP KW41Z BTLE and Zigbee Sniffer capture helper.
Installed size: 169 KB
How to install: sudo apt install kismet-capture-nxp-kw41z
kismet_cap_nxp_kw41z
:~# kismet_cap_nxp_kw41z -h
kismet_cap_nxp_kw41z is a capture driver for Kismet. Typically it is started
automatically by the Kismet server.
kismet_cap_nxp_kw41z supports sending data to a remote Kismet server
usage: kismet_cap_nxp_kw41z [options]
--connect [host]:[port] Connect to remote Kismet server on [host] and [port]; by
default this now uses the new websockets interface built
into the Kismet webserver on port 2501; to connect using
the legacy remote capture protocol, specify the '--tcp'
option and the appropriate port, by default port 3501.
--tcp Use the legacy TCP remote capture protocol, when combined
with the --connect option. The modern protocol uses
websockets built into the Kismet server and does not
need this option.
--ssl Use SSL to connect to a websocket-enabled Kismet server
--ssl-certificate [certfile] Use SSL to connect to a websocket-enabled Kismet server
and use the provided certificate authority certificate
to validate the server.
--user [username] Kismet username for a websockets-based remote capture
source. A username and password, or an API key, are
required for websockets mode. A username and password
are ONLY used in websockets mode.
--password [password] Kismet password for a websockets-based remote capture source.
A username and password, or an API key, are required for
websocket mode. A username and password are ONLY used in
websockets mode.
--apikey [api key] A Kismet API key for the 'datasource' role; this may be
supplied instead of a username and password for websockets
based remote capture. An API key is ONLY used in websockets
mode.
--endpoint [endpoint] An alternate endpoint for the websockets connection. By
default remote datasources are terminated at
/datasource/remote/remotesource.ws
This should typically only be changed when using a HTTP proxy
homing the Kismet service under a directory. Endpoints
should include the full path to the websocket endpoint, for
example:
--endpoint=/kismet/proxy/datasource/remote/remotesource.ws
--source [source def] Specify a source to send to the remote
Kismet server; only used in conjunction with remote capture.
--disable-retry Do not attempt to reconnect to a remote server if there is an
error; exit immediately. By default a remote capture will
attempt to reconnect indefinitely if the server is not
available.
--fixed-gps [lat,lon,alt] Set a fixed location for this capture (remote only),
accepts lat,lon,alt or lat,lon
--gps-name [name] Set an alternate GPS name for this source
--daemonize Background the capture tool and enter daemon mode.
--list List supported devices detected
--autodetect [uuid:optional] Look for a Kismet server in announcement mode, optionally
waiting for a specific server UUID to be seen. Requires
a Kismet server configured for announcement mode.kismet-capture-rz-killerbee
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet works with Wi-Fi interfaces, Bluetooth interfaces, some SDR (software defined radio) hardware like the RTLSDR, and other specialized capture hardware.
This package contains the Kismet Killerbee Sniffer capture helper.
Installed size: 169 KB
How to install: sudo apt install kismet-capture-rz-killerbee
Dependencies:
debconf | debconf-2.0
kismet-capture-common
libc6
libprotobuf-c1
libusb-1.0-0
libwebsockets17
kismet_cap_rz_killerbee
:~# kismet_cap_rz_killerbee -h
kismet_cap_rz_killerbee is a capture driver for Kismet. Typically it is started
automatically by the Kismet server.
kismet_cap_rz_killerbee supports sending data to a remote Kismet server
usage: kismet_cap_rz_killerbee [options]
--connect [host]:[port] Connect to remote Kismet server on [host] and [port]; by
default this now uses the new websockets interface built
into the Kismet webserver on port 2501; to connect using
the legacy remote capture protocol, specify the '--tcp'
option and the appropriate port, by default port 3501.
--tcp Use the legacy TCP remote capture protocol, when combined
with the --connect option. The modern protocol uses
websockets built into the Kismet server and does not
need this option.
--ssl Use SSL to connect to a websocket-enabled Kismet server
--ssl-certificate [certfile] Use SSL to connect to a websocket-enabled Kismet server
and use the provided certificate authority certificate
to validate the server.
--user [username] Kismet username for a websockets-based remote capture
source. A username and password, or an API key, are
required for websockets mode. A username and password
are ONLY used in websockets mode.
--password [password] Kismet password for a websockets-based remote capture source.
A username and password, or an API key, are required for
websocket mode. A username and password are ONLY used in
websockets mode.
--apikey [api key] A Kismet API key for the 'datasource' role; this may be
supplied instead of a username and password for websockets
based remote capture. An API key is ONLY used in websockets
mode.
--endpoint [endpoint] An alternate endpoint for the websockets connection. By
default remote datasources are terminated at
/datasource/remote/remotesource.ws
This should typically only be changed when using a HTTP proxy
homing the Kismet service under a directory. Endpoints
should include the full path to the websocket endpoint, for
example:
--endpoint=/kismet/proxy/datasource/remote/remotesource.ws
--source [source def] Specify a source to send to the remote
Kismet server; only used in conjunction with remote capture.
--disable-retry Do not attempt to reconnect to a remote server if there is an
error; exit immediately. By default a remote capture will
attempt to reconnect indefinitely if the server is not
available.
--fixed-gps [lat,lon,alt] Set a fixed location for this capture (remote only),
accepts lat,lon,alt or lat,lon
--gps-name [name] Set an alternate GPS name for this source
--daemonize Background the capture tool and enter daemon mode.
--list List supported devices detected
--autodetect [uuid:optional] Look for a Kismet server in announcement mode, optionally
waiting for a specific server UUID to be seen. Requires
a Kismet server configured for announcement mode.kismet-capture-ti-cc-2531
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet works with Wi-Fi interfaces, Bluetooth interfaces, some SDR (software defined radio) hardware like the RTLSDR, and other specialized capture hardware.
This package contains the Kismet TICC2531 802.15.4 Zigbee Sniffer capture helper.
Installed size: 169 KB
How to install: sudo apt install kismet-capture-ti-cc-2531
Dependencies:
debconf | debconf-2.0
kismet-capture-common
libc6
libprotobuf-c1
libusb-1.0-0
libwebsockets17
kismet_cap_ti_cc_2531
:~# kismet_cap_ti_cc_2531 -h
kismet_cap_ti_cc_2531 is a capture driver for Kismet. Typically it is started
automatically by the Kismet server.
kismet_cap_ti_cc_2531 supports sending data to a remote Kismet server
usage: kismet_cap_ti_cc_2531 [options]
--connect [host]:[port] Connect to remote Kismet server on [host] and [port]; by
default this now uses the new websockets interface built
into the Kismet webserver on port 2501; to connect using
the legacy remote capture protocol, specify the '--tcp'
option and the appropriate port, by default port 3501.
--tcp Use the legacy TCP remote capture protocol, when combined
with the --connect option. The modern protocol uses
websockets built into the Kismet server and does not
need this option.
--ssl Use SSL to connect to a websocket-enabled Kismet server
--ssl-certificate [certfile] Use SSL to connect to a websocket-enabled Kismet server
and use the provided certificate authority certificate
to validate the server.
--user [username] Kismet username for a websockets-based remote capture
source. A username and password, or an API key, are
required for websockets mode. A username and password
are ONLY used in websockets mode.
--password [password] Kismet password for a websockets-based remote capture source.
A username and password, or an API key, are required for
websocket mode. A username and password are ONLY used in
websockets mode.
--apikey [api key] A Kismet API key for the 'datasource' role; this may be
supplied instead of a username and password for websockets
based remote capture. An API key is ONLY used in websockets
mode.
--endpoint [endpoint] An alternate endpoint for the websockets connection. By
default remote datasources are terminated at
/datasource/remote/remotesource.ws
This should typically only be changed when using a HTTP proxy
homing the Kismet service under a directory. Endpoints
should include the full path to the websocket endpoint, for
example:
--endpoint=/kismet/proxy/datasource/remote/remotesource.ws
--source [source def] Specify a source to send to the remote
Kismet server; only used in conjunction with remote capture.
--disable-retry Do not attempt to reconnect to a remote server if there is an
error; exit immediately. By default a remote capture will
attempt to reconnect indefinitely if the server is not
available.
--fixed-gps [lat,lon,alt] Set a fixed location for this capture (remote only),
accepts lat,lon,alt or lat,lon
--gps-name [name] Set an alternate GPS name for this source
--daemonize Background the capture tool and enter daemon mode.
--list List supported devices detected
--autodetect [uuid:optional] Look for a Kismet server in announcement mode, optionally
waiting for a specific server UUID to be seen. Requires
a Kismet server configured for announcement mode.kismet-capture-ti-cc-2540
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet works with Wi-Fi interfaces, Bluetooth interfaces, some SDR (software defined radio) hardware like the RTLSDR, and other specialized capture hardware.
This package contains the Kismet TICC2540 BTLE Sniffer capture helper.
Installed size: 169 KB
How to install: sudo apt install kismet-capture-ti-cc-2540
Dependencies:
debconf | debconf-2.0
kismet-capture-common
libc6
libprotobuf-c1
libusb-1.0-0
libwebsockets17
kismet_cap_ti_cc_2540
:~# kismet_cap_ti_cc_2540 -h
kismet_cap_ti_cc_2540 is a capture driver for Kismet. Typically it is started
automatically by the Kismet server.
kismet_cap_ti_cc_2540 supports sending data to a remote Kismet server
usage: kismet_cap_ti_cc_2540 [options]
--connect [host]:[port] Connect to remote Kismet server on [host] and [port]; by
default this now uses the new websockets interface built
into the Kismet webserver on port 2501; to connect using
the legacy remote capture protocol, specify the '--tcp'
option and the appropriate port, by default port 3501.
--tcp Use the legacy TCP remote capture protocol, when combined
with the --connect option. The modern protocol uses
websockets built into the Kismet server and does not
need this option.
--ssl Use SSL to connect to a websocket-enabled Kismet server
--ssl-certificate [certfile] Use SSL to connect to a websocket-enabled Kismet server
and use the provided certificate authority certificate
to validate the server.
--user [username] Kismet username for a websockets-based remote capture
source. A username and password, or an API key, are
required for websockets mode. A username and password
are ONLY used in websockets mode.
--password [password] Kismet password for a websockets-based remote capture source.
A username and password, or an API key, are required for
websocket mode. A username and password are ONLY used in
websockets mode.
--apikey [api key] A Kismet API key for the 'datasource' role; this may be
supplied instead of a username and password for websockets
based remote capture. An API key is ONLY used in websockets
mode.
--endpoint [endpoint] An alternate endpoint for the websockets connection. By
default remote datasources are terminated at
/datasource/remote/remotesource.ws
This should typically only be changed when using a HTTP proxy
homing the Kismet service under a directory. Endpoints
should include the full path to the websocket endpoint, for
example:
--endpoint=/kismet/proxy/datasource/remote/remotesource.ws
--source [source def] Specify a source to send to the remote
Kismet server; only used in conjunction with remote capture.
--disable-retry Do not attempt to reconnect to a remote server if there is an
error; exit immediately. By default a remote capture will
attempt to reconnect indefinitely if the server is not
available.
--fixed-gps [lat,lon,alt] Set a fixed location for this capture (remote only),
accepts lat,lon,alt or lat,lon
--gps-name [name] Set an alternate GPS name for this source
--daemonize Background the capture tool and enter daemon mode.
--list List supported devices detected
--autodetect [uuid:optional] Look for a Kismet server in announcement mode, optionally
waiting for a specific server UUID to be seen. Requires
a Kismet server configured for announcement mode.kismet-capture-ubertooth-one
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet works with Wi-Fi interfaces, Bluetooth interfaces, some SDR (software defined radio) hardware like the RTLSDR, and other specialized capture hardware.
This package contains the Kismet Ubertooth One BT Sniffer capture helper.
Installed size: 165 KB
How to install: sudo apt install kismet-capture-ubertooth-one
Dependencies:
debconf | debconf-2.0
kismet-capture-common
libc6
libprotobuf-c1
libubertooth1
libwebsockets17
kismet_cap_ubertooth_one
:~# kismet_cap_ubertooth_one -h
kismet_cap_ubertooth_one is a capture driver for Kismet. Typically it is started
automatically by the Kismet server.
kismet_cap_ubertooth_one supports sending data to a remote Kismet server
usage: kismet_cap_ubertooth_one [options]
--connect [host]:[port] Connect to remote Kismet server on [host] and [port]; by
default this now uses the new websockets interface built
into the Kismet webserver on port 2501; to connect using
the legacy remote capture protocol, specify the '--tcp'
option and the appropriate port, by default port 3501.
--tcp Use the legacy TCP remote capture protocol, when combined
with the --connect option. The modern protocol uses
websockets built into the Kismet server and does not
need this option.
--ssl Use SSL to connect to a websocket-enabled Kismet server
--ssl-certificate [certfile] Use SSL to connect to a websocket-enabled Kismet server
and use the provided certificate authority certificate
to validate the server.
--user [username] Kismet username for a websockets-based remote capture
source. A username and password, or an API key, are
required for websockets mode. A username and password
are ONLY used in websockets mode.
--password [password] Kismet password for a websockets-based remote capture source.
A username and password, or an API key, are required for
websocket mode. A username and password are ONLY used in
websockets mode.
--apikey [api key] A Kismet API key for the 'datasource' role; this may be
supplied instead of a username and password for websockets
based remote capture. An API key is ONLY used in websockets
mode.
--endpoint [endpoint] An alternate endpoint for the websockets connection. By
default remote datasources are terminated at
/datasource/remote/remotesource.ws
This should typically only be changed when using a HTTP proxy
homing the Kismet service under a directory. Endpoints
should include the full path to the websocket endpoint, for
example:
--endpoint=/kismet/proxy/datasource/remote/remotesource.ws
--source [source def] Specify a source to send to the remote
Kismet server; only used in conjunction with remote capture.
--disable-retry Do not attempt to reconnect to a remote server if there is an
error; exit immediately. By default a remote capture will
attempt to reconnect indefinitely if the server is not
available.
--fixed-gps [lat,lon,alt] Set a fixed location for this capture (remote only),
accepts lat,lon,alt or lat,lon
--gps-name [name] Set an alternate GPS name for this source
--daemonize Background the capture tool and enter daemon mode.
--list List supported devices detected
--autodetect [uuid:optional] Look for a Kismet server in announcement mode, optionally
waiting for a specific server UUID to be seen. Requires
a Kismet server configured for announcement mode.kismet-core
Kismet is a wireless network and device detector, sniffer, wardriving tool, and WIDS (wireless intrusion detection) framework.
Kismet works with Wi-Fi interfaces, Bluetooth interfaces, some SDR (software defined radio) hardware like the RTLSDR, and other specialized capture hardware.
This package contains the Kismet Core.
Installed size: 20.39 MB
How to install: sudo apt install kismet-core
Dependencies:
libc6
libgcc-s1
libpcap0.8
libpcre3
libprotobuf-c1
libprotobuf32
libsensors5
libsqlite3-0
libstdc++6
libwebsockets17
zlib1g
kismet
Wireless sniffer and monitor
:~# kismet -h
usage: kismet [OPTION]
Nearly all of these options are run-time overrides for values in the
kismet.conf configuration file. Permanent changes should be made to
the configuration file.
*** Generic Options ***
-v, --version Show version
-h --help Display this help message
--no-console-wrapper Disable server console wrapper
--no-ncurses-wrapper Disable server console wrapper
--no-ncurses Disable server console wrapper
--debug Disable the console wrapper and the crash
handling functions, for debugging
-c <datasource> Use the specified datasource
-f, --config-file <file> Use alternate configuration file
--no-line-wrap Turn off linewrapping of output
(for grep, speed, etc)
-s, --silent Turn off stdout output after setup phase
--daemonize Spawn detached in the background
--no-plugins Do not load plugins
--homedir <path> Use an alternate path as the home
directory instead of the user entry
--confdir <path> Use an alternate path as the base
config directory instead of the default
set at compile time
--datadir <path> Use an alternate path as the data
directory instead of the default set at
compile time.
--override <flavor> Load an alternate configuration override
from {confdir}/kismet_{flavor}.conf
or as a specific override file.
*** Logging Options ***
-T, --log-types <types> Override activated log types
-t, --log-title <title> Override default log title
-p, --log-prefix <prefix> Directory to store log files
-n, --no-logging Disable logging entirely
*** Device Tracking Options ***
--device-timeout=n Expire devices after N secondskismet_cap_kismetdb
:~# kismet_cap_kismetdb -h
kismet_cap_kismetdb is a capture driver for Kismet. Typically it is started
automatically by the Kismet server.
kismet_cap_kismetdb supports sending data to a remote Kismet server
usage: kismet_cap_kismetdb [options]
--connect [host]:[port] Connect to remote Kismet server on [host] and [port]; by
default this now uses the new websockets interface built
into the Kismet webserver on port 2501; to connect using
the legacy remote capture protocol, specify the '--tcp'
option and the appropriate port, by default port 3501.
--tcp Use the legacy TCP remote capture protocol, when combined
with the --connect option. The modern protocol uses
websockets built into the Kismet server and does not
need this option.
--ssl Use SSL to connect to a websocket-enabled Kismet server
--ssl-certificate [certfile] Use SSL to connect to a websocket-enabled Kismet server
and use the provided certificate authority certificate
to validate the server.
--user [username] Kismet username for a websockets-based remote capture
source. A username and password, or an API key, are
required for websockets mode. A username and password
are ONLY used in websockets mode.
--password [password] Kismet password for a websockets-based remote capture source.
A username and password, or an API key, are required for
websocket mode. A username and password are ONLY used in
websockets mode.
--apikey [api key] A Kismet API key for the 'datasource' role; this may be
supplied instead of a username and password for websockets
based remote capture. An API key is ONLY used in websockets
mode.
--endpoint [endpoint] An alternate endpoint for the websockets connection. By
default remote datasources are terminated at
/datasource/remote/remotesource.ws
This should typically only be changed when using a HTTP proxy
homing the Kismet service under a directory. Endpoints
should include the full path to the websocket endpoint, for
example:
--endpoint=/kismet/proxy/datasource/remote/remotesource.ws
--source [source def] Specify a source to send to the remote
Kismet server; only used in conjunction with remote capture.
--disable-retry Do not attempt to reconnect to a remote server if there is an
error; exit immediately. By default a remote capture will
attempt to reconnect indefinitely if the server is not
available.
--fixed-gps [lat,lon,alt] Set a fixed location for this capture (remote only),
accepts lat,lon,alt or lat,lon
--gps-name [name] Set an alternate GPS name for this source
--daemonize Background the capture tool and enter daemon mode.
--list List supported devices detected
--autodetect [uuid:optional] Look for a Kismet server in announcement mode, optionally
waiting for a specific server UUID to be seen. Requires
a Kismet server configured for announcement mode.kismet_cap_pcapfile
:~# kismet_cap_pcapfile -h
kismet_cap_pcapfile is a capture driver for Kismet. Typically it is started
automatically by the Kismet server.
kismet_cap_pcapfile supports sending data to a remote Kismet server
usage: kismet_cap_pcapfile [options]
--connect [host]:[port] Connect to remote Kismet server on [host] and [port]; by
default this now uses the new websockets interface built
into the Kismet webserver on port 2501; to connect using
the legacy remote capture protocol, specify the '--tcp'
option and the appropriate port, by default port 3501.
--tcp Use the legacy TCP remote capture protocol, when combined
with the --connect option. The modern protocol uses
websockets built into the Kismet server and does not
need this option.
--ssl Use SSL to connect to a websocket-enabled Kismet server
--ssl-certificate [certfile] Use SSL to connect to a websocket-enabled Kismet server
and use the provided certificate authority certificate
to validate the server.
--user [username] Kismet username for a websockets-based remote capture
source. A username and password, or an API key, are
required for websockets mode. A username and password
are ONLY used in websockets mode.
--password [password] Kismet password for a websockets-based remote capture source.
A username and password, or an API key, are required for
websocket mode. A username and password are ONLY used in
websockets mode.
--apikey [api key] A Kismet API key for the 'datasource' role; this may be
supplied instead of a username and password for websockets
based remote capture. An API key is ONLY used in websockets
mode.
--endpoint [endpoint] An alternate endpoint for the websockets connection. By
default remote datasources are terminated at
/datasource/remote/remotesource.ws
This should typically only be changed when using a HTTP proxy
homing the Kismet service under a directory. Endpoints
should include the full path to the websocket endpoint, for
example:
--endpoint=/kismet/proxy/datasource/remote/remotesource.ws
--source [source def] Specify a source to send to the remote
Kismet server; only used in conjunction with remote capture.
--disable-retry Do not attempt to reconnect to a remote server if there is an
error; exit immediately. By default a remote capture will
attempt to reconnect indefinitely if the server is not
available.
--fixed-gps [lat,lon,alt] Set a fixed location for this capture (remote only),
accepts lat,lon,alt or lat,lon
--gps-name [name] Set an alternate GPS name for this source
--daemonize Background the capture tool and enter daemon mode.
--list List supported devices detected
--autodetect [uuid:optional] Look for a Kismet server in announcement mode, optionally
waiting for a specific server UUID to be seen. Requires
a Kismet server configured for announcement mode.kismet_server
Wireless sniffer and monitor
:~# kismet_server -h
kismet_server is now named just kismet, you may wish to update