Comment # 3
on bug 12269
from Christopher Maynard
(In reply to alex from comment #2)
> Actually I think pretty formatted text output also could be suitable, and I
> even expected that tshark -P can do it...but it doesn't.
It should. It works for me, printing all column data. If it doesn't work for
you, maybe you could describe in a bit more detail what fails exactly?
> It doesn't use profile settings, it doesn't print packet list with so many
> cool custom columns I configured
tshark should use your currently active profile settings, but in case you've
changed your Wireshark profile, you can always force tshark to use a specific
profile with the "-C <configuration profile>" option. (Ref:
https://www.wireshark.org/docs/man-pages/tshark.html)
> It seems custom column feature underestimated and many engineers still use
> time-consuming manual packet details checking instead.
It seems that at least some engineers have Wireshark installed then? For those
engineers, you could send your profile to them so their settings would match
yours.
You are receiving this mail because:
- You are watching all bug changes.
