Joerg Mayer wrote:
On Thu, Feb 15, 2007 at 09:56:56AM -0800, Guy Harris wrote:
Douglas Pratley wrote:
Following on from recent comments about being able to save "user
decodes", has anyone been working on being able to save Wireshark
settings under different "profiles"? There's some discussion of this on
the Wiki, and it would obviously be a very useful feature if user
decodes are persisted. Or is there a feeling that this question is best
left until there is the next generation PCAP file format to play with,
as settings could be embedded in that?
Given that Wireshark can read files other than libpcap files, and will
continue to be able to read them, and that this is probably considered a
significant feature (as it means you can use Wireshark even on media on
which it can't capture), whilst it might be useful to allow various
Wireshark settings to be put into pcap-NG files, it wouldn't be
*sufficient* to allow that.
One feature that might be useful would be support for a "Wireshark
settings file" that could be associated with a capture, so that if a
file named foo.{pcap,cap,...} were opened, Wireshark could look for
foo.wssettings, or something such as that, and, if it finds, load it.
Hmm, maybe just adding some files to the config directory and taring
them would be an option (and of course accessing them from the tar file
instead of the normal file later on).
Sorry, that all sounds like a *very* complicated way ...
I would like to hear more about the specific problem (what settings are
actually affected and why) before thinking about a solution.
Implementing a solution without really understanding the underlying
problem is just a bad way to solve things ...
Regards, ULFL
