The kernel has been compiled with 30 bpfs and there are 30 bpf entries in
/dev... The devices are bpf0 through bpf29.

I should note that I have had this same problem on my Solaris 8 box--and I
don't have the opportunity to set any sort of "bpf" device there (haven't
tested it under linux yet... But I have an RH 7.1 box in the wings).
Apologize for the question about the execvp functionality with the two nmap
entries... If I'd studied the function and looked at previously working
sources (and paid a little attention to ptycall.c), I'd have realized my
original assumption was incorrect.

Any other ideas?

Appreciate your time,

Aaron

-----Original Message-----
From: Renaud Deraison [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, January 09, 2002 6:11 AM
To: '[EMAIL PROTECTED]'
Subject: Re: Scan finds no hosts alive--ever--hence, empty report


On Tue, Jan 08, 2002 at 04:15:04PM -0800, SULLIVAN, AARON R (PB) wrote:
> 
>    Ran the most recent cvs version of nessus (1.1.12) on a FreeBSD 4.4
>    x86 box and when I start the scan, it instantly completes with an
>    empty report.  The host is up, ping-able, and scan-able with nmap.  I
>    had been running an ftp downloaded version of 1.1.11 before with the
>    same problem.  The log from the nessusd.messages file is as such:
[...]
>    I seem to see smackings of this from other messages on the list, only
>    those messages are complaining about nmap never completing.  I had
>    been running 1.1.10 before and did not have this problem.  My guess is
>    that the error has something to do with the following line from the
>    log:
>    
>    [Tue Jan  8 14:51:39 2002][62759] Executing on opentty() slave fd 12:
>    execvp (nmap, nmap, -n, -P0, -p, 1-15000, -sT, -O, -r, 
> 64.162.129.53).
>    
>    I may just recall incorrectly... but isn't there only supposed to be
>    one "nmap" in the statement in the execvp line (instead of nmap,
>    nmap)?  I think that might be the problem, but am looking to see if
>    this is a simple, silly problem before I go back and mess with
>    anything more complicated.

Your problem comes from 'ping_host.nasl' (as the host can't be declared dead
by nmap, regardless of the validity of that call, because the option -P0 is
set). Do you have enough bpf's in /dev and in your 
kernel ?

                                -- Renaud

Reply via email to