Nmap Development mailing list archives

Re: NPing running out of sockets


From: David Fifield <david () bamsoftware com>
Date: Mon, 4 Oct 2010 12:17:50 -0600

On Sat, Oct 02, 2010 at 03:30:54PM +0200, Luis MartinGarcia wrote:
On Fri, Oct 1, 2010 at 5:20 PM, Patrik Karlsson <patrik () cqure net> wrote:
While testing the broadcast functionality per Davids instructions [1] I ran into some trouble with Nping.
It seems as if sockets are not released properly and slowly increase with each packet being sent.
After 252seconds I'm out of sockets on my OS X system. The error looks like this:

SENT (246.2010s) UDP packet with 20 bytes to 255.255.255.255:67
SENT (247.2020s) UDP packet with 20 bytes to 255.255.255.255:67
SENT (248.2020s) UDP packet with 20 bytes to 255.255.255.255:67
SENT (249.2030s) UDP packet with 20 bytes to 255.255.255.255:67
SENT (250.2040s) UDP packet with 20 bytes to 255.255.255.255:67
SENT (251.2040s) UDP packet with 20 bytes to 255.255.255.255:67
SENT (252.2040s) UDP packet with 20 bytes to 255.255.255.255:67
Socket troubles: Too many open files
Assertion failed: (nse->iod->sd >= 0), function nsp_add_event, file nsock_core.c, line 1239.
Abort trap

Thank you for reporting this. I'm away on holidays, but I'll fix this
when I get back, in a couple of weeks.

I think that the pending nsock_setup_udp could be used to solve this.
Instead of creating one new iod with a socket for every "connection,"
you could use one unconnected socket for all sends and receives.

Patrik, a workaround is to run as root.

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


Current thread: