Command line client showing wrong port range

Hi List,

actually this is not too much of a problem but still I'm wondering why it is
doing this.

I have a configfile that the nessus command line client uses to get the scan
configuration. The scan itself is started like this:

   nessus -T nbe -xqV -c <configfile> <server> <port> <user> <password>
<hostfile> <reportfile.nbe>

Now, in my configfile it clearly says

   port_range = 1-10000

but the console output of nessus shows

   portscan|<host>|0|65535
   portscan|<host>|65535|65535

I sometimes use other configfiles that go up to port 65535 and I'm not sure
if I remember it right but when first run with 10000 ports without having
run the 65535 ports before it displayed it correctly.
Well, I tried to analyze this a little with tcpdump and it looks like as if
only ports up to 10000 are scanned but I haven't figured out yet how to set
up a precise filter that only shows the packets I want ( if anyone knows one
plz let me know). My filter (dst host <target IP> and src host <myIP>) only
captures around 800 packets during the nmap.nasl execution.
Now, the Nmap option USER SPECIED RANGE is obsolete, right?

Btw, this happens with version 2.2.4 and it did with 2.2.2.

Anything I'm doin wrong here?

Greetz
Chris

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus