Note that there are some explanatory texts on larger screens.

plurals
  1. PONmap: server stops accepting new connections after nmap runs
    text
    copied!<p>I have a CentOS 6 server with nmap 5.51 installed on it. I issue the following command:</p> <pre><code>nmap -sS -PN -p1-1024 --traceroute --reason -O -sV {My IP} -vv (This is all "don't quote me") -sS is a type of scan where TCP connections are not fully established -PN means skip checking if host is online -p1-65535 is the port range --traceroute means add traceroute --reason "Shows the reason each port is set to a specific state and the reason each host is up or down." -O means OS detection -sV detects the version of the program listening on each port -vv means "be verbose" </code></pre> <p>So anyway... I run this command, wait a few minutes, it prints the result and EXITS. I open another terminal window (or tab), try to connect to that same server through SSH... And the connection times out. This happens every time, and only after running nmap. Rebooting is the only thing that fixes it. </p> <p>It seems that if I already have a connection, it keeps communicating, but new ones get refused. Like I said, nmap has already exited, and I made sure it's not in the process list (ps uax | grep nmap). </p> <p>And another thing, the weirdest of all: everything is fine while nmap runs. It's when it goes away that shenanigans start.</p> <p>But this is not consistent. When I added the argument -T2 ("polite" scanning), the server went down instantly, including existing connections.</p> <p>What next?</p> <p>Note that the server that screws up is the one that does the scanning, not the target.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload