Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Re: Latest Nmap = Segmentation fault
From: Lionel Cons <lionel.cons () cern ch>
Date: Tue, 4 Dec 2007 12:11:20 +0100

Diman Todorov writes:
okay, I seem to have misjudged your problem. I committed a fix to the  
svn repository.

It works fine. I don't get the segfault anymore. Thanks.

But just on a side note, what are you trying to accomplish?

I'm trying to detect RMCP (Remote Management and Control Protocol)
support. As this may come from some hardware (BMC = Baseboard
Management Controller) and from not the operating system, the port
may appear to be closed.

Here are real life traces:

Nmap tests the port:

11:51:04.839450 IP scanner.63476 > target.623: UDP, length 0

The OS replies that nothing runs there:

11:51:04.851190 IP target > scanner: icmp 36: target udp port 623 unreachable

The NSE script sends a well crafter packet:

11:51:04.860910 IP scanner.41480 > target.623: UDP, length 12

The OS replies that nothing runs there:

11:51:04.872635 IP target > scanner: icmp 48: target udp port 623 unreachable

But the hardware replies:

11:51:04.887943 IP target.623 > scanner.41480: UDP, length 28

So Nmap really thinks that the port is closed, so it seems I cannot
use a port rule.

Cheers,

Lionel

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


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]