I would implement a listener for the tap interface of the ip dissector. Handling which addresses exist must be done on your end. You can ignore display, and keep just with the basic tap callback, but remember to keep the tap callback as short as possible.
regards On Mon, Oct 31, 2016 at 3:01 PM, Dario Lombardo <dario.lombardo...@gmail.com > wrote: > As a starting point I'd like to have the ones in packet_info. > > On Mon, Oct 31, 2016 at 2:50 PM, Roland Knall <rkn...@gmail.com> wrote: > >> Hi >> >> What ip src/dest do you mean? If you mean the ones from a packet trace, a >> tap interface might be the easiest to get the information. I do a similar >> thing with a 3rd-party plugin of mine. >> >> regards >> Roland >> >> On Mon, Oct 31, 2016 at 2:44 PM, Dario Lombardo < >> dario.lombardo...@gmail.com> wrote: >> >>> Hi >>> I'd like to read the ip src/dst of the current open file from the Qt UI. >>> which is the easiest way to achieve this? >>> Thanks >>> Dario. >>> >>> ____________________________________________________________ >>> _______________ >>> 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-requ...@wireshark.org?subject=unsubscr >>> ibe >>> >> >> >> ____________________________________________________________ >> _______________ >> 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-requ...@wireshark.org?subject=unsubscr >> ibe >> > > > ____________________________________________________________ > _______________ > 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-requ...@wireshark.org?subject= > unsubscribe >
___________________________________________________________________________ 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-requ...@wireshark.org?subject=unsubscribe