[15147] in bugtraq
Re: Jolt2 crashes tcpdump
daemon@ATHENA.MIT.EDU (Earl T. Carter)
Thu Jun 1 21:00:46 2000
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0035_01BFCB9D.88050E80"
Message-Id: <003801bfcbc7$71615d80$8d20fea9@cisco.com>
Date: Thu, 1 Jun 2000 07:46:44 -0500
Reply-To: "Earl T. Carter" <ecarter@CISCO.COM>
From: "Earl T. Carter" <ecarter@CISCO.COM>
X-To: bugtraq@securityfocus.com
To: BUGTRAQ@SECURITYFOCUS.COM
This is a multi-part message in MIME format.
------=_NextPart_000_0035_01BFCB9D.88050E80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
After further testing, I discovered that problem is not with the tcpdump =
program. The problem lies with Redhat version 6.0. Just launching the =
jolt2 program at the redhat box itself causes the machine to lock up =
(without even running tcpdump). I did not notice this originally =
because it locks up quicker if you are writing to a file with tcpdump =
running. I seem to remember that there were some problems with the =
Redhat kernel when 6.0 was released. These problems were corrected in =
Redhat 6.1. To verify this, I checked everything against a machine =
running Redhat 6.1 and there was no problem.
Earl=20
------=_NextPart_000_0035_01BFCB9D.88050E80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>After further testing, I discovered =
that problem is=20
not with the tcpdump program. The problem lies with Redhat version =
6.0. Just launching the jolt2 program at the redhat box itself =
causes the=20
machine to lock up (without even running tcpdump). I did =
not notice=20
this originally because it locks up quicker if you are writing to a file =
with=20
tcpdump running. I seem to remember that there were some problems =
with the=20
Redhat kernel when 6.0 was released. These problems were corrected =
in=20
Redhat 6.1. To verify this, I checked everything against a machine =
running=20
Redhat 6.1 and there was no problem.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>Earl </FONT></DIV></BODY></HTML>
------=_NextPart_000_0035_01BFCB9D.88050E80--
