Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: Build with GEOIP

117 views
Skip to first unread message

Pushkar Pradhan

unread,
Mar 25, 2016, 11:21:39 AM3/25/16
to Olsen, Richard William (Rick) CTR (US), bind-...@lists.isc.org
Sounds to me like it is looking for the header file which is in bin/named/include/named.
Can you try setting up your GeoIP so that everything is under the same directory?
 
pushkar


On Friday, March 25, 2016 7:00 AM, "Olsen, Richard William (Rick) CTR (US)" <richard.w...@mail.mil> wrote:


I'm trying to configure the GEOIP option in to our bind build. I have the free
GeoIP databases for initial testing. Can anyone point me to a walkthrough or
give me the required steps. I've read the stuff I can find on ISC and it talks
about using the --with-geoip config option and states:

"BIND 9.10's GeoIP features work by allowing you to create ACL elements that
evaluate based on the location information for the client's IP address.  This
uses the API provided by MaxMindR to query their GeoIP database but should
work with any database in a compatible format."

This makes it sound to me like the API for maxmind is built in to the bind
code. What I get when trying to build out the bind "--with-geoip"

Configure: error: GeoIP path not found


so I tried to use " --with-geoip=/var/named/GeoIP"

Path does not exist



Used "--with-geoip=/var/named/chroot/var/named/GeoIP" (created the directory
and put the databases here.)
Now I get

checking GeoIP.h usability... no
checking GeoIP.h presence... no
checking forGeoIP.h... no
configure: error GeoIP header file not found

the build directory for this release has geoip.h in bin/named/include/named

I'm obviously missing some things.



_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-...@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Evan Hunt

unread,
Mar 25, 2016, 12:17:28 PM3/25/16
to Olsen, Richard William (Rick) CTR (US), bind-...@lists.isc.org
On Fri, Mar 25, 2016 at 01:58:51PM +0000, Olsen, Richard William (Rick) CTR (US) wrote:
> "BIND 9.10's GeoIP features work by allowing you to create ACL elements that
> evaluate based on the location information for the client's IP address. This
> uses the API provided by MaxMindR to query their GeoIP database but should
> work with any database in a compatible format."
>
> This makes it sound to me like the API for maxmind is built in to the bind
> code. What I get when trying to build out the bind "--with-geoip"
>
> Configure: error: GeoIP path not found
>
>
> so I tried to use " --with-geoip=/var/named/GeoIP"

It needs the path to the libGeoIP library. On my system that's in
/usr/lib, so --with-geoip=/usr would work. The configure script knows a
handful of directories to check automatically, though, and /usr is one of
them, so I just use "configure --with-geoip" and that works fine.

You may not have the library installed. There's probably a package
for your OS, or the source is at https://github.com/maxmind/geoip-api-c.

> the build directory for this release has geoip.h in bin/named/include/named

That file is part of BIND. Look for GeoIP.h, with the capital letters.

--
Evan Hunt -- ea...@isc.org
Internet Systems Consortium, Inc.

PGNd

unread,
Mar 25, 2016, 1:13:04 PM3/25/16
to bind-...@lists.isc.org


On Fri, Mar 25, 2016, at 09:50 AM, Olsen, Richard William (Rick) CTR (US) wrote:
> Thanks to those who have responded with helpful replies. I understand now
> that the bind build does not have the api actually built in and that I have
> to install one.

just fyi, note that, even with

--with-geoip=<path>

bind sources only set rpath for OS == <netbsd*|openbsd*|solaris*>

For linux, if you want compile-time & run-time usage of non-system-path GeoIP, you'll need to manage your rpath with $LDFLAGS & $LIBS.

I'm not clear why
(a) rpath is not set for linux, if only as an option,
and
(b) why geoip's pkg-config data is not used. adding path-to geoip.pc could be useful.

0 new messages