https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5655
--- Comment #9 from herorade-wireshark@xxxxxxxx 2011-02-06 12:56:13 PST ---
(In reply to comment #7)
Hi Bill
many thanks for your comprehensive Message
here my answers:
1. - 4. you are right, I agree
5. The issue is the IHMO crude style of CM-STATUS Messages
please see
http://www.cablelabs.com/specifications/CM-SP-MULPIv3.0-I14-101008.pdf
page 153.
In message code I've found "01 03 04 01 0c" The first "01" is the Status
event, "03" is the length of the (SUB-)TLV, "01 04" is the (SUB-)TLV itself and
"0c" is the interesting value.
So at every 5th byte the interesting value was found, but the length byte is 3
:-(
But, you are right, I had to fix case tree and case four. case one and two
works fine in my eyes.
6. I simply look at sources of the other DOCSIS dissectors and I've found
nothing like that. Is these an absolutely requirement?
7. not yet. But the fuzz-test.sh runs at the moment.
Excuse my many mistakes I made, but I'm a DOCSIS expert, not a C coder. This is
my first dissector and my first work with ANSI C since over 15 years.
cheers
Hendrik
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
