Start/stop sniffing by external event

RE: Start/stop sniffing by external event

David Edwin — Sat, 18 May 2019 14:57:27 GMT

We can consider the feature but, our backlog for the next few releases are already filled. Why don't you try the Sniffer API with the python and see if that works for you.

The latest beta(pre-releasee) with stability fixes is posted on this case.

RE: Start/stop sniffing by external event

ekrashtan — Sat, 18 May 2019 14:35:51 GMT

Wireshark will perform badly when you hit more than 1 million packets in the capture.

Yes, that's why I requested such feature.

1. One-two days, but only when equipment in an active state, It means total 10-20 minutes in short periods (few seconds)

2. Yes, I thought about this possibility, but I need to catch only one wrong sequence and still have no idea how to filter the necessary period without an external toggle.

RE: Start/stop sniffing by external event

David Edwin — Sat, 18 May 2019 13:05:15 GMT

I would suggest upgrading to a nRF52 based DK board as our tests show that the nRF51 based DKs perform worse when we need to sniff large number of packets.

We have attempted to improve stability of the UART link so we can observe for "long" periods of time.

1. However what do you mean by "long" ?

2. You can also use the python based Sniffer API instead of wireshark so large number of packets can be received and analyzed.
Wireshark will perform badly when you hit more than 1 million packets in the capture.