Wireshark-bugs: [Wireshark-bugs] [Bug 10280] Frame Relay dissector doesn't handle X.25-over-Fram
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 10 Oct 2014 20:42:28 +0000

Comment # 9 on bug 10280 from 
(In reply to ton schoenmakers from comment #8)

> What I have been able to determine from the traces taken, is that the complete
> X.25 packet is stripped of it's Preamble and Frame Check Bytes, then
> encapsulated with a 2-Byte FR header and a 2-Byte FCS trailer.

So "complete X.25 packet" refers to LAPB and the X.25 Packet Layer Protocol. so
the Frame Relay payload begins with a LAPB address?

> Vanguard claims to use the Annex-G protocol, but the only
> reference to that I have been able to locate in the ITU Recommendation X.25
> (10/96) and those do not make sense to me.

You, too? :-)

ITU-T Recommendation X.25 does, indeed, have an Annex G.

So does ANSI T1.617 and, according to the Frame Relay Forum's FRF.3.2 Frame
Relay Multiprotocol Encapsulation Implementation Agreement:

    https://www.broadband-forum.org/technical/download/FRF.3/FRF.3.2.pdf

"I.555 Section 5 was formerly known as ANSI T1.617 Annex G" (see footnote on
page 8).

The latter Annex G appears to be what the references to "Annex G" for
X.25-over-Frame Relay are talking about.

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