Wireshark-dev: Re: [Wireshark-dev] Add plugin timing statistics
I was able to add statistics for some simple request/response timing. Using (!PINFO_FD_VISITED(pinfo)) I checked my packets on the first pass, in order. Since I have a Request/Response format, as I saw my Request frame, I stored it in my conversation proto data. When the Response came, I read the Request frame stored and associated the two with transaction data – written in a wmem_tree I also stored in the conversation proto data. My transactions have no unique identifier – so I used the frame number. Dissecting the Response, I could lookup the Request transaction and fill it in with the Response frame, and fill in the Response’s Request frame too. And I handle when they can’t find a partner. The proto_tree_add_uint referring to an FT_FRAMENUM; FRAMENUM_TYPE(FT_FRAMENUM_REQUEST/RESPONSE) links everything with hyperlinks and arrows with virtually no effort. I can’t find information in tcpinfo pointing to the ACK packet, but I’ll make another thread with that question. Thank you, Jay Turner From: Wireshark-dev <wireshark-dev-bounces@xxxxxxxxxxxxx> On Behalf Of Dario Lombardo You could start by reading stats_tree documentation that tells you how handle statistic using the stats_tree subsystem (based on tap, but more evolved), by reading packet_info structure that stores info about lower layer protocols, and by reading the DNS dissector (above others), that creates stats that sound like the ones you need. On Mon, Aug 31, 2020 at 5:21 PM <jayrturner99@xxxxxxxxx> wrote:
-- Naima is online. |
- Prev by Date: Re: [Wireshark-dev] Updating Migration from Gerrit Issue
- Next by Date: [Wireshark-dev] Find ACK for my packet?
- Previous by thread: [Wireshark-dev] Remote Developer Den, July 2020
- Next by thread: Re: [Wireshark-dev] Add plugin timing statistics
- Index(es):