Dissector stability guarantees
Hello,
Is there any policy in place regarding the stability of dissector field names and textual representation of data?
1 Answer
- Sort by
oldest newest most voted
0
None really, but it's informally "discouraged" as it can break workflows that depend on them, e.g. scripted display filters and post processing of fields.
Comments
I did see it happen on at least one field in the WLAN dissector.
Seems to me like we should start versioning scripts.
Unfortunately they do change, it's not as if they are IANA registered, and I believe the WLAN stuff has seen some extensive changes.
Fields shouldn't change within a stable release, e.g. 3.2.x, but could change on the next major version, e.g. 3.4.x.
In a "mission critical" environment I would hope that all the tools, Wireshark, associated scripts etc. are version controlled, elsewhere any breakage would be adapted to.
In the WLAN case it is necessary sometimes to upgrade wireshark to support newer specs, which can break older scripts.
Anyway, it seems like having multiple major versions installed might work.
Your Answer
Please start posting anonymously - your entry will be published after you log in or create a new account.
This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.
Comments