Bug 58000 - error in libpcap code (RH specific)
Summary: error in libpcap code (RH specific)
Keywords:
Status: CLOSED DUPLICATE of bug 53692
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: tcpdump
Version: 7.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-01-04 20:11 UTC by Need Real Name
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-01-04 20:11:27 UTC
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.