freebsd security - Jun 2006 - Anyone running ntop on FBSD5.4

If you are running ntop on 5.4, what compile options?
Use ports version? Or surgefile tarball?

It makes a great security forensics tools, but I can't get it to stop
segfaulting.Was wondering if anyone found a fix for it.

-- 
Michael Scheidell, CTO
561-999-5000, ext 1131
SECNAP Network Security Corporation
Take a vacation from spam: http://www.spammertrap.com

>If you are running ntop on 5.4, what compile options?
>Use ports version? Or surgefile tarball?
>
>It makes a great security forensics tools, but I can't get it to stop
>segfaulting.Was wondering if anyone found a fix for it.
>
I had the same problems on FreeBSD 5.4. Ntop keeps segfaulting. After an
upgrade to 6.0-RELEASE it works flawlessly.
No clue what the problem was :o).

Regards,

Remco Bressers

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