[148111] in North American Network Operators' Group
Re: Problems with 100.42.32.0/20
daemon@ATHENA.MIT.EDU (Josh Baird)
Tue Jan 3 14:06:01 2012
In-Reply-To: <CABmW_PfVNXF3_vz8ussaXwvQK37Z+PPP_sXYvtx4U8SPrx+cEA@mail.gmail.com>
Date: Tue, 3 Jan 2012 14:04:59 -0500
From: Josh Baird <joshbaird@gmail.com>
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Verizon just contacted me off-list. The problem was identified as an
outdated bogon filter on their end.
Verizon - thanks for the quick response!
Thanks,
Josh
On Tue, Jan 3, 2012 at 12:42 PM, Josh Baird <joshbaird@gmail.com> wrote:
> Hi,
>
> We just received 100.42.32.0/20 from ARIN. =A0According to ARIN, this
> block was received from IANA in November 2010 and was issued to us in
> November 2011. =A0Since we started using it, we have seen many problems
> with different Geo-IP providers incorrectly classifying the block -
> both location and provider wise (lots of them think this is Verizon
> space for some reason in both Canada and Kansas). =A0I have followed
> http://nanog.cluepon.net/index.php/GeoIP and contacted most of these
> providers already. =A0Not one has returned my email/inquiry.
>
> The main problem that I am seeing is that Verizon/UUNET is filtering
> access to some of their networks from 100.42.32.0/20. =A0We are
> currently unable to reach any of UUNET.net's authoritative DNS servers
> (198.6.1.83, 198.6.1.161, etc) and appear to be filtered by some
> Verizon Business/UUNET routers.
>
> $ traceroute 198.6.1.83
> traceroute to 198.6.1.83 (198.6.1.83), 30 hops max, 40 byte packets
> 1 =A0209.65.192.129 (209.65.192.129) =A01.491 ms =A01.716 ms =A01.942 ms
> 2 =A0vl41-irtr1.dan100.net.kywimax.com (209.65.192.45) =A00.551 ms =A00.5=
82
> ms =A00.587 ms
> 3 =A0rrcs-173-197-155-189.west.biz.rr.com (173.197.155.189) =A00.474 ms
> 0.519 ms =A00.505 ms
> 4 =A0ae8.chcgill3-rtr1.kc.rr.com (65.28.199.197) =A020.349 ms =A020.340 m=
s =A020.409 ms
> 5 =A0ae-5-1.cr0.chi30.tbone.rr.com (66.109.6.112) =A020.243 ms =A020.235 =
ms =A020.223 ms
> 6 =A0107.14.17.147 (107.14.17.147) =A027.982 ms =A027.567 ms =A027.540 ms
> 7 =A0216.156.72.165.ptr.us.xo.net (216.156.72.165) =A020.945 ms
> te1-2-0d0.cir1.chicago2-il.us.xo.net (216.156.72.5) =A020.920 ms
> 216.156.72.157.ptr.us.xo.net (216.156.72.157) =A020.912 ms
> 8 =A0 (204.255.168.97) =A020.868 ms =A020.826 ms =A020.910 ms
> 9 =A0 (152.63.66.77) =A036.133 ms =A036.243 ms =A036.233 ms
> 10 =A0 (152.63.43.109) =A045.859 ms =A045.853 ms =A045.843 ms
> 11 =A0 (152.63.38.9) =A045.177 ms =A045.175 ms =A045.168 ms
> 12 =A0* * *
> 13 =A0* * *
> 14 =A0* =A0(207.18.173.162) =A046.105 ms !X *
>
> (pos5-0.soesr1.ash.ops.us.uu.net)
>
> I have contacted VZW Business' IP-NOC and was not really given a
> contact that could help me with this situation. =A0I have also emailed
> filters@lists.verizonbusiness.com and I'm awaiting a response
> (hopefully).
>
> Would anyone happen to have an idea of why I am seeing so many
> problems with this block, and who I may be able to reach out to at VZB
> to hopefully get this issue resolved?
>
> Thanks.
