Generic Remote Datasources

[mardecker]

Hi there,

I recently developed interconntected IoT-Devices (BW16-RTL8720DN) for capturing different security-relevant WLAN-Frames.
My Server-application turns those captures into PCAP-Files (one for each Sensor).
Is it possible to directly send PCAP entries to Kismet?

[kismetwireless]

yeah; you can feed packets to kismet over the remote capture protocol. if they're already wifi, then you can feed them with the existing wifi dlt and they'll be decoded; if they're a new protocol, you'll need to add a phy handler for them. take a look at the datasource_{whatever} files in the kismet source; those are the C++ side which maps a remote capture into a local driver; those are mostly boilerplate. then take a look at the datasources themselves - something like the pcap datasource might be a good starting point. they handle configuring the capture, getting the packets, and passing that to kismet over ipc/tcp/websockets. the implementation of the datasource protocol is all handled in a library included with kismet, so you may not have to modify much from the pcap file source example. if you need a new phy handler / they're not otherwise normal packets, you'll need to dig a lot deeper into the phy stuff which handles the dissection and categorization for different types of packets, but since you said it's wlan, you might be all set.

…

-m

On Wednesday, August 20th, 2025 at 12:38 PM, mardecker ***@***.***> wrote: mardecker created an issue [(kismetwireless/kismet#567)](#567) Hi there, I recently developed interconntected IoT-Devices (BW16-RTL8720DN) for capturing different security-relevant WLAN-Frames. My Server-application turns those captures into PCAP-Files (one for each Sensor). Is it possible to directly send PCAP entries to Kismet? — Reply to this email directly, [view it on GitHub](#567), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AFKJYY62H37R5FT5OSADPBT3OSQADAVCNFSM6AAAAACEMB3ZJOVHI2DSMVQWIX3LMV43ASLTON2WKOZTGMZTQOBQGM3TSOI). You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>