Ethereal-dev: RE: [Ethereal-dev] using Ethereal for generating trace files etc ...
> In thinking about generating trace files from ethereal, I
> started looking
> at some infrastructure ...
What sort of traces are you interested in? Just dumping info per node
as you go along the tree? Or smth more generic, like generating
the end stats?
> u/U are not. Can anyone suggest a better set of flags to use.
Well, maybe just go for a long (--option-name) one?
> I need to specify that tracing be switched on and go to a
> particular file.
Also maybe you want to specify the precise testing verbosity.
Smth along the lines:
"start tracing at the IP level, down to TCP header but not the payload"
and maybe you want to configure exactly which fields you want traced
- maybe you could allow to specify the format string in a dfilter syntax
variant:
ip.addr tcp.port http
would dump you both ip address fields, tcp ports, and the whole http subtree
> I was thinking of adding code to do this, but given that most
> of the info
> is in the proto tree, there might be a simple way to achieve
> this as well.
this looks like yet another way of rendering the tree, but you still
need code to decide whether you want to prune a subtree and
which data you want to dump
V.
