From 2953db4dbd1bc6a58e27bace12204bb338676547 Mon Sep 17 00:00:00 2001 From: Nathanael Bartley Date: Tue, 25 Jul 2017 12:17:37 -0700 Subject: [PATCH] Make clear the local host limitation There seems to be a few places where people are trying to scan their local host (to test, or otherwise). It would be helpful for this to be noted up front. --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 895829e6..3dec4117 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,8 @@ ranges and port ranges. NOTE: masscan uses a **custom TCP/IP stack**. Anything other than simple port scans will cause conflict with the local TCP/IP stack. This means you need to either use the `-S` option to use a separate IP address, or configure your -operating system to firewall the ports that masscan uses. +operating system to firewall the ports that masscan uses. Because +masscan uses a custom stack, it cannot scan the local host. This tool is free, but consider funding it here: 1MASSCANaHUiyTtR3bJ2sLGuMw5kDBaj4T