Wireshark-bugs: [Wireshark-bugs] [Bug 9427] Dissector for T1-channels-over-raw-Ethernet protocol
Mike Petersen
changed
bug 9427
| What |
Removed |
Added |
| CC |
|
mbp@guisys.com
|
Comment # 18
on bug 9427
from Mike Petersen
> "Next" in what sense?
> Are we talking about the next *frame* on the *same* T1, or are we talking about multiple T1s on a T3?
We're taking about the next frame of the same T1. The data is sequential and
contiguous from the one selected T1.
> I.e., each frame in the capture has 7680 sequential bits from the T1?
Yes. Each Frame has 960 sequential octets or 7680 sequential bits of the same
T1.
> And that T1 is carrying Frame Relay traffic? Is that traffic using the full T1, or is this fractional T1?
It is my understanding that the Frame-Relay traffic of interest occupies the
full-T1.
This is a custom feature designed for Brett to provide a means to collect
long-term Frame-relay data streamed into a T1 then Mux'd into a DS3. The
access point is a DS3 and the data of interest is the Frame-Relay content
within one T1 of that DS3. To facilitate Long Term collection of this data for
comparative analysis to the data prior to insertion into the T1, and
subsequently into the DS3. Access at a DS3 or T1 and transfer of payload into
raw Ethernet Frames provides an ideal means for long term collection of this
data into a pcap format which in turn provides the means for subsequent decode
and analysis.
This feature is also anticipated to be of great value in the Network migration
from TDM to packet - especially in addressing Special Services (BRI, DDS,
4-wire analog, etc.). Many of these 'Specials' are outside standard IEEE
definitions as they are no longer widely deployed - so new methods must be
deployed address interim support for these services within both the TDM and
Packet networks.
You are receiving this mail because:
- You are watching all bug changes.
