[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-users
Subject:    Re: [Wireshark-users] [Wireshark-dev] Dissecting packet details field by field
From:       Guy Harris <guy () alum ! mit ! edu>
Date:       2017-07-15 3:46:08
Message-ID: 85E63803-4FD3-43F5-980B-2F82EC3759D6 () alum ! mit ! edu
[Download RAW message or body]

On Jul 14, 2017, at 4:19 PM, Guy Harris <guy@alum.mit.edu> wrote:

> On Jul 14, 2017, at 5:38 AM, David Schaeffer <david.schaeffer2@gmail.com> wrote:
> 
> > The problem is we have multiple PLCs sending the same bit codes so just grabbing \
> > a filter for solely the bit code doesn't work, as it pulls from every PLC. I need \
> > to grab the IP address with it to track the specific bit code from that specific \
> > PLC.
> 
> *That* would require adding the ability to register a per-field callback, with the \
> default being one that causes a "standard" I/O graph to be popped up, and with your \
> dissector specifying a callback grabbing the IP address and the value of the bit \
> code.  That might call the "draw an I/O graph" code with another callback \
> specified; that callback would indicate whether to use the packet or not.

Or the first callback would just specify the appropriate filter to use.  That'd \
probably be useful for other protocols as well; perhaps making the callback \
per-protocol would suffice. \
___________________________________________________________________________ Sent via: \
                Wireshark-users mailing list <wireshark-users@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@wireshark.org?subject=unsubscribe


[prev in list] [next in list] [prev in thread] [next in thread]