Wireshark-bugs: [Wireshark-bugs] [Bug 9624] Added ASTERIX Category 062 Reserved Expansion Field
Comment # 13
on bug 9624
from Marko Hrastovec
(In reply to comment #12)
> Just an idea: How about adding a preference which would allow parallel
> implementaion of
> a) additional headers between udp and asterix header
> b) different implementation flavours for customer specific stuff
> depending on sic/sac + source ip?
> The combination of sic/sac + source ip should be sufficient to identify the
> sender and (as admins) we are supposed to know which protocol flavour is in
> use.
I am not sure I understand you correctly. I am not aware of possibility that
would allow the dissector to save some settings. We are having problems how to
include dissection for various versions of the same category. There is no
indication in the message itself which version of category is used.
Are you proposing that from source IP and sic/sac the dissector could "guess"
which version of asterix is used?
For that kind of guessing some settings would be required where we could
specify attributes which would tell us how to dissect certain traffic. First we
have to solve the problem of dissecting more versions of the same category.
Other dissectors in wireshark just make new dissector for the new version of
protocol, but that is kind of difficult for asterix because there are 256
possible categories and each of them can have more versions.
You are receiving this mail because:
- You are watching all bug changes.
