Wireshark · Wireshark-users: Re: [Wireshark-users] LUA Postdissector Field Extractors getting nil values from built-in TCP Dissec

Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: Re: [Wireshark-users] LUA Postdissector Field Extractors getting nil values from

From: Edwin Nasol <enasol@xxxxxxxxx>

Date: Fri, 27 Feb 2009 10:00:25 +0000 (UTC)

Does it mean, then, that at the Postdissector level or state, field information 
from previous dissectors (which already completed their run) are inaccessible? 
And only the data.data information can be field-extracted?

Or is there any other way to access them?

TIA,
Edwin Nasol

References:
- [Wireshark-users] LUA Postdissector Field Extractors getting nil values from built-in TCP Dissectors
  - From: Edwin Nasol
- Re: [Wireshark-users] LUA Postdissector Field Extractors getting nil values from built-in TCP Dissectors
  - From: Edwin Nasol

Prev by Date: [Wireshark-users] packet counter statistics for a dissector
Next by Date: Re: [Wireshark-users] Not seeing SSL protocol packets
Previous by thread: Re: [Wireshark-users] LUA Postdissector Field Extractors getting nil values from built-in TCP Dissectors
Next by thread: [Wireshark-users] How to find out the current locally installed version of WinPCap?
Index(es):
- Date
- Thread

© Wireshark Foundation · Privacy Policy

Facebook·Mastodon·Twitter·YouTube