Wireshark-bugs: [Wireshark-bugs] [Bug 8221] Large SABP messages are not getting decoded
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 24 Jan 2014 07:17:09 +0000

Comment # 10 on bug 8221 from 
(In reply to comment #9)
> (In reply to comment #8)
> > Hello all,
> > 
> > <<PER dissector does not support yet a length determinant >= 16K (X.691
> > chapter 10.9.3.8).>>
> > 
> > Can somebody explain what does length determinant exactly means? Does it
> > mean the maximum number of bytes SABP should have?
> 
> Some PER structures has a length indication in this case the length is > 16K
> which means that it will be segmented if I remember correctly, there is no
> code
> yet to handle segmented PER so it's impossible to parse the message.
> Implementig PER reassembly would be quite complicated and no one has tried
> to do that yet.
> So the chanses of some one fixing this is slim.

Thanks for the reply. So, if the number of bytes transferred from TCP to SABP
is greater than 16K, then it will be a segmented PER and since reassembly of
segmented PER is still not supported, it will give abnormal results.

And the way I understand, length determinant == Number of bytes passed from TCP
to SABP. Am I right?

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