Nmap Development mailing list archives

Re: optional ipv6 support


From: "Rick \"Zero_Chaos\" Farina" <zerochaos () gentoo org>
Date: Sat, 02 Feb 2013 12:00:20 -0500

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/30/2013 01:06 AM, David Fifield wrote:
On Tue, Jan 29, 2013 at 10:24:12PM -0500, Rick "Zero_Chaos" Farina wrote:
Currently the only ipv6 related things happening in configure.ac is this:

dnl Check IPv6 raw sending flavor.
CHECK_IPV6_IPPROTO_RAW

This means that when configure runs it checks libpcap for ipv6 support
and enables if it finds support.

For many reasons, this is not a great thing.  So call "automagic
dependencies" [1] cause a great deal of heartache when things are
rebuilt or binaries are transfered to other systems.  Would it be
possible to add --enable-ipv6 --disable-ipv6 flags like in nbase?

# Check for IPv6 support -- modified from Apache 2.0.40:

AC_ARG_ENABLE(ipv6,
  [  --disable-ipv6          Disable IPv6 support ],
  [ if test "$enableval" = "no"; then
        user_disabled_ipv6=1
    fi ],
  [ user_disabled_ipv6=0 ] )

Thanks for your consideration,

Nmap gets its value for HAVE_IPV6 from nbase, so it should already work
as you wish. It's possible that there is code referring to IPv6 that is
not protected by HAVE_IPV6 guards, but that would be a separate bug.

I just tried configuring Nmap with
      ./configure --disable-ipv6
and HAVE_IPV6 is disabled in nbase_config.h, as expected.

You are most correct.  Reading the files was not as clear as to how they
interact, actually testing works great. Thanks for your sanity :-)

- -Zero

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRDUYkAAoJEKXdFCfdEflKuZYQAI93tlQ+tamw1gf+2Cl0hvEb
yXTJ4dDXUTJA+nF2tzty4+MsSoIrjeTxj0jK82OMlnjVuUHFawZKeEXOOUyLkRQx
L626I/n/C4+0dOZdg2wk9ITI4qjL8fAGY2iQNj6A4ybjCZuF58sLtbQeZe8Ji1n3
4JLMCQDNp7qkOXWE9X/vw8VEq86JN2TSgSDOSdFSMutdVARMGIx2Vm4le8aDqt0r
vlYfUdruXFhbZRp5Yff/R5Gue33/ebuJELDtaecxkVxOidOqRBzyoYYHOQM6cEVr
zVOhDdBizhgky+NM1Bcv671M1mU9VXN2lTXNmH82GCSqSeejgmd2+BUKsvA/bWyG
nlhOrz+e5nddNPdzNvz30ynlk76zo5m+Y3rNsgh4DiLzZRbL1+F667oYR2ejqJgE
VOLVffltH5Avi8ToqznVayRUBbobplVDyOlHbXSMUzwEBO1x5lEtxaqZpt4ZdL6v
8+63qlnXjIngAC/6ie4bU8nGLMU4QGtI035hCBzaA3lCCef3BislsgApESM7CmIu
jclMo7QGI4NVpYsZrwzCzK5Ld6jvdyvCmWswhrIWFTCF0a72PrTCIeeozC+5T7Ry
9HMqwIh+NWJrnx8bvZ277I+yDD2IhK/2vQ9ppXN7z17W7nKOgbCHLJsOc2qouES5
CuFWIXDH7dTjjLmCfTzb
=Jw5f
-----END PGP SIGNATURE-----
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/


Current thread: