Hi Peter,

Thanks for the help!
It worked for the most part - it didn't find rrd.h after that, in
/usr/local/include, so I copied it to /usr/include and the ./configure then
worked.

Is there a way to compile nfsen without the use or requirement of
Mail::Header and Mail::Internet & related dependencies if I have no plans on
emailing the alerts?

Regards

On Feb 16, 2008 10:33 AM, Peter Haag <[EMAIL PROTECTED]> wrote:

>
>
> --On February 16, 2008 2:36:33 AM -0500 Richard Daemon <
> [EMAIL PROTECTED]> wrote:
>
> | How did you get --enable-nfprofile working?
> |
> | I tried with --with-rrdpath=/usr/local where /usr/local/lib/ has:
> |
> | /usr/local/lib/librrd.a
> | /usr/local/lib/librrd.la
> | /usr/local/lib/librrd.so.0.0
>
> RRD is a bit picky especially under OpenBSD. So
> In your shell (C-shell ex.) set:
>
> setenv LDFLAGS '-L/usr/local/lib -L/usr/X11R6/lib'
>
> rerun ./configure
>
> Enjoy
>
>    - Peter
>
> |
> | Yet I get this error:
> | configure: error: Can not link librrd. Please specify --with-rrdpath=..
> | configure failed!
> | ...
> | Using nfsen 1.3 (latest -stable) and nfdump 1.5.6.
> |
> | I'm not sure what else to try.
> |
> | Now if only someone could make this BSD licensed software as a port. :-)
>
>
> It's on my todo list, as soon as time allows.
>
>
> |
> | On Fri, Feb 15, 2008 at 5:07 PM, Simon Slaytor <[EMAIL PROTECTED]> wrote:
> |
> | > Yes I have four high availability 4.2 firewalls, 8 boxes in total all
> | > sending data to a single nfsen backend which is running on a dedicated
> | > OBSD 4.2 box. All dependent apps/tools are available from ports,
> simply
> | > enable apache in non chroot mode then just compile up the two apps
> from
> | > src.
> | >
> | > Richard Daemon wrote:
> | > >
> | > >
> | > > On Fri, Feb 15, 2008 at 11:17 AM, Simon Slaytor <[EMAIL PROTECTED]
> | > > <mailto:[EMAIL PROTECTED]>> wrote:
> | > >
> | > >     It would take a bit more setting up but what about pfflowd from
> | > >     ports/packages and nfdump/nfsen?
> | > >
> | > >     I use this at work for tracking exactly what's flowing through
> our
> | > >     firewalls i.e. which protocols by who'm to where etc.
> | > >
> | > >     Sounds like exactly what your after.
> | > >
> | > >     http://nfsen.sourceforge.net/
> | > >
> | > >
> | > > Wow, now this looks good!
> | > >
> | > > You have it working with OpenBSD firewalls using pfflowd for
> | > > nfdump/nfsen or are you using nfdump/nfsen with netflows from other
> | > > infrastructure systems?
> |
>
>
>
> --
> Peter Haag

Reply via email to