Re: [Wireshark-dev] Send info to plugin
On Oct 7, 2011, at 2:27 AM, fa...@freesurf.fr wrote: Typically a filename + Directory where the the plugin dissector would write some statistic information. If those are statistics about the protocol, that sort of work is best done in a tap, rather than a dissector; dissectors should just dissect packet data and put items corresponding to packet fields into the protocol tree and possibly attach expert info items to it as a result of further analysis. You can have plugin taps, just as you can have plugin dissectors. A tap for Wireshark can put up a GUI. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Send info to plugin
On Oct 7, 2011, at 4:40 AM, Martin Kaiser wrote: Thus wrote Guy Harris (g...@alum.mit.edu): (At this point, I really wish my name were Zarathustra. :-)) I've been playing with a new port_type PT_DVBCI_SESSION_NUMBER and set both source and destination port to the session number. Does that make sense or is there a better approach? The circuits for protocols that have a virtual circuit ID of some sort was based on an existing mechanism in Wireshark, which I put there originally for the benefit of the Frame Relay dissector, and later used in X.25 and elsewhere; see epan/circuit.h and routines using it. It sounds as if DVB-CI has what amounts to a VC ID, the session number. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Send info to plugin
Hello, Is there any way to send some information to a plugin dissector from the wireshark GUI interface? For instance using a wireshark menu to set some variable that will be accessible from the plugin. Or maybe it is possible to add a menu from the plugin? Thanks Fabien ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Send info to plugin
Hi, Can't you do what you want through preferences possibly with a UAT table? GUI code is not suppposed to live in plugins. With the new UIManager code in trunk it is possible To add items to the menubar. There's absolutly no guatrantee that that API is stable and I'm Not sure if it would work from a plugin, there is no ducumentation on it either. Regards Anders -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of fa...@freesurf.fr Sent: den 7 oktober 2011 10:20 To: wireshark-dev@wireshark.org Subject: [Wireshark-dev] Send info to plugin Hello, Is there any way to send some information to a plugin dissector from the wireshark GUI interface? For instance using a wireshark menu to set some variable that will be accessible from the plugin. Or maybe it is possible to add a menu from the plugin? Thanks Fabien ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://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:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Send info to plugin
On Oct 7, 2011, at 1:19 AM, fa...@freesurf.fr wrote: Is there any way to send some information to a plugin dissector from the wireshark GUI interface? What sort of information? For instance using a wireshark menu to set some variable that will be accessible from the plugin. As Anders suggested, you *can* give it global information through a preference setting. We should probably also add a notion of conversations available to dissectors at multiple layers (a notion more general than the current address-and-port-endpoint-pair notion, that can include multiple address layers, circuits for protocols that have a virtual circuit ID of some sort, and conversations at layers above the transport layer), and per-conversation settings as well, with Wireshark offering a GUI to let you select a conversation and set one or more of a set of dissector-specified parameters. Or maybe it is possible to add a menu from the plugin? A menu item to do what? ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Send info to plugin
On Oct 7, 2011, at 1:19 AM, fa...@freesurf.fr wrote: Is there any way to send some information to a plugin dissector from the wireshark GUI interface? What sort of information? Typically a filename + Directory where the the plugin dissector would write some statistic information. For instance using a wireshark menu to set some variable that will be accessible from the plugin. As Anders suggested, you *can* give it global information through a preference setting. We should probably also add a notion of conversations available to dissectors at multiple layers (a notion more general than the current address-and-port-endpoint-pair notion, that can include multiple address layers, circuits for protocols that have a virtual circuit ID of some sort, and conversations at layers above the transport layer), and per-conversation settings as well, with Wireshark offering a GUI to let you select a conversation and set one or more of a set of dissector-specified parameters. Or maybe it is possible to add a menu from the plugin? A menu item to do what? I imagine a menu that would open a popup asking to enter the filename + directory. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Send info to plugin
Thus wrote Guy Harris (g...@alum.mit.edu): We should probably also add a notion of conversations available to dissectors at multiple layers (a notion more general than the current address-and-port-endpoint-pair notion, that can include multiple address layers, circuits for protocols that have a virtual circuit ID of some sort, and conversations at layers above the transport layer) that would definitely be helpful. As far as I can see, DVB-CI is an example that does not fit into the current mechanism very well. CI is not based on tcp/ip, a ci session looks like open_session_request(resource_id) session_opened(newly assigned session number) payload transfer(session_number, payload data) ... close session(session_number) For now, how would you create a conversation from this? I've been playing with a new port_type PT_DVBCI_SESSION_NUMBER and set both source and destination port to the session number. Does that make sense or is there a better approach? Thanks, Martin ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
