On 7/27/07, Matt Poduska <[EMAIL PROTECTED]> wrote: > Joel, > > It was not in our plan to support any XML display of LLRP frames. I'm not > sure about other's opinions, but it seems to me that WireShark is not a good > tool for the functionality you suggest. With the use of an LLRP binary > parser, creating a standalone application to generate XML message > representations would be a straightforward task. > > Another option might be to create a WireShark capture file conversion tool. > > - Matt >
I tend to agree with Matt on the GUI portion: the WS packet display is a big GTK tree control. Structurally it is similar to XML in that XML is a directed acyclic graph (tree), but if one just dumped the packet there as XML it would be a big string, not searchable via the normal WS filters. What could work is if CPlusPlus library were integrated into WS and the XML generator were made available through File->Export, or a new option under Analyze. That would leverage WS ability to capture traffic without affecting it, and do all post facto, tricky desegmentation work that being a passive observer necessitates.. -- John. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
