http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2514
--- Comment #3 from Andy Levin <levina@xxxxxxxxxxxx> 2008-05-02 07:51:11 GMT ---
(In reply to comment #0)
> Created an attachment (id=1762)
--> (http://bugs.wireshark.org/bugzilla/attachment.cgi?id=1762) [details]
> pcap contains a series of fragmented GTP packets.
> Build Information:
> Version 0.99.5 (SVN Rev 20677)
> Copyright 1998-2007 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> Compiled with GTK+ 2.10.7, with GLib 2.12.7, with WinPcap (version unknown),
> with libz 1.2.3, with libpcre 6.4, with Net-SNMP 5.4, with ADNS, with Lua 5.1,
> with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio
> PortAudio V19-devel, with AirPcap.
> Running on Windows XP Service Pack 2, build 2600, with WinPcap (3.0), without
> AirPcap.
> Built using Microsoft Visual C++ 6.0 build 8804
> Wireshark is Open Source Software released under the GNU General Public
> License.
> Check the man page and http://www.wireshark.org for more information.
> --
> When this same version if Wireshark and WinPcap is run on Windows 2000 and XP,
> the pcap file I open produces a list of packets quite different between the 2
> os. The Wireshark running on the Windows 2000 system produces the correct
> list.
> I have attached the pcap file.
(In reply to comment #2)
> If the two installations have identical configuration files they show identical
> dissections. How are the configurations made identical? Are the config files
> copied?
> I don't have these two configurations available, so can't test it myself.
I went through the preferences, paying close attention to the GTP protocol
settings. What is the config file name and where can I find it. I will copy
it from one system to the other, try again and report the results.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.