Hi,
good point. I tried it out and discovered that nmap doesn't find the open
port when given the -f command line switch.
Then went into my configuration file and en-/disabled couple of nmap options
(only fragmentation in the first place of course) and.... nope. Nessus still
can't find the port open. Then even used the Nessus internal SYN scan but it
still can't find the port open. Actually could this be a bug? Because this
started hapening when I updated to 2.2.4.
Greetz
Chris
----- Original Message -----
From: "George A. Theall" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, September 13, 2005 1:54 PM
Subject: Re: batch mode changes file attributes
On Thu, Sep 08, 2005 at 12:46:59PM +0200, I am WE4SEL wrote:
open port is 1723. Port range I defined in my config file (not
nessusd.conf - see original mail) is default and I just tried 1-12000
with no change in behaviour.
Looking at the config in your original post, I see you're calling
nmap.nasl and telling it to fragment packets; ie,
Nmap (NASL wrapper)[checkbox]:Fragment IP packets (bypasses firewalls)
= yes
yet you don't use the "-f" option when running nmap from a commandline.
If you disable that option, does Nessus then find the port open?
George
--
[EMAIL PROTECTED]
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
