latest 2.0.0j unhappy

Carter Bullard carter at qosient.com
Thu Sep 28 12:48:59 EDT 2000


Hey Peter,
   Well this is the time stamp problem.  I put a hard
stop in the program to tell us if it was Argus or
Libpcap that was causing the problem.  Definitely
Libpcap.

   Seems that libpcap returned a bad timestamp.
What version of libpcap are you using.  V0.5?

Carter


-----Original Message-----
From: owner-argus at lists.andrew.cmu.edu
[mailto:owner-argus at lists.andrew.cmu.edu]On Behalf Of Peter Van Epp
Sent: Thursday, September 28, 2000 12:29 PM
To: argus
Subject: latest 2.0.0j unhappy


	The latest 2.0.0j is unhappy:

root    5191  0.9  0.4  3572 2308  p0  S     9:16AM   0:00.06
argus_bpf -irl0 -P0 -m -w argus.log
root    5192  0.0  0.1  1904  628  p0  S     9:16AM   0:00.01
argus_bpf -irl0 -P0 -m -w argus.log
root    5193  0.0  0.1  1908  612  p0  S     9:16AM   0:00.03
argus_bpf -irl0 -P0 -m -w argus.log
root       0  0.0  0.0     0    0  ??  DLs  Tue11AM   0:00.07  (swapper)
demoa# argus_bpf[5191]: -751182481.-1158019072 : ArgusError ArgusEtherPacket
(0x0, 0x81c06d0, 0x81c06e2) libpcap timestamp out of range
tv_sec -751182481.-1158019072

and now dead:

root    5192  0.0  0.1  1904  628  p0  S     9:16AM   0:00.30
argus_bpf -irl0 -P0 -m -w argus.log
root    5193  0.0  0.1  1908  612  p0  S     9:16AM   0:00.79
argus_bpf -irl0 -P0 -m -w argus.log
root       0  0.0  0.0     0    0  ??  DLs  Tue11AM   0:00.07  (swapper)

	It doesn't appear to have cored, just died quietly.

Peter Van Epp / Operations and Technical Support
Simon Fraser University, Burnaby, B.C. Canada
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20000928/36ab74ac/attachment.html>


More information about the argus mailing list