Hi, Guy,
Thanks for your help. Now I can successfully
compile ethereal 0.9.5. It is really a piece of art.
During my compilation and usage of the software, I
realized several things.
1) If you open any packet-xxx.c file in Microsoft
Visual Studio 6.0 on Windows platform, for example,
packet-tcp.c, and save it in Visual Studio without
modifying anything, you can NOT recompile it
successfully. The nmake crashes when auto-generating
register.c with either python or sh. I guess that is
caused by the fact that packet-xxx.c is developed in
LINUX or UNIX version, and when it is saved in Visual
Studio 6.0 on Windows platform, the end-of-line
character is changed from the UNIX style to Windows
style. Then the python or sh script could not parse
it successfully. If it is the case, then it is a bug
in compilation script (for both python and sh).
2) When ethereal started catching the packets,
although all the packets were successfully caught, I
could not read the packet payload, e.g. the email
contents. In the lowest panel, there are only numbers
and weird characters. I just wonder whether those
weird characters are UNICODE or they need to be
decoded. Basically, my question is "how can I read
the contents or payloads of the packets", instead of
only the source/destination addresses and ports.
3) On the interface of ethereal, I clicked on 'Edit'
menu, then 'Preferences' menu, and then 'TCP Streams'
button. I saw on the right panel a lot of color
adjusters for server and client. What are the
meanings of those color adjusters? What are the
server and the client? I surfed all the documentation
on your web site, but could not find any explanation.
I really appreciate your time in thinking about
those questions. If you have time, would you please
drop me a line?
Have a great holiday.
John
__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com
