Mac address lookup device type how to#
Mac address lookup device type mac#

Typically used to retrieve the bulk status of many devices for display in the UI.

Mac address lookup device type mac#

Required, a vector of MAC addresses to be returnedĪrray of all devices matching any of the supplied MAC addresses.įetch multiple devices matching any of the supplied keys. The supplied MAC addresses can either be complete MACs ( aa:bb:cc:dd:ee:ff), or partial-match masked MACs for instance to match only the OUI 00:aa:bb, a masked MAC address of 00:aa:bb:00:00:00/ff:ff:ff:00:00:00 can be supplied, as defined in Keys and MAC addresses. This API will always return a vector of devices, even when only one device is matched. Typically used to monitor the presence of target devices. devices/by-mac/ /devices.jsonĪrray of all devices with the supplied MAC address, optionally simplified by fields parameter.įetch devices matching any of multiple MAC addresses (or partial MAC addresses). This API will always return a vector of devices, even when only one device matches the MAC address. This becomes more likely when using non-Wi-Fi capture types which synthesize false MAC addresses because no official address is available, such as RTL-433, Mousejack, and other SDR-based datasources. It is possible (though usually not likely) that there may be MAC address collisions between different PHY types. Vector of (optionally summarized and filtered) devices active since TSĭevice record, with optional simplification of the fields, matching DEVICEKEYįetch devices which match the supplied MAC address. This endpoint is typically used by scripted clients to monitor currently active devices. This endpoint is most useful for extracting bulk data and passing it to another tool like Elasticsearch.Įach device is returned as a JSON object, one JSON record per line.įetch devices which have been active since the supplied timestamp. This endpoint only returns ekjson-formatted data. Sort order direction from jquery-datatablesĪ special ekjson-only endpoint which provides a dump of all devices. Search term, applied to all fields in the summary vectorĭisplay column number for sorting, indexed with colmap data Optional, inserted by the Kismet Datatable UI to enable datatable mode which wraps the output in a container suitable for consumption by jquery-datatables.Īdditionally, when in datatables mode, the following HTTP POST variables are used: Key Optional column correlation info inserted by the Kismet Datatable UI for mapping jquery-datatables column information for proper ordering and sorting.

The device summarization is best utilized when applying a view window via the start and length variables.Ģ019-06 While still available, this API has been deprecated in favor of the all device view. It is used heavily by the Kismet UI for the main device list table. The device summarization endpoint is the primary interface for clients to access the device list.

Mac address lookup device type how to#

See the views api for detailed information on how to use the views endpoints. devices/views/all/last-time/ /devices.json This API supercedes the /devices/summary/ API. This list is used by the main Kismet UI to display all devices, for instance. The device tracker uses device views to provide a windowed, sortable, searchable device list. Whenever possible, limiting the fields requested and the time range requested will reduce the load on the Kismet server and the client consuming the data. The preferred method of retrieving device lists is to use the POST URI /devices/summary/ or /devices/last-time with a list of fields provided. A device may have multiple phy-specific records, for instance a device may contain both a device.dot11 record and a device.uav record if it is seen to be a Wi-Fi based UAV/Drone device. For complex relationships (such as 802.11 Wi-Fi), a list of related devices describes the access point-client relationship.Īll devices will have a basic set of records (held in the group of fields, generally) and sub-trees of records attached by the phy-specific handlers. Clients, bridges, access points, wireless sensors, and any other type of entity seen by Kismet will be a device. Alerts - device presence / absence - changingĪ device is the central record of a tracked entity in Kismet.Alerts - device presence / absence - viewing.Device summary and windowed device view.