From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Shivani Bhardwaj <shivanib134@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v2] configure: Show support for connlabel
Date: Sat, 12 Mar 2016 12:50:27 +0100 [thread overview]
Message-ID: <20160312115027.GA2262@salvia> (raw)
In-Reply-To: <20160310171028.GA8038@gmail.com>
On Thu, Mar 10, 2016 at 10:40:29PM +0530, Shivani Bhardwaj wrote:
> Add the --disable-connlabel option and the appropriate functionality
> associated with it.
>
> After this patch, iptables configuration shows up as:
>
> Iptables Configuration:
> IPv4 support: yes
> IPv6 support: yes
> Devel support: yes
> IPQ support: no
> Large file support: yes
> BPF utils support: no
> nfsynproxy util support: no
> nftables support: yes
> connlabel support: yes
>
> Signed-off-by: Shivani Bhardwaj <shivanib134@gmail.com>
> ---
> Changes in v2:
> Correct the option to disable-connlabel and add code to make it
> work
>
> configure.ac | 38 +++++++++++++++++++++++++-------------
> 1 file changed, 25 insertions(+), 13 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index 33a8f2d..afc6845 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -63,6 +63,10 @@ AC_ARG_WITH([pkgconfigdir], AS_HELP_STRING([--with-pkgconfigdir=PATH],
> AC_ARG_ENABLE([nftables],
> AS_HELP_STRING([--disable-nftables], [Do not build nftables compat]),
> [enable_nftables="$enableval"], [enable_nftables="yes"])
> +AC_ARG_ENABLE([connlabel],
> + AS_HELP_STRING([--disable-connlabel],
> + [Do not build libnetfilter_conntrack]),
> + [enable_connlabel="$enableval"], [enable_connlabel="yes"])
>
> libiptc_LDFLAGS2="";
> AX_CHECK_LINKER_FLAGS([-Wl,--no-as-needed],
> @@ -93,15 +97,6 @@ if test "$ac_cv_header_linux_ip_vs_h" != "yes"; then
> blacklist_modules="$blacklist_modules ipvs";
> fi;
>
> -PKG_CHECK_MODULES([libnetfilter_conntrack], [libnetfilter_conntrack >= 1.0.4],
> - [nfconntrack=1], [nfconntrack=0])
> -AM_CONDITIONAL([HAVE_LIBNETFILTER_CONNTRACK], [test "$nfconntrack" = 1])
> -
> -if test "$nfconntrack" -ne 1; then
> - blacklist_modules="$blacklist_modules connlabel";
> - echo "WARNING: libnetfilter_conntrack not found, connlabel match will not be built";
> -fi;
> -
> AC_CHECK_SIZEOF([struct ip6_hdr], [], [#include <netinet/ip6.h>])
>
> AM_CONDITIONAL([ENABLE_STATIC], [test "$enable_static" = "yes"])
> @@ -114,15 +109,12 @@ AM_CONDITIONAL([ENABLE_LIBIPQ], [test "$enable_libipq" = "yes"])
> AM_CONDITIONAL([ENABLE_BPFC], [test "$enable_bpfc" = "yes"])
> AM_CONDITIONAL([ENABLE_SYNCONF], [test "$enable_nfsynproxy" = "yes"])
> AM_CONDITIONAL([ENABLE_NFTABLES], [test "$enable_nftables" = "yes"])
> +AM_CONDITIONAL([ENABLE_CONNLABEL], [test "$enable_connlabel" = "yes"])
>
> if test "x$enable_bpfc" = "xyes" || test "x$enable_nfsynproxy" = "xyes"; then
> AC_CHECK_LIB(pcap, pcap_compile,, AC_MSG_ERROR(missing libpcap library required by bpf compiler or nfsynproxy tool))
> fi
>
> -PKG_CHECK_MODULES([libnfnetlink], [libnfnetlink >= 1.0],
> - [nfnetlink=1], [nfnetlink=0])
> -AM_CONDITIONAL([HAVE_LIBNFNETLINK], [test "$nfnetlink" = 1])
> -
> if test "x$enable_nftables" = "xyes"; then
> PKG_CHECK_MODULES([libmnl], [libmnl >= 1.0], [mnl=1], [mnl=0])
>
> @@ -163,6 +155,25 @@ fi
> AM_CONDITIONAL([HAVE_LIBMNL], [test "$mnl" = 1])
> AM_CONDITIONAL([HAVE_LIBNFTNL], [test "$nftables" = 1])
>
> +if test "x$enable_connlabel" = "xyes"; then
> + PKG_CHECK_MODULES([libnetfilter_conntrack],
> + [libnetfilter_conntrack >= 1.0.4],
> + [nfconntrack=1], [nfconntrack=0])
> +
> + if test "$nfconntrack" -ne 1; then
> + blacklist_modules="$blacklist_modules connlabel";
> + echo "WARNING: libnetfilter_conntrack not found, connlabel match will not be built";
> + fi;
> +
> + PKG_CHECK_MODULES([libnfnetlink], [libnfnetlink >= 1.0],
> + [nfnetlink=1], [nfnetlink=0])
IIRC, libnfnetlink is actually required by other extensions, such as
nfnl_osf under utils.
So you should keep back this where it is I think.
prev parent reply other threads:[~2016-03-12 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 17:10 [PATCH v2] configure: Show support for connlabel Shivani Bhardwaj
2016-03-12 11:50 ` Pablo Neira Ayuso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160312115027.GA2262@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=shivanib134@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).