Re: [SoC Patch] host and port state reasons - new and improved

["Eddie Bell" <ejlbell () gmail com>]

hey alex,

I thought I had fixed that bug but I just tried it on localhost and I get
the same result. Although if I try it on my ethernet interface it works. I
believe it is because nmap does not send a ping to the host it is scanning
from, it just assumes it is automatically up. Ill take another look and see
if I can fix it

thanks
 - eddie

On 22/06/06, Alex Prinsier <aphexer () mailhaven com> wrote:
> Hello,
>
> I was checking which hosts were up on the network and I got this line
> with the --reason:
> Host xxx.access.telenet.be (81.165.xxx.xxx) appears to be up, received
> no-response
>
> "no-response" doesn't seem a logic reason for being up to me :) Though
> that particular host was the host I was scanning from. I'm not sure how
> nmap handles that. All other hosts scanned gave normal results like
>
> Host xxx2.access.telenet.be (81.165.xxx.xxx2) appears to be up, received
> echo-reply
>
> or Host 81.165.xxx.xxx3 appears to be down, received no-response
>
> So there only seems something wrong when my own host is part of the
> network being scanned.
>
> I'm not sure what you should change, but "no-reponse" is not a valid
> reason for being up (as far as i know :)).
>
> The scan command was: nmap -sP -T4 -v -v --send-ip --reason 81.165.xxx.0
/24
> Btw: great patch ;)
>
> Alex


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev