Nmap Development mailing list archives
Nmap's nc version fails to correctly do IPv4 fallback
From: Quanah Gibson-Mount <quanah () zimbra com>
Date: Tue, 18 Nov 2014 10:51:49 -0800
Unlike the OpenBSD "nc", the version from nmap fails to correctly fall back to ipv4 if it is unable to connect to the ipv6 address of a system.
Using OpenBSD "nc": [zimbra@zre-ldap003 ~]$ nc -v localhost 7171 nc: connect to localhost port 7171 (tcp) failed: Connection refused Connection to localhost 7171 port [tcp/*] succeeded! Using nmap's nc: nc: connect to localhost port 7171 (tcp) failed: Connection refusedAnd then no fallback. This is problematic in particular with "localhost", where most systems now have:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
--Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration _______________________________________________ Sent through the dev mailing list http://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- Nmap's nc version fails to correctly do IPv4 fallback Quanah Gibson-Mount (Nov 18)
- Re: Nmap's nc version fails to correctly do IPv4 fallback Daniel Miller (Nov 18)
- Re: Nmap's nc version fails to correctly do IPv4 fallback Quanah Gibson-Mount (Nov 18)
- Re: Nmap's nc version fails to correctly do IPv4 fallback Fyodor (Nov 18)
- Re: Nmap's nc version fails to correctly do IPv4 fallback Daniel Miller (Nov 18)