Wireshark · Wireshark-dev: Re: [Wireshark-dev] How code recognizes that processing of all packets with tap was finished?

ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] How code recognizes that processing of all packets with tap

From: Guy Harris <guy@xxxxxxxxxxxx>

Date: Thu, 21 Jun 2018 11:45:48 -0700

On Jun 20, 2018, at 3:14 PM, Jirka Novak <j.novak@xxxxxxxxxxxx> wrote:

>  What is correct way to recognize that capture processing with tap was
> finished?

There isn't one, unfortunately.  We'd have to change the tap mechanism to introduce a "we're done processing packets" callback to provide that.

Follow-Ups:
- Re: [Wireshark-dev] How code recognizes that processing of all packets with tap was finished?
  - From: Jirka Novak

References:
- [Wireshark-dev] How code recognizes that processing of all packets with tap was finished?
  - From: Jirka Novak

Prev by Date: [Wireshark-dev] How code recognizes that processing of all packets with tap was finished?
Next by Date: [Wireshark-dev] Publishing binaries for a new plugin
Previous by thread: [Wireshark-dev] How code recognizes that processing of all packets with tap was finished?
Next by thread: Re: [Wireshark-dev] How code recognizes that processing of all packets with tap was finished?
Index(es):
- Date
- Thread

© Wireshark Foundation · Privacy Policy

Facebook·Mastodon·Twitter·YouTube