Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: Re: [Wireshark-users] ISDN Layer 3 decode

From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Sat, 22 Oct 2011 12:24:40 -0700
On Oct 22, 2011, at 11:13 AM, Keith French wrote:

> The software that I would really like to load into Wireshark is Aethra's PC_108XP. This software serves as the expert software for many of their analysers and I think now that the "Export to Ethereal" option (I take your point about the possible age of formats here), is only for their ADSL & Ethernet analysers, not my ISDN, & Q.Sig analyser. Capinfos cannot open its native .aps format,

Well, if you have some .aps files and the corresponding "export as text" dumps, we might e able to reverse-engineer the format.

> using the Export to Ethereal to a .cap shows up in capinfos as:-
> 
> File name:           C:\Users\Keith\Desktop\Environment Agency\QSig Traces\test.cap
> File type:           Wireshark/tcpdump/... - libpcap
> File encapsulation:  OpenBSD PF Firewall logs, pre-3.4

Well, somebody at Aethra screwed up big-time there.  They chose 17 as the link-layer type value; I doubt they were *so* crazy as to think that a PF log would be the right format, so they were probably looking at some non-OpenBSD system that didn't use 17 for some other purpose and decided "hey, this is available" without bothering to tell the Ethereal/Wireshark developers.  Maybe they wrote their own plugin for Ethereal/Wireshark or built their own modified version.

> Hence why I think my best bet (if it is even possible) is to take the Layer 3 hex (and L2 if needed) & some how use text2pcap to try & load it into Wireshark.

If the frame begins with a LAPD header, try using 203 as the DLT_ value in text2pcap (after tweaking the hex dump if necessary to make text2pcap handle it).

> The other analyser that I have borrowed that can output its D channel decode to Wireshark is called a "Mty Eye"

As soon as I saw "Eye" I wondered whether this was at all related to Innoventif's EyeSDN capture devices:

	http://www.innoventif.com/

> from MOESARC TECHNOLOGY UK LTD. As I mentioned before it uses a .TRC file, which Wireshark can read and running capinfos on it shows:-
> 
> File name:           C:\Users\Keith\Documents\Mty Eye Analyser\Lab Traces\Mty Eye QSig Trace.trc
> File type:           EyeSDN USB S0/E1 ISDN trace format

...and, sure enough, I was right.  They might be reselling the EyeSDN boxes under their own name - they're listed as a distributor:

	http://www.innoventif.com/4_1_0.html

Innoventif contributed support to Ethereal/Wireshark to read their file format.