From owner-freebsd-security@FreeBSD.ORG Mon Jun 12 12:04:29 2006 Return-Path: X-Original-To: freebsd-security@freebsd.org Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A753D16A41F for ; Mon, 12 Jun 2006 12:04:29 +0000 (UTC) (envelope-from scheidell@secnap.net) Received: from secnap2.secnap.com (secnap2.secnap.com [204.89.241.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D36643D4C for ; Mon, 12 Jun 2006 12:04:29 +0000 (GMT) (envelope-from scheidell@secnap.net) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 12 Jun 2006 08:04:28 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Anyone running ntop on FBSD5.4 Thread-Index: AcaNru/ctWYsbcN3RWePt4ff2VYFsAAaDlIg From: "Michael Scheidell" To: "talonz" Cc: freebsd-security@freebsd.org Subject: RE: Anyone running ntop on FBSD5.4 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jun 2006 12:04:29 -0000 > -----Original Message----- > From: owner-freebsd-security@freebsd.org=20 > [mailto:owner-freebsd-security@freebsd.org] On Behalf Of talonz > Sent: Sunday, June 11, 2006 7:28 PM > To: Remco Bressers > Cc: freebsd-security@freebsd.org > Subject: Re: Anyone running ntop on FBSD5.4 >=20 >=20 > Remco Bressers wrote: > I had this same problem as well. disable ipv6 or tcp6 using the ntop=20 > flags found in the manual page (man 8 ntop) worked well for me. >=20 Strange, its already disabled in ports in the config. # we currently disable IPv6 CONFIGURE_ARGS+=3D--disable-ipv6 Tried -4, still, when I go to Summary->Traffic page, when it finally gets to bottom, it segv's Gdb shows it in myrrd library. Working with ntop people now to trace it down. Looks like there has been a long history of failures with ntop going back to 4.xx. Maybe it can finally be fixed.