Comment # 27
on bug 8562
from Mathias Guettler
(In reply to comment #26)
> (In reply to comment #25)
> > (In reply to comment #21)
> > > (In reply to comment #19)
> > > > Created attachment 10634 [details]
> > > > Corrigendum of the "ATN Security Label" decoding on CLNP/IDRP PDU's
> > > >
> > > > The traffic type "ATN security label" of IDRP PDUS seems to be incorrectly
> > > > reported as "unknown". Acording to the ATN SARPS "System management" PDU's
> > > > shall be flagged with 0x60 in the Traffic Type section of the "ATN security
> > > > label".
> > >
> > > I'm not at all familiar with these protocols, couldn't google a spec for
> > > this.
> > > Do you have a link?
> > >
> > > I should be able to see this if I filter for clnp.atn.tt, right? Do I need a
> > > different capture file to see the problem?
> >
> > Why not filter for "idrp", "idrp.open.hold-time" etc. ?
> >
> > Using "clnp.xxx" you would get properties of the "clnp" dissector, I guess,
> > but IDRP is a separate dissector.
> >
> > Or what was the question?
>
> You reported the problem that ATN_TT_SYS_MGMT_NO_PREFERENCE has a wrong
> value.
> I tried to find out where this is used and the problem can be seen.
>
> It's used in osi_opt_sec_atn_tt_vals, this is assinged to hf_clnp_atntt. So
> I was hoping to see the problem you reported when I filter clnp.atn.tt.
> However, this did not match any packet in your caputure.
Ah. You my see it in the capture if you open the ATN Security Label (CLNP
Option Field) of a clnp NPDU in the middle panel:
"ISO 8473/X.233 CLNP ConnectionLess Network PDU "->"OPTION Section"->"ATN
Security Label"->"Traffic Type and Routing: Unknown (0x60)"
Instead of "Traffic Type and Routing: Unknown (0x60)" it should read "Traffic
Type and Routing: ATN Systems Management No Preference"
You are receiving this mail because:
- You are watching all bug changes.