Wireshark mailing list archives
Re: Getting captured interface name inside plugin
From: Guy Harris <gharris () sonic net>
Date: Sun, 6 Jun 2021 17:24:48 -0700
On Jun 6, 2021, at 5:13 PM, Jan Mall <jan.mall () uni-ulm de> wrote:
I'm currently developing a plugin/dissector (C API), which should have a different dissection behavior depending on the interface Wireshark is currently listening on.
Why? What is the *ultimate* goal of this? ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Getting captured interface name inside plugin Jan Mall (Jun 06)
- Re: Getting captured interface name inside plugin Guy Harris (Jun 06)
- Re: Getting captured interface name inside plugin Jan Mall (Jun 06)
- Re: Getting captured interface name inside plugin Richard Sharpe (Jun 06)
- Re: Getting captured interface name inside plugin Guy Harris (Jun 06)
- Re: Getting captured interface name inside plugin Roland Knall (Jun 07)
- Re: Getting captured interface name inside plugin Jan Mall (Jun 07)
- Re: Getting captured interface name inside plugin Guy Harris (Jun 07)
- Re: Getting captured interface name inside plugin Jan Mall (Jun 07)
- Re: Getting captured interface name inside plugin Jan Mall (Jun 06)
- Re: Getting captured interface name inside plugin Guy Harris (Jun 06)