http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1454
Summary: messenger packets ok after pp0 but malformed after eth0
Product: Wireshark
Version: SVN
Platform: PC
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: toralf.foerster@xxxxxx
Build Information:
tfoerste@n22 ~/devel/wireshark/trunk $ ./tshark -v
TShark 0.99.6 (SVN Rev 21067)
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 GLib 2.12.9, with libpcap 0.9.5, with libz 1.2.3, with libpcre
6.6, with Net-SNMP 5.2.1.2, without ADNS, without Lua, with GnuTLS 1.4.4, with
Gcrypt 1.2.2, without Kerberos.
Running on Linux 2.6.19-gentoo-r5, with libpcap version 0.9.5.
Built using gcc 3.4.6 (Gentoo 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.10).
--
I'm not sure whether it's a problem and if - whether it's a wireshark problem
or a problem of my Gentoo system:
I'm wondering why all messenger packets looks nice if I choose ppp0 as an
interface whereas each messenger packets is market as malformed if I choose
eth0 as an interface.
Sometimes ago I filed bug #1270 which might be related to this effect - I
didn't realized at that time that the packets are malformed only if eth0 was
choosed.
Or is the described behaviour a side effect from "UDP checksum offload" of my
e1000 card ?
--
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.