Wireshark · Wireshark-users: Re: [Wireshark-users] [Fwd: Re: Newbie Q - Displaying TCP data content in a column..]

[Jaap Keuter <jaap.keuter@xxxxxxxxx>]

Hi,

You can file an enhancement bug at https://bugs.wireshark.org
If anyone can find the time, it may picked up. Time is limited though.

Thanx,
Jaap


Kevin Hawkins wrote:
> I'm sort of hoping that the great people who maintain WireShark may have
>
> read this and might have logged it and add it as a feature.
>
> Is that optimistic and if so should I be posting a request request 
> elsewhere (where ?) ?
>
> Chris
>
> Stephen Fisher wrote:
> > On Tue, Nov 25, 2008 at 03:54:51PM +0100, Stig Bjørlykke wrote:
> >   
> > > 2008/11/25 Kevin Hawkins <wireshark@xxxxxxxxxxx>:
> > >     
> >   
> > > > - just one last bit - can I get that data displayed in the column in 
> > > > ASCII ?
> > > >       
> > > I don't think you can do this with the current implementation.
> > >     
> >   
> > > But I can see several possible enhancements to make this work:
> > > - Add a (hidden?) entry in the data dissector, named data.text.
> > > - Add a preference to the data dissector to display as HEX or text.
> > >     
> > Hidden field = bad :)
> >
> > How about two visible fields for the data disssector - one that shows 
> > bytes and the other text?  FT_BYTES cuts it off after 'x' number of 
> > characters, we could have the text do the same perhaps.  It would be 
> > handy so you don't have to look in the hex output below to see plain 
> > text when looking at unrecognized traffic.
> >
> >
> > Steve