Here is the break down of subnet 39.32.0.0/11 :
http://prntscr.com/djq88m
According to this, geo policy should be apply to 39.45.X.X as well but its
not .
On Thu, Dec 15, 2016 at 5:11 PM, shahzaib mushtaq <shahzaib...@gmail.com>
wrote:
> Hi,
>
> We're using nginx geo module to redirect requests from specific
> subnets/supernets. If request is coming from following ips, it should be
> redirected towards caching node :
>
> geo $qwilt_user {
> default 0;
> 182.184.25.66/32 1;
> 103.28.152.0/22 1;
> 203.135.0.0/18 1;
> 203.99.0.0/16 1;
> 116.71.0.0/16 1;
> 59.103.0.0/16 1;
> 119.152.0.0/13 1;
> *39.32.0.0/11 <http://39.32.0.0/11> 1;*
>
> The critical problem here now is that if request is coming from ip
> 39.45.111.1 its not redirecting but you can clearly see from subnet bit
> above which is /11 , means subnets from 39.32.X.X all the way to 39.63.X.X
> are summed up within subnet 39.32.0.0/11 & supposed to be redirect.
>
> Is this limitation of the geo module that it is not supporting
> supernetting ?
>
> Thanks in advance !!
>
> Shahzaib
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
