Hi Michael,
sorry for reviving this almost 9 year old bug, I'm trying to do a bit
of housekeeping :) .
I suspect that what you experienced is a limitation of libdnet (the
library that nmap uses to query the routing table) in combination with
policy routing: It looks like the "default" table is n
Package: nmap
Version: 4.68-1
Severity: important
Nmap is unable to determine route to any addresse which is matched by
the default routing table.
Nmap thus only works for explizit matches from the main table which
renders it completly useless.
# nmap -sS -vvv -p 80 -e ppp0 www.heise.de
Startin
2 matches
Mail list logo