Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 58000

Summary: error in libpcap code (RH specific)
Product: [Retired] Red Hat Linux Reporter: Need Real Name <dbrumley>
Component: tcpdumpAssignee: Harald Hoyer <harald>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-01-04 20:11:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2002-01-04 20:11:22 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; SunOS 5.8 sun4u)

Description of problem:
libpcap code in RH 7.2 seems to have an error.  In tcpdump you can see the
problem:
command: ./tcpdump -n -i eth0
...some data....
-2147415483 packets received by filter
-1073744432 packets dropped by kernel

This is in libpcap, not tcpdump AFAIK because other apps, such as argus
(http://www.qosient.com) linked against libpcap have no problem.  Also, I
deinstalled
RH libpcap and insatlled the version (made from source) from tcpdump.org
and
everything worked fine on argus. 

I reproduced the problem rebuilding tpcdump.src.rpm from scratch, so it's
not just
a binary issue...it's somewhere (probably) in the RH patches.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. See above.
2.
3.
	

Actual Results:  negative byte counts in output of tcpdump. libpcap
related.

Expected Results:  negative byte counts don't make sense. should be
positive.

Additional info:

Note this isn't just an uninit int error...other applications linked
against RH libpcap
will not work from mysterious errors.  Once libpcap was replaced with the
version
from tcpdump.org, those errors go away.

Comment 1 Harald Hoyer 2002-01-07 10:36:40 UTC

*** This bug has been marked as a duplicate of 53692 ***