Skip to content

*BUG* KismetDB (.kismet) replay creates zero devices and ssids while equivalent PCAPNG replay works #619

Description

@SuperZuignap

KismetDB replay creates no devices, while PCAPNG converted from the same
database works correctly.

Kismet version:
Kismet 2025.09.0-b5d5a2d04

Platform:
Kali Purple 2026.3, Raspberry Pi 5, arm64

Broken command:
kismet -c "/home/XXXX/Kismet-20260727-07-00-23-1.kismet:realtime=true"

Also tested:
kismet -c "/home/XXXX/Kismet-20260727-07-00-23-1.kismet:pps=5000"

Observed:

  • KismetDB datasource reports successful launch.
  • Devices and SSIDs do not populate.
  • /devices/views/all_views.json shows size 0 for:
    • all
    • phy-IEEE802.11
    • phydot11_accesspoints
    • the datasource-specific seenby view

Database validation:

  • packets table contains 5,545 packets.
  • devices.device JSON contains SSIDs such as dot11.probedssid.ssid.
  • Exported PCAPNG contains beacon and probe frames with visible SSIDs in Wireshark.

Working comparison:
kismetdb_to_pcap
--in capture.kismet
--out capture.pcapng

kismet -c "capture.pcapng:realtime=true"

The PCAPNG replay immediately reconstructs Devices and SSIDs.

This suggests that the KismetDB datasource launches but does not deliver its
stored packets into the device-tracking packet-processing pipeline.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions