Closed rye closed 4 years ago
nmap
from the host does just fine, whereas nmap
from inside the scanner
container seems to encounter big trouble:
Host:
$ nmap [REDACTED]
Starting Nmap [REDACTED] ( http://nmap.org ) at 2019-11-01 08:24 CDT
Nmap scan report for [REDACTED]
Host is up ([REDACTED] latency).
Not shown: 998 closed ports
PORT STATE SERVICE
80/tcp open http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 4.51 seconds
Container:
$ docker-compose exec scanner /bin/bash
root@scanner:/# nmap [REDACTED]
Starting Nmap 7.40 ( https://nmap.org ) at 2019-11-01 13:25 UTC
Nmap scan report for [REDACTED]
Host is up (0.00066s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
80/tcp open http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 90.48 seconds
These have been resolved since I switched to the host
networking mode… in fact, it was the scanner plugins timeout so switching to host networking might not have been necessary.
In scanning a VOIP vlan, it seems like we run into inconsistency with UDP; tcpdump doesn't see any of the return traffic. Take a look.