Hi, I need some clarification regarding the availability of decoded protocol fields when using tshark -2. I have the following test LUA script:
I run the script with the following command:
This produces the following output:
It seems that the decoded protocol field eth.type is not available in the first scan (when pinfo.visited is false). Is this correct? Thanks and regards…Paul asked 27 Jul ‘15, 03:46 PaulOfford |
One Answer:
Correct - both tshark and Wireshark invoke dissection at various times, and in order to improve on performance they don't dissect certain fields if they don't think they need to. So in tshark's case, with the two-pass analysis it doesn't think you need that field information until the second pass. I bet if you set a filter, like ' But anyway there is a work-around for this that should make it work: add the Lua boolean "
That should force tshark/wireshark to generate all fields all the time. It impacts performance, which is why it's not enabled by default. answered 27 Jul '15, 05:24 Hadriel |
Hi Hadriel, Adding the Boolean doesn't work - I get the same result as I get without it. The filter works great - thanks for that.
Best regards...Paul
Hmmm... yet another bug. If you submit another bug for it I'll fix that too.