Does Ethereal really *hang* or does it only take a lot of time to display
the stream in EBCDIC format? The reason for this question, is that
internally Ethereal needs to reread and reprocess the whole TCP stream
(parts of which are saved as a temporary file in your temp folder; that'd be
in Documents and Settings\<user name>\Local Settings\Temp on a Win2k/XP
system, and its name looks like followXXXXsomething).
I tried to convert from ASCII to EBCDIC on a TCP stream consisting of 264
packets in a capture file containing about 24000 packets, and it took
several seconds to complete. Hexdump and C string generation even took much
longer.
Regards,
Olivier
-----Original Message-----
From: Ron Norton
I just installed 0.10.4 on w2k sp3. Removed 0.10.3 to do that.
Have 682k trace of a tn3270 conversation which contains telnet frames with
ebcdic content. If I do a "follow tcp stream", get the ascii display of the
stream, and try to click ebcdic or hex, ethereal hangs, and I have to force
end the program.
0.10.3 same file same process is ok.
winpcap 3.0 is in use.
Is this a known? Am I missing some new config or set up thing I should be
doing for 0.10.4?
0.10.4 seems to have some nice changes.
Thanks,
Ron Norton