 | 1 | initial version |
As Spooky notes, this would require code changes.
You should submit an enhancement request on the Wireshark Bugzilla for this; that, rather than asking here, the best way to request new features in Wireshark. Put a link to this question into the enhancement request.
Note that the best way to do this might be to have Wireshark read a text file giving descriptions of the fields in question, so that code doesn't have to be changed in the future; that approach is already used for RADIUS and DIAMETER parameters. Unlike RADIUS, where the FreeRADIUS file format can be and is used, I don't know of a standard format for describing Netflow/IPFIX fields in a text file; Elastiflow appears to have a YAML-based format for that, but 1) that file doesn't have a lot of fields, 2) I don't know if any other programs use that format, so it's not as obvious a choice as FreeRADIUS form is for RADIUS dictionaries.
