nanog mailing list archives
Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?
From: Bryan Tong <contact () nullivex com>
Date: Fri, 4 Oct 2013 11:35:11 -0600
Working here on Bresnan (charter) root@hq:~# traceroute floksociety.org traceroute to floksociety.org (200.10.150.169), 30 hops max, 60 byte packets 1 * * * 2 cacco002dr9-GE-1-0-0-U0.int.bresnan.net (69.146.239.57) 38.721 ms 39.799 ms 39.899 m s 3 host-72-175-111-198.bln-mt.client.bresnan.net (72.175.111.198) 26.722 ms 27.671 ms 2 7.771 ms 4 chywyaT1cr5-XE-5-2-0-U0.int.bresnan.net (72.175.110.135) 27.791 ms 27.818 ms 27.820 ms 5 seawafh2cr5-XE-5-1-0-U0.int.bresnan.net (72.175.111.166) 67.666 ms 68.616 ms 68.641 ms 6 seawafh1tr5-XE-2-0-0-U0.int.bresnan.net (72.175.110.68) 51.856 ms 61.108 ms 61.768 m s 7 12.90.77.21 (12.90.77.21) 65.384 ms 66.327 ms 66.448 ms 8 cr2.st6wa.ip.att.net (12.123.46.130) 122.440 ms 112.765 ms 111.808 ms 9 cr2.dvmco.ip.att.net (12.122.1.77) 111.733 ms 102.272 ms 98.744 ms 10 cr2.dlstx.ip.att.net (12.122.31.89) 105.493 ms 106.421 ms 105.106 ms 11 dlstx02jt.ip.att.net (12.122.214.249) 104.780 ms 101.914 ms 106.405 ms 12 213.140.53.61 (213.140.53.61) 103.208 ms 192.205.35.250 (192.205.35.250) 100.279 ms 2 13.140.53.61 (213.140.53.61) 121.303 ms 13 Te0-5-0-6-grtmiabr5.red.telefonica-wholesale.net (94.142.125.58) 144.127 ms Xe8-0-2-0- grtmiabr4.red.telefonica-wholesale.net(94.142.119.38) 159.790 ms Xe3-1-2-0-grtmiabr4.red. telefonica-wholesale.net (94.142.126.134) 139.640 ms 14 Te0-2-0-4-grtmiana4.red.telefonica-wholesale.net (94.142.123.5) 138.665 ms Te0-1-0-0-g rtmiana4.red.telefonica-wholesale.net(213.140.37.77) 139.681 ms Xe7-1-6-0-grtmiana2.red.t elefonica-wholesale.net (94.142.125.154) 145.648 ms 15 176.52.249.245 (176.52.249.245) 163.222 ms 176.52.251.201 (176.52.251.201) 143.164 ms 176.52.249.241 (176.52.249.241) 140.896 ms 16 176.52.252.66 (176.52.252.66) 184.038 ms 188.723 ms 181.953 ms 17 * * * 18 * * * 19 * * * 20 host-186-5-116-193.telconet.net (186.5.116.193) 189.490 ms 188.537 ms 188.500 ms 21 host-186-101-89-42.telconet.net (186.101.89.42) 190.366 ms 188.294 ms 192.845 ms 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Traceroute black holes but the site works. Site works on VZW in Colorado. Cheers On Fri, Oct 4, 2013 at 11:22 AM, Christopher Morrow <morrowc.lists () gmail com
wrote:
On Fri, Oct 4, 2013 at 1:15 PM, Gordon Cook <cook () cookreport com> wrote:Hi chris really appreciate the help from ALL you guyssure thing.does what you just said mean that non reachability for version customermay mean a config problem for a small bloc and not something intentional?? that's probably hard to say... I do know that: 5 0.xe-9-2-0.GW9.IAD8.ALTER.NET (152.63.36.30) 6.457 ms 6.821 ms 0.xe-11-2-1.GW9.IAD8.ALTER.NET (152.63.42.2) 5.932 ms 6 telefonica-gw.customer.alter.net (152.179.50.114) 7.182 ms 5.433 ms 5.431 ms 7 Xe4-1-6-0-grtmiana2.red.telefonica-wholesale.net (94.142.123.145) 47.271 ms 48.381 ms Te0-7-0-5-grtmiana4.red.telefonica-wholesale.net (94.142.126.182) 50.290 ms telefonica is a 'customer' not a 'peer' of 701, based on their connectivity. This means that telefonica has to tell 701: "Yo, I need you to accept routes for x, y, z, ktnxbi!' knowing the normal (well, 5yrs ago) config for customers of 701, I don't expect there'd be special handling of this prefix either... so I suspect either no one told 701 to accept this, or telefonica pouched it at the handoff :( If they didn't do that, these routes wouldn't be accepted. If telefonica botched some filter on their side (see the comment about prepending). It's fairly sure though that the prefix isn't 'blackholed'... since it's everything in the /22 not just the local /32 or /24. Bill Herrin's on target as well, it's really hard to say from here :) -chrisOn Oct 4, 2013, at 12:54 PM, Christopher Morrow <morrowc.lists () gmail com>wrote:err.. nothing in the /24 is reachable from 701's perspective (so it seems)... so I'd suspect that there's a routing problem with the /24, in fact the surrounding /24's also seem to be having the same problem. On Fri, Oct 4, 2013 at 12:42 PM, Miles Fidelman <mfidelman () meetinghouse net> wrote:Also inaccessible from FIOS Boston: new-host-2:~ mfidelman$ traceroute floksociety.org traceroute to floksociety.org (200.10.150.169), 64 hops max, 52 bytepackets1 wireless_broadband_router (192.168.1.1) 1.534 ms 0.853 ms 0.724 ms 2 l100.bstnma-vfttp-84.verizon-gni.net (96.252.37.1) 7.619 ms 6.855ms7.304 ms 3 200.10.150.169 (200.10.150.169) 10.482 ms !N *^C But just fine from our datacenter via xo.net. And the web server isup - atleast to a text browser (Lynx). Also via Verizion cell network (Boston area). Some kind of routing table glitch or peering issue, perhaps? William Herrin wrote:On Fri, Oct 4, 2013 at 12:09 PM, Gordon Cook <cook () cookreport com>wrote:traceroute to floksociety.org (200.10.150.169), 64 hops max, 72bytepackets 1 192.168.1.1 (192.168.1.1) 0.759 ms 0.309 ms 0.357 ms 2 l100.cmdnnj-vfttp-26.verizon-gni.net (98.110.50.1) 36.778 ms 17.508 ms 7.316 ms 3 * g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119)6.482 ms!N * 4 * * g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119)7.101ms !N 5 * g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119)9.239 ms!N * 6 g0-3-4-5.cmdnnj-lcr-21.verizon-gni.net (130.81.184.119) 6.823ms!N * 8.846 ms !NInaccessible via FIOS Washington DC too: traceroute -T -p 80 200.10.150.169 traceroute to 200.10.150.169 (200.10.150.169), 30 hops max, 40 byte packets 1 L300.WASHDC-VFTTP-91.verizon-gni.net (173.73.47.1) 1.804 ms 1.595 ms 1.562 ms 2 G0-6-4-7.WASHDC-LCR-22.verizon-gni.net (130.81.216.250) 5.321ms !N* * Correctly accessible via Cox, Qwest, Sprint and others, but the network path is really slow and really long. The border is consistently with telefonica-wholesale.net and then telconet.net. Beyond the border there are badly behaving routers, including ones configured with RFC 1918 addresses. The addressable routers are reachable via Verizon, just not the last hop. traceroute -T -p 80 200.10.150.169 traceroute to 200.10.150.169 (200.10.150.169), 30 hops max, 60 byte packets 1 sark.dirtside.com (70.182.189.216) 0.708 ms 0.689 ms 0.569 ms 2 10.1.192.1 (10.1.192.1) 9.957 ms 9.874 ms 9.725 ms 3 ip68-100-3-49.dc.dc.cox.net (68.100.3.49) 9.631 ms 9.507 ms9.424ms 4 ip68-100-3-113.dc.dc.cox.net (68.100.3.113) 9.310 ms 9.226 ms 9.140 ms 5 mrfddsrj02gex070002.rd.dc.cox.net (68.100.0.145) 9.111 ms 9.019 ms 8.929 ms 6 68.1.4.139 (68.1.4.139) 8.791 ms * 5.981 ms 7 209.48.42.61 (209.48.42.61) 5.748 ms 11.361 ms 10.948 ms 8 vb2000d2.rar3.washington-dc.us.xo.net (207.88.13.66) 58.454 ms 52.415 ms 52.421 ms 9 te-3-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.9) 60.543 ms 60.397 ms 60.378 ms 10 te-3-0-0.rar3.dallas-tx.us.xo.net (207.88.12.2) 58.211 ms58.407ms 58.392 ms 11 * * * 12 206.111.5.226.ptr.us.xo.net (206.111.5.226) 53.378 ms 49.080 ms 47.435 ms 13 Xe-8-1-0-0-grtmiabr3.red.telefonica-wholesale.net (94.142.125.54) 76.006 ms Xe8-0-2-0-grtmiabr4.red.telefonica-wholesale.net (94.142.119.38) 60.181 ms Xe13-1-4-0-grtmiabr4.red.telefonica-wholesale.net (213.140.43.109) 125.888 ms 14 Te-0-2-0-0-grtmiana4.red.telefonica-wholesale.net(94.142.119.233) 67.105 ms Te0-1-0-0-grtmiana4.red.telefonica-wholesale.net (213.140.37.77) 63.435 ms Xe5-1-8-0-grtmiana2.red.telefonica-wholesale.net (213.140.36.89) 141.873 ms 15 Xe9-3-0-0-gramiana4.red.telefonica-wholesale.net (94.142.126.197) 62.450 ms 176.52.249.245 (176.52.249.245) 66.665 ms 176.52.249.241 (176.52.249.241) 64.668 ms 16 176.52.252.66 (176.52.252.66) 118.619 ms 118.057 ms 117.934 ms 17 * * * 18 * * * 19 * * * 20 host-186-5-116-193.telconet.net (186.5.116.193) 122.586 ms 120.967 ms 115.040 ms 21 host-186-101-89-42.telconet.net (186.101.89.42) 122.801 ms 125.164 ms 119.520 ms 22 * * * 23 200.10.150.169 (200.10.150.169) 253.710 ms 246.684 ms 244.845ms-- In theory, there is no difference between theory and practice. In practice, there is. .... Yogi Berra
-- eSited LLC (701) 390-9638
Current thread:
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose?, (continued)
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? William Herrin (Oct 04)
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Gordon Cook (Oct 04)
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Miles Fidelman (Oct 04)
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Miles Fidelman (Oct 04)
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Christopher Morrow (Oct 04)
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Christopher Morrow (Oct 04)
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Gordon Cook (Oct 04)
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Christopher Morrow (Oct 04)
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Bryan Tong (Oct 04)
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Christopher Morrow (Oct 04)
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Joly MacFie (Oct 04)
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Justin M. Streiner (Oct 04)
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- It worked! Huge Thanks Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Gordon Cook (Oct 04)
- Re: verizon trouble ticket NJ DQ04PWR9 -- is verizon blocking FLOKsociety.org by accident or on purpose? Christopher Morrow (Oct 05)