ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 1690] Feature request: Support EBCDIC display for DRDA pro

Date: Mon, 19 Nov 2007 20:47:26 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1690





------- Comment #7 from stephentfisher@xxxxxxxxx  2007-11-19 20:47 GMT -------
I have modified my local Wireshark to display each piece of data
(drda.param.data) in ASCII straight out of the packet and also converted into
EBCDIC:

V DRDA (Exchange Server Attributes)
  > DDM (EXCSAT)
   V Parameter (External Name)
           Length 23
           Code point: EXTNAM (0x115e)
           Data (ASCII): \304\302\362\311\325\342\343\361K\363\363@@@@@@@@
           Data (EBCDIC): DB2INST1.33

Is this a good approach to displaying it?  I don't use the DRDA protocol, so
your suggestions are welcome.  A comment at the top of the source code says
that the data is always EBCDIC unless otherwise negotiated.  Do you know how
that negotiation works or if it is ever used?  If it isn't used, we could just
display the data field once with EBCDIC conversions and not display the
straight ASCII display.  Finally, are there any other fields in the DRDA
protocol that need to be converted from EBCDIC to ASCII for display in
Wireshark?


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.