From b1086ac340271df91fe6670d66eccaf4d90c3a6c Mon Sep 17 00:00:00 2001 From: henri Date: Thu, 1 Mar 2012 09:05:02 +0000 Subject: [PATCH] Added a --nsock-engine option to nmap, nping and ncat to enforce use of a given nsock IO engine. [Henri] --- CHANGELOG | 3 +++ docs/refguide.xml | 17 +++++++++++++++++ ncat/ncat_main.c | 5 +++++ nmap.cc | 5 +++++ nping/ArgParser.cc | 5 ++++- nsock/include/nsock.h | 8 ++++++++ nsock/src/nsock_engines.c | 14 +++++++++++++- nsock/src/nsock_pool.c | 4 ++-- 8 files changed, 57 insertions(+), 4 deletions(-) diff --git a/CHANGELOG b/CHANGELOG index b55396a87..2b2ee9bd1 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -1,5 +1,8 @@ # Nmap Changelog ($Id$); -*-text-*- +o Added a --nsock-engine option to nmap, nping and ncat to enforce use of a + given nsock IO engine. [Henri] + o [NSE] Added support to broadcast-listener for extracting address, native vlan and management IP address from CDP packets. [Tom] diff --git a/docs/refguide.xml b/docs/refguide.xml index bcf38e31a..fcb70f0b3 100644 --- a/docs/refguide.xml +++ b/docs/refguide.xml @@ -2860,6 +2860,23 @@ worth the extra time. + + + + Nsock IO engine + + + +Enforce use of a given nsock IO multiplexing engine. Only the +select(2)-based fallback engine is guaranteed to be +available on your system. Engines are named after the name of the IO +management facility they leverage. Engines currenty implemented are +epoll and select. + + + +