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

Wireshark-dev: [Wireshark-dev] SNA Trace on VMS

Date: Fri, 10 Nov 2006 16:34:45 -0000
Title: SNA Trace on VMS

Hi

I use Wireshark to analyze TCP trace files collected on a VMS platform, and it works fine.

I'm trying to work out how to get Wireshark to parse SDLC-SNA Trace files collected on a VMS platform.

I know that the VMS TCP analysis uses the file vms.c and that there is a link to vms_open() from file_access.c and it sets the "file_encap" to WTAP_ENCAP_RAW_IP.

I guess that for the SNA trace file I'll need a vms_sna.c, vms_open_sna() and a link to vms_open_sna() from file_access.c. But will I need to add a new WTAP_ENCAP_SNA?

And I don't understand how I build the links to the existing SNA modules in packet-sna.c or even packet-sdlc.c!

Can anyone give me some clues please?

Thanks

Trefor

Example Trace


Gateway node DEMSAC     Physical Unit SNA-0
(Protocol version = 2.0.0, Buffering level = 10, Data size = 256)

R 11:02:10.60 TH=2C000101005E RH=0B90A0 RU=211. bytes     (005,00000001)
              FID2,OS,DAF=01,OAF=01,SNF=005E
              RQ,FMD,FI,BCI,ECI,DR1I,ERI,BBI,CDI
              2E05 02FF 0003 D100 0004 4D48 5350 0019 : ......J..\(\\&..
              10C7 C2C2 E3D3 E4E3 4BC1 F2E4 C3C9 C3C9 : .GBBTLUT.A2UCICI
              F1AF 1F0A F205 4E00 0204 60C1 C2C9 00A5 : 1\.\2.+..\-ABI.v
              12FF 3035 3130 3031 3533 3030 3530 3030 : ..\\\\\\\\\\\\\\
              3034 3030 3031 3030 3630 3030 3031 3130 : \\\\\\\\\\\\\\\\
              3037 3030 3033 3030 3038 3030 3031 3244 : \.\\\\\\\\\\\\.\
              4159 3330 3030 3337 3030 2030 3039 3030 : \\\\\\\.\\\\\\\\
              3030 3253 5430 3130 3030 3030 3132 3031 : \\.\\\\\\\\\\.\\
              3130 3030 3138 3031 3730 3030 3031 3130 : \\\\\\\\.\\\\\\\
              3138 3030 3030 3139 3530 3030 3030 3531 : \\\\\\\\\\\\\\\\
              3332 3530 3030 3034 444F 4345 3332 3630 : \.\\\\\\\!\\\.\\
              3030 3033 3030 3135 3134 3030 3032 3032 : \\\\\\\\\\\\\.\.
              3039 3030 3031 3230 3139 3132 3530 3538 : \\\\\\.\\\\.\\\\
              3533 20                                 : \\\
T 11:02:10.84 TH=2D000101805E RH=4B8000 RU=5. bytes       (005,00000001)
              FID2,OS,EFI,DAF=01,OAF=01,SNF=805E
              RQ,DFC,FI,BCI,ECI,DR1I
              C900 0100 01                            : I....
T 11:02:10.85 TH=2C000101002F RH=039020 RU=68. bytes      (005,00000001)
              FID2,OS,DAF=01,OAF=01,SNF=002F
              RQ,FMD,BCI,ECI,DR1I,ERI,CDI
              0044 12FF 3035 3230 3030 3536 3030 3530 : .\..\\.\\\\\\\\\
              3030 3031 3130 3036 3030 3030 3131 3030 : \\\\\\\\\\\\\\\\
              3730 3030 3330 3030 3830 3030 3132 4441 : .\\\\\\\\\\\\.\\
              5933 3030 3033 3730 3020 3030 3930 3030 : \\\\\\.\\\\\\\\\
              3032 5354                               : \.\\
R 11:02:10.89 TH=2D000101805E RH=CB8000 RU=1. byte        (005,00000001)
              FID2,OS,EFI,DAF=01,OAF=01,SNF=805E
              +RSP,DFC,FI,BCI,ECI,DR1I
              C9                                      : I
R 11:02:10.90 TH=2C000101005F RH=4B9001 RU=5. bytes       (005,00000001)
              FID2,OS,DAF=01,OAF=01,SNF=005F
              RQ,DFC,FI,BCI,ECI,DR1I,ERI,CEB
              0400 0600 00                            : \.\..