Sniffing with Pyspinel with or without extcap

[MattWestb]

As i understand is it possible with Pyspinel and extcap using OTR RCP and its spinel interface for sniffing Thread / Zigbee (IEEE 802.15.4) packages if reading OT pages like https://openthread.io/guides/pyspinel/sniffer-extcap but is only made for Nordic and TI chips.
I think it shall being possible with other RCP with spinel enabled.

Have some experience of doing it and how to do it in real with our chips (ESP32/EFR32MG) ?

Also is it in the long run interesting implanting part of it in HA for doing deeper diagnostic for our mesh networks ??

[puddly]

I haven't used it as an extcap interface yet but you can do it over CLI if you're running a OpenThread RCP + Ziggurat build (it right now uses Ziggurat commands instead of Spinel directly):

zigpy -vvv radio --baudrate 460800 ziggurat /dev/cu.usb... packet-capture -c 25 -o - | wireshark -k -S -i -

I've tested it with a few different chips.

Also is it in the long run interesting implanting part of it in HA for doing deeper diagnostic for our mesh networks ??

The problem right now is promiscuous mode. If I remember correctly, SiLabs RAIL does not allow you to enable auto-ACK and keep the radio in promiscuous mode. ESP32-C6 should. I was hoping to automatically add this data to debug logs.

Enabling promiscuous mode + auto ACKing should allow the radio to react to packets that aren't intended for it, allowing us to build topology information for nearby routers that are more than one hop away. In theory.

[MattWestb]

Ops so its like EZSP but only defining Ziggurat !!
Is it needing tshark if trying it on windows like Bellows is doing ??

Was looking little on multi rail but Silabs only have one example of Zigbee NCP with GP on the other rail and also the multi-protocol but both are not using spinel so not for this project.

Sadly have the Matter devs blocking all no Matter thread devices in there map GUI but in the best it was possible mapping Home Kit and ESPHome devices but not longer and its one pain in the ass !! -> putting all HomeKit thread devices in the black box (EVE and Nanoleaf).
Some devs have trying reading the neighbors from the thread network but normally not working good (some time can getting all data and build the map but oft cant getting anything) so for the moment our thread mesh networks is one black box.
Also Matter devs is only interesting in the matter fabrics and is the real long and short 15.4 dresses that is the ground of the network and then linking to thread IPV6 addresses and if possible to all devices in HA.

Also if can sniffing all on one channel its possible getting more thread and Zigbee network and information / topography and is having network keys and / or TLV but its little extreme for HA i think.