<div dir="ltr">Hi,<input name="virtru-metadata" type="hidden" value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"expires":false,"isManaged":false},"attachments":{}}"><div><br>Sorry guys it was my bad. We have policy to only redirect HTTPS requests, though the request coming from this ip was with HTTP hence no map policy on it.</div><div><br></div><div>In short, things are working as expected :)<br><br>Shahzaib</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 15, 2016 at 5:35 PM, shahzaib mushtaq <span dir="ltr"><<a href="mailto:shahzaib.cb@gmail.com" target="_blank">shahzaib.cb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Here is the break down of subnet <a href="http://39.32.0.0/11" target="_blank">39.32.0.0/11</a> :<br><br><a href="http://prntscr.com/djq88m" target="_blank">http://prntscr.com/djq88m</a><br><br>According to this, geo policy should be apply to 39.45.X.X as well but its not .<input name="virtru-metadata" type="hidden" value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"expires":false,"isManaged":false},"attachments":{}}"></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 15, 2016 at 5:11 PM, shahzaib mushtaq <span dir="ltr"><<a href="mailto:shahzaib.cb@gmail.com" target="_blank">shahzaib.cb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<input name="virtru-metadata" type="hidden" value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"expires":false,"isManaged":false},"attachments":{}}"><div><br>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 :<br><br><div>geo $qwilt_user {</div><div>  default 0;</div><div>  <a href="http://182.184.25.66/32" target="_blank">182.184.25.66/32</a> 1;</div><div>  <a href="http://103.28.152.0/22" target="_blank">103.28.152.0/22</a> 1;</div><div>  <a href="http://203.135.0.0/18" target="_blank">203.135.0.0/18</a> 1;</div><div>  <a href="http://203.99.0.0/16" target="_blank">203.99.0.0/16</a> 1;</div><div>  <a href="http://116.71.0.0/16" target="_blank">116.71.0.0/16</a> 1;</div><div>  <a href="http://59.103.0.0/16" target="_blank">59.103.0.0/16</a> 1;</div><div>  <a href="http://119.152.0.0/13" target="_blank">119.152.0.0/13</a> 1;</div><div>  <b><a href="http://39.32.0.0/11" target="_blank">39.32.0.0/11</a> 1;</b><br></div></div><div><br></div><div>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 <a href="http://39.32.0.0/11" target="_blank">39.32.0.0/11</a> & supposed to be redirect.</div><div><br></div><div>Is this limitation of the geo module that it is not supporting supernetting ?</div><div><br></div><div>Thanks in advance !!</div><span class="m_-190008336956824166HOEnZb"><font color="#888888"><div><br>Shahzaib</div></font></span></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>