On Mon, Aug 31, 2015 at 09:47:11PM +0200, Pascal Quantin wrote:
> > On Mon, Aug 31, 2015 at 08:17:44AM +0200, Pascal Quantin wrote:
> > > 2015-08-31 5:34 GMT+02:00 Joerg Mayer <jmayer@xxxxxxxxx>:
> > >
> > > > When using tshark from head I have a bunch of problems right now:
> > > >
> > > > 1) stderr is getting spammed with
> > > > (process:9870): Capture-WARNING **: Dissector stp incomplete in frame
> > > > 41915: undecoded byte number 57 (0x0030+9)
...
> My understanding is that it is not intended to be activated by default, but
> only in "development mode" (at least according to the comments in the
> Gerrit patch if I remember correctly).
I don't really want to switch stuff on and off all the time. Many "interesting"
things are noted during normal work.
> > > > 2) -T fields -e _ws.col.info isn't working (empty column), both with
...
> tshark.pod needs to be fixed, but tshark -h gives you _ws.col.Info.
Which you now fixed.
> Could we plese agree to either *always* use small letters or to make the
> > filter names case insensitive? Also:
> > =========
> > $ tshark -T fields -e asdf
> > ** (process:13516): WARNING **: 'asdf' isn't a valid field!
> > tshark: Some fields aren't valid
> > $ tshark -T fields -e _ws.col.info
> > Capturing on 'Wi-Fi'
...
> Right now it's the column title as you configured it. Maybe it should be
> made case insensitive, but there is a real logic (and not inconsistency). I
> do not ceck this code part and whether _ws.col.XXX could (should?) trigger
> an error if the syntax is wrong.
Sorry, that was easy to misunderstand: The inconsistency remark was only about
how non-existent field names are handled, not about the spelling.
Thanks
Jörg
--
Joerg Mayer <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
