Date: Mon, 12 Jun 2006 08:04:28 -0400 From: "Michael Scheidell" <scheidell@secnap.net> To: "talonz" <talonz@gmail.com> Cc: freebsd-security@freebsd.org Subject: RE: Anyone running ntop on FBSD5.4 Message-ID: <B3BCAF4246A8A84983A80DAB50FE7242396BFC@secnap2.secnap.com>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-security@freebsd.org > [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 > > > Remco Bressers wrote: > I had this same problem as well. disable ipv6 or tcp6 using the ntop > flags found in the manual page (man 8 ntop) worked well for me. > Strange, its already disabled in ports in the config. # we currently disable IPv6 CONFIGURE_ARGS+=--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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B3BCAF4246A8A84983A80DAB50FE7242396BFC>