Hi. On Friday 13 of April 2012 14:47:24 Maxim Dounin wrote: > We'll work on various ipv6-related things after 1.2.0 release (it > was expected to happen yesterday, but was postponed to avoid > interference with security updates; next expected date is about 23 > april). It will likely be committed then. Nice to hear that. Best regards, Gregor Kališnik_______________________________by MasterMind2k - Nginx Mailing List - English
Hi. On Wednesday 05 of October 2011 13:26:47 csg wrote: > Most IPv6 stuff was introduced with newer versions of the GeoIP library > (IIRC something around 1.4.7), so you might either want to autodetect > GeoIP's capabilities or embed the relevant stuff into > > #if LIBGEOIP_VERSION >= 1004007 > ... > #endif > > directives. Otherwise you might break builds against oby MasterMind2k - Nginx Mailing List - English
Hi. On Wednesday 22 of June 2011 01:45:45 you wrote: > Hello! > > On Tue, Jun 21, 2011 at 11:12:08PM +0200, Gregor KaliÅ¡nik wrote: > > [...] > > > Oops, sorry, looks like I forgot to actually attach it. Let me try > again. :) > > Maxim Dounin Got it. Best regards, Gregor Kališnik_______________________________________________ nginx-devel mailing list nby MasterMind2k - Nginx Development
Hi. On Tuesday 21 of June 2011 20:52:51 you wrote: > Hello! > > Ah, ok, I see now. IPv6 support appeared in libgeoip 1.4.5, but > it was rather limited. So the test for (at least one) constant > appeared in 1.4.7 is indeed required. I believe GEOIP_CITY_EDITION_REV0_V6 constant would be sufficient (random pick :) ). > > Please include attached patch for configure partby MasterMind2k - Nginx Development
Hi. On Wednesday 15 of June 2011 03:47:18 you wrote: > Hello! > > On Tue, Jun 14, 2011 at 07:52:10AM +0200, Gregor Kališnik wrote: > > Hi. > > > > I believe it would be sufficient to just check for geoipv6_t type. > > ngx_feature_incs="#include <GeoIP.h>" > ... > ngx_feature_test="geoipv6_t v6addr; >by MasterMind2k - Nginx Development
Hi. On Tuesday 14 of June 2011 05:38:59 you wrote: > Hello! > > On Sat, Jun 11, 2011 at 08:19:52PM +0200, Gregor Kališnik wrote: > > Hi. > You can't assume you have sockaddr_in6 unless compiled with ipv6. If IPv6 is not compiled, then GeoIPv6 also won't be compiled. > This should go to auto/lib/geoip/conf. And probably should be > made shorter. > > Naming thisby MasterMind2k - Nginx Development
Hi. On Saturday 11 of June 2011 16:54:18 you wrote: > Unrelated whitespace breakage. There are multiple other style > issues, too. There souldn't be any now in this patch. > I don't really like this aproach. Result looks to cluttered with > #if's and hard to read. Probably it's good idea to try to produce > something better. Put one #if .. #endif block at the begining. Not sby MasterMind2k - Nginx Development
Hi. Sending patch with snprintf. Also note that this patch needs geoip-1.4.7 (if nginx is compiled with ipv6 support). Best regards. On Saturday 11 of June 2011 13:10:24 you wrote: > 2011/6/11 Gregor Kališnik <gregor@unimatrix-one.org>: > > Hi. > > Hi Gregor, > > > I've created a patch for nginx GeoIP module to also use the GeoIP IPv6 > > version. The paby MasterMind2k - Nginx Development
Hi. I've created a patch for nginx GeoIP module to also use the GeoIP IPv6 version. The patch is attached. Currently it runs on http://www.podnapisi.net and there are no appearant problems. Best regards, Gregor Kališnik_______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://nginx.org/mailman/listinfo/nginx-develby MasterMind2k - Nginx Development
Hi. I've written a patch that uses GeoIP IPv6 database. I've made some quick tests (connect with my external IPv4 and my public IPv6) and it seems this patch works. Usage is simple. If you specify the IPv6 database, it will use it for IPv6 and IPv4 addresses (same variables). If you specify the IPv4 database, it will be used only for IPv4. This patch is based on Nginx 1.0.4. Best reby MasterMind2k - Ideas and Feature Requests