Thanks for the clarification. I'm looking to export/display the
username, ip and message data, so maybe it would be easier to tap the
main aim file rather than specifically the messaging, assuming the info
that messaging dissects is accessible from the main file? Would the data
I want already b
Hi,
Whatever you choose depends on what you want to do with the tapped information,
so that is totally up to you.
The syntax is correct. pinfo is a pointer to the packet info struct, containing
all kinds of meta data on the frame. That's something (almost) every tap
listener wants to have, so
Hello everyone,
I'm currently working on implementing a tap interface for the
aim_messaging dissector and have some questions. Do you think I'd be
better off tapping the main aim protocol? Right now I have it tapping
packets to the queue twice, at the end of dissect_aim_msg_outgoing and
dissect
