[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20110905174847.GB32733@1984>
Date: Mon, 5 Sep 2011 19:48:47 +0200
From: Pablo Neira Ayuso <pablo@...filter.org>
To: "Anthony G. Basile" <basile@...nsource.dyc.edu>
Cc: davem@...emloft.net, kaber@...sh.net, blueness@...too.org,
gurligebis@...too.org, base-system@...too.org, kernel@...too.org,
toolchain@...too.org, mchehab@...hat.com, hverkuil@...all.nl,
laurent.pinchart@...asonboard.com, arnd@...db.de,
eparis@...hat.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, netfilter-devel@...r.kernel.org,
netfilter@...r.kernel.org, coreteam@...filter.org
Subject: Re: [PATCH] netfilter: install nf_nat.h and related headers to
INSTALL_HDR_PATH
On Sat, Sep 03, 2011 at 02:49:44PM -0400, Anthony G. Basile wrote:
> Currently nf_nat.h, nf_conntrack_tuple.h and related headers under
> include/net/netfilter are not installed as part of the public kernel
> headers. However, there are userland applications, other than iptables
> which ships with its own headers, which need these to make use of NAT in
> the kernel's netfilter API. For example, miniupnpd, requires them and is
> forced to search /usr/src/linux when building.
Could anyone clarify why miniupnpd (or any other application) require
this?
Those headers contain structure layouts that may change along time
without further notice, thus breaking backward compatibility.
and BTW, no need to cross-post this message to such a huge list of CC.
I guess you could simply use netfilter-devel for this.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists