https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3903
--- Comment #7 from Artem Tamazov <artem.tamazov@xxxxxxxxxxx> 2009-09-10 09:48:32 PDT ---
Thanks for committing my work.
Regarding your question - I do not know still. Let's see what users want.
My opinion is that the main disadvantage of "Decode as.." is that the
associations are not remembered between Wireshark sessions. But it is nicely
interactive - just click on packet and select dissector you wish. May be it
would be good to learn Wireshark to save "Decode as..." state to the
configuration file.
Note also the following limitation. For TDM pseudowires, the configured
destination port together with both the source and destination IP addresses
uniquely identify the PW for the receiver (see rfc5086, for example). This
means that the same port number may be used for different PW types, provided
that IP addresses are different (for example, even if SAToP PW is established
between two IP addresses with destination port X, then it is quite legal to
pass CESoPSN traffic between different pair of IPs with the same destination
port X). Current implementation of Wireshark does not check IP addresses when
specific dissector is selected, only port number is taken into account.
In the context of the limitation mentioned above, it makes sense to implement
preference which allows to associate SrcIP/DstIP:DstPORT with certain PW
dissector. However I tend to leave implementation as it is until end users are
satisfied.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
