Hi again,
it gets irritating to count on the capabilities of the tool only to
realise after 3 hours of hard work that the thing DOESN'T work. The
export facility is completely neglected!.
1) The capture and displayed mean absolutely nothing for what it
actually happens. One creates a filter to display ONLY a certain range
of packets. Guess what; on the export the _entire_ thing gets saved
2) The Marked only packets does not work. You mark some packets and the
export saves them AAALLL!!! on text.
3) The selected packets only mean nothing since there is no distinction
between mark and select. If one could also add on edit mark all and
select all (displayed or captured) then maybe this will get some meaning.
4) Please please please set a preference tab for exports
primarily text
To work on traces one DOES need to save only the packet
summary (so somebody enable config on what to save on the exported text
by default)
Config on what mark and select means on the save of the
exported text.
Ensure a reset of the counters just in case (diplayed and
captured)
apologies for the rant but somebody heeeelp..
If the above are already addressed somehow on 10.5 please let me know (I
have 10.5 but cannot see them working)
cheers
theo
Theo Pagtzis wrote:
Hello all,
while am not on the list, I would like to report an annoying bug on
Ethereal that has been slipping of for some time now. Whenever, one
filters a trace and tries to export it as text, while the first time the
number of diplayed and saved packet summaries is correct, from the
second time onwards, this is not happening. The second export (second
filter snapshot of the trace) seems to keep the old no. of displayed
lines as well as saved.
If one could fix that and les us know that would be great.
--
theo
Nets & Mobile Systems Group
UCL-CS
