Wireshark · Ethereal-dev: Re: [Ethereal-dev] SCTP patch: put source and destination ports in tree

[Jeff Morriss <jeff.morriss@xxxxxxxxxxx>]

Hi Michael,

Thanks.  Question, though: since the default column list doesn't include
a port (and since TCP, UDP, IP, etc. put src & dest info in the tree)
would it be Better for the default for this behavior to be on?  (I saw
that the preference defaults it to off.)

I think this would make the default "out of the box" behavior more user 
friendly.  What do you think?

Regards,
-Jeff

Michael Tuexen wrote:
> Hi Jeff,
>
> I have checked in the functionality. I have added a preference for that,
> because I always use a port number column and will add a list of
> chunks to the protocol tree summary. So having both, the port numbers
> and the chunks may consume too much space. So let the user decide...
>
> Best regards
> Michael
>
> On Feb 25, 2005, at 1:56 AM, Jeff Morriss wrote:
>
> > Hi list,
> >
> > Here is a small patch which makes the SCTP dissector more like TCP in 
> > that the Source and Destination ports are displayed in the tree item 
> > (thus saving the user the trouble of expanding the SCTP tree just to 
> > find the port numbers).
> >
> > I didn't implement a preference (like 'tcp_summary_in_tree') because I 
> > don't see the benefit; if desired I can add that.
> >
> > Regards,
> > -Jeff
> >
> > <sctp.patch.gz>_______________________________________________
> > Ethereal-dev mailing list
> > Ethereal-dev@xxxxxxxxxxxx
> > http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev