Wireshark-bugs: [Wireshark-bugs] [Bug 10691] BACnet protocol: Dissection error after exception s
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 12 Nov 2014 07:25:38 +0000

Comment # 4 on bug 10691 from 
(In reply to Christoph Jähnigen from comment #3)
> The capture contains invalid data: the event priority of a
> BACnetSpecialEvent is an Unsigned in the range of 1 to 16, but in capture a
> value of 0 is set. I could agree that the dissection error message could be
> more specific.

That is right. In the scope of an BACnet application the value is "out of
range". But in the scope of the telegram/message it is a valid message (valid
BACnet ASN.1). Continuing dissection of telegramdata is not influenced.
Highliting of the invalid value would be nice.

But nevertheless, I retried it with a valid event priority (value 8) and the
result was the same. Dissection stopped with "something is going wrong here
!!". See new attachment.

You are receiving this mail because:
  • You are watching all bug changes.