Your message dated Sat, 24 May 2014 21:31:01 +0200
with message-id <[email protected]>
and subject line Can't reproduce
has caused the Debian Bug report #195299,
regarding nmap: IPv6 mode doesn't seem to do ping tests properly
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
195299: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=195299
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nmap
Version: 3.27-1
Severity: normal
Nmap when used in IPv6 mode (-6) doesn't seem to do ping detection
properly. Session follows...
*snip*
############################################################################
[root@spawn ~]$ ping6 -c1 2001:618:4:17cc:2::69
PING 2001:618:4:17cc:2::69(2001:618:4:17cc:2::69) 56 data bytes
64 bytes from 2001:618:4:17cc:2::69: icmp_seq=1 ttl=61 time=67.5 ms
--- 2001:618:4:17cc:2::69 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 67.527/67.527/67.527/0.000 ms
############################################################################
[root@spawn ~]$ nmap -6 -p22 2001:618:4:17cc:2::69
Starting nmap 3.27 ( www.insecure.org/nmap/ ) at 2003-05-29 21:07 CEST
Note: Host seems down. If it is really up, but blocking our ping probes, try -P0
Nmap run completed -- 1 IP address (0 hosts up) scanned in 24.014 seconds
############################################################################
[root@spawn ~]$ nmap -6 -p22 -P0 2001:618:4:17cc:2::69
Starting nmap 3.27 ( www.insecure.org/nmap/ ) at 2003-05-29 21:09 CEST
Interesting ports on 2001:618:4:17cc:2::69:
Port State Service
22/tcp open ssh
Nmap run completed -- 1 IP address (1 host up) scanned in 0.246 seconds
*snip*
############################################################################
What would make it think that the host isn't up? Version 3.20 had the
same behaviour.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux spawn 2.4.20 #2 Thu Apr 24 23:35:54 CEST 2003 i586
Locale: LANG=C, LC_CTYPE=sv_SE
Versions of packages nmap depends on:
ii libc6 2.3.1-17 GNU C Library: Shared libraries an
ii libgcc1 1:3.3-2 GCC support library
ii libstdc++5 1:3.3-2 The GNU Standard C++ Library v3
-- no debconf information
--- End Message ---
--- Begin Message ---
I have not been able to reproduce the issue with 6.46-1:
$ host google.com
[...]
google.com has IPv6 address 2a00:1450:4005:809::1007
[...]
$ nmap -6 -p80 2a00:1450:4005:809::1007
Starting Nmap 6.46 ( http://nmap.org ) at 2014-05-24 21:25 CEST
Nmap scan report for ham02s12-in-x07.1e100.net (2a00:1450:4005:809::1007)
Host is up (0.079s latency).
PORT STATE SERVICE
80/tcp open http
Nmap done: 1 IP address (1 host up) scanned in 0.24 seconds
I am therefore closing this bug. If there's anything I missed, please
re-open the bug.
Cheers,
-Hilko
--- End Message ---
