Bug#714925: nmap: [REGRESSION 5.00-3 -> 6.00-0.3] -sP fails with "nexthost: failed to determine route to X.X.X.X"

2017-09-18 Thread Timo Lindfors
Hi, On Sun, 17 Sep 2017, Lukas Schwaighofer wrote: Do you still have a similar setup and would you mind checking if that problem is still present? I don't have access to a similar setup at the moment. I'm fine with just closing the bug. -Timo

Bug#714925: nmap: [REGRESSION 5.00-3 -> 6.00-0.3] -sP fails with "nexthost: failed to determine route to X.X.X.X"

2017-09-17 Thread Lukas Schwaighofer
Hi Timo, thanks for the very thorough bug report and for discussing it with upstream. I'm doing a bit of housekeeping of the nmap bugs and tried to determine if this bug is still present. According to upstream [1], this issue might have been mitigated by newer versions of the Linux kernel, in

Bug#714925: nmap: [REGRESSION 5.00-3 - 6.00-0.3] -sP fails with nexthost: failed to determine route to X.X.X.X

2013-07-04 Thread Timo Juhani Lindfors
Package: nmap Version: 6.00-0.3 Severity: normal Steps to reproduce: 1) configure eth0 to use 10.7.0.0/16 subnet 2) Run sudo nmap -n -T normal -sP 10.7.24-34.1-254 Expected results: 2) nmap pings each host in the network Actual results: 2) nmap fails after it has processed 1024 hosts: Starting