Comment # 6
on bug 8522
from Audric Schiltknecht
Evan,
(In reply to comment #5)
> Yuck. So, the "eth" heuristic table is only for protocols that are not
> ethernet at all but might have ethernet framing (thus the fact that they get
> called with the whole payload).
As a matter of fact, it is exactly the case here: DVB-S2 is transported in an
ethernet framing. I'm sorry, I should have been more precise on this point in
my initial request.
But I am glad to know why I had to skip the whole ethernet header!
>
> Your test packet contains an ethernet 802.3 header. As far as I can tell
> from reading the code, there is no way to register subdissectors for that
> payload at all - the code claims that Logical Link Control is the only valid
> protocol to be carried on raw 802.3 of this form.
>
> At this point we're beyond my knowledge of the protocols involved. Is DVB-S2
> doing something 'improper' when it's carried over raw 802.3? Is the comment
> in the ethernet dissector wrong?
Since DVB-S2 is a "modulation and channel coding system" designed to be carried
over radio waves, there is no specifications -at least that I am aware of- for
its transport in a "classical", wire-based network (if somebody knows of such
standard, I will gladly take a look to see if I can adapt the dissector).
Our equipments use an ethernet framing, the same way the equipments the
original DVB-S2 dissector author has use UDP datagrams, and there might be
others using other means to carry DVB-S2.
If you think that the ethernet based dissector is too specific to be included
into wireshark, I will fully understand your choice.
Regards,
Audric
You are receiving this mail because:
- You are watching all bug changes.