[Ntop] Compile warning on FreeBSD 4.4: setkey(3) not present in the system!

2001-11-29 Thread Scott Hanson
Hello, We're trying to get ntop-2.0-pre working under FreeBSD 4.4. However, we're getting the warnings below when compiling. We got the warnings with ntop-beta3 as well. The crypt libraries are present, and according to ldd are linked in. ntop seems to run, although it's been up for only a day,

Re: [Ntop] Compile warning on FreeBSD 4.4: setkey(3) not present in the system!

2001-11-29 Thread Stanley Hopcroft
Dear Sir, I have compiled ntop-2.0-pre on FreeBSD 4.3-RELEASE and I get the same warnings (IIRC). However, ntop works fine, as far as I have been able to test it. Its is not an issue to me. Thank you, Yours sincerely. --

Re: [Ntop] Compile warning on FreeBSD 4.4: setkey(3) not present in the system!

2001-11-29 Thread Luca Deri
Scott, the warnings you mention are not a problem although they should be removed. I don't have FreeBSD here. A while ago, when i compiled ntop under BSD, the gethostbyaddr() system call as broken causing ntop to eat up all the CPU cycles. For this reason there's a patch in the code (only for

Re: [Ntop] Compile warning on FreeBSD 4.4: setkey(3) not present in the system!

2001-11-29 Thread Luca Deri
Scott, the warnings you mention are not a problem although they should be removed. I don't have FreeBSD here. A while ago, when i compiled ntop under BSD, the gethostbyaddr() system call as broken causing ntop to eat up all the CPU cycles. For this reason there's a patch in the code (only for

Re: [Ntop] Compile warning on FreeBSD 4.4: setkey(3) not present in the system!

2001-11-29 Thread Luca Deri
Scott, the warnings you mention are not a problem although they should be removed. I don't have FreeBSD here. A while ago, when i compiled ntop under BSD, the gethostbyaddr() system call as broken causing ntop to eat up all the CPU cycles. For this reason there's a patch in the code (only for