>Joe Bob wrote:
>>I am currently working on a Yahoo! Messenger program and I am using Ethereal extensively. My problem is this. Under an older version of Messenger, Ethereal could pick up the YMSG packets and sort them into nice sections with no problem. With the latest version, Yahoo! has moved from port 5050 to 119 which is well known to be the NNTP port. I can only assume Yahoo! done this to solve some of their firewall problems. Now when I sniff my Yahoo! Messenger traffic Ethereal tries to read the packets as NNTP. This is completely the wrong protocol and is almost of no value to me. Is there a way to get the old feature back?
I was going to suggest using "Analyze, Decode As" feature, but I don't see YMSG as one of the available options. There is also no way to change the tcp port number under Edit, Preference, Protocols, YMSG.
You might want to shoot an email to the development list for Ethereal asking for the features to be added.
Or you can use something like netdude to modify the pcap file (change all 119 to 5050)
hsb