[Ron Flory <ron.flory@xxxxxxxxxx>]

hi-

 Please don't take this message in a negative way; Ethereal is probably one
of the most useful utilities I've seen in a very long time.  I hope that by
reporting these 'problems' that Ethereal will become an even better
program.

 Three long-standing 'issues' with Ethereal since at least version 0.8.9 :

1. TFTP packets are incorrectly reported as (invalid) WCCP packets.
   If I disable the WCCP protocol, TFTP packets are correctly decoded.
   I would assume the correct action would be to fix the WCCP dissector 
   so that it does not (incorrectly) claim TFTP packets as its own.

2. The action of disabling the WCCP protocol (to work-around the above
   issue) is not preserved across Ethereal sessions, nor can I seem to 
   find how/where to save these settings so that I don't have to manually
   disable WCCP every time I start Ethereal.

3. Expanding/displaying the payload of the last packet of a chain of 
   RIPv2-Responce packets locks Ethereal up dead-solid.  This happens 
   every time and can only be recovered by killing the Ethereal process.

 Thanks for listening.

ron