On Feb 12, 2013, at 2:54 AM, Graham Bloice wrote:
> On 12 February 2013 01:52, Guy Harris wrote:
>
>> On Feb 11, 2013, at 5:02 PM, Hadriel Kaplan wrote:
>>
>> > I guess I'll just fix it and have it say "works for tshark only".
>>
>> ...but there's not even a guarantee that it'll work for TS
On 12 February 2013 01:52, Guy Harris wrote:
>
> On Feb 11, 2013, at 5:02 PM, Hadriel Kaplan
> wrote:
>
> > I guess I'll just fix it and have it say "works for tshark only".
>
> ...but there's not even a guarantee that it'll work for TShark forever, so
> I changed your update to use only the pos
On Feb 11, 2013, at 5:02 PM, Hadriel Kaplan wrote:
> I guess I'll just fix it and have it say "works for tshark only".
...but there's not even a guarantee that it'll work for TShark forever, so I
changed your update to use only the post-dissector code.
On Feb 11, 2013, at 7:37 PM, Guy Harris wrote:
> *If* Wireshark is supposed to support setting columns in taps, rather than in
> dissectors or in post-dissectors:
> http://wiki.wireshark.org/Lua/Examples/PostDissector
> *then* the listener taps would have to be called whenever the columns
On Feb 11, 2013, at 4:10 PM, Hadriel Kaplan wrote:
> Setting column text via Lua plugins by using the pinfo:set() method (the
> Pinfo from a Listener tap), doesn't seem to work for two reasons:
> 1) The TL_REQUIRES_COLUMNS flag wasn't being set when registering Lua
> listener taps in Listener_
Howdy,
Setting column text via Lua plugins by using the pinfo:set() method (the Pinfo
from a Listener tap), doesn't seem to work for two reasons:
1) The TL_REQUIRES_COLUMNS flag wasn't being set when registering Lua listener
taps in Listener_new(). I fixed that in my local copy.
2) Wireshark ap
