83.222.0.0/19 Unroutable on Verizon

2009-09-03 Thread Peter Beckman 

I can't reach 83.222.0.0/19 from Verizon, but I can via Cox Communications
Business Fiber as well as Level3.  Dies at a peering point it seems:

HOST: homeLoss%   Snt   Last   Avg  Best  Wrst StDev
  1. mph   0.0%200.7   0.6   0.5   0.7   0.1
  2. 10.1.41.890.0%202.3   3.6   1.7  26.4   5.6
  3. G2-0-3-891.WASHDC-LCR-08.ver  0.0%202.1   1.9   1.6   2.2   0.2
  4. so-1-1-0-0.RES-BB-RTR2.veriz  0.0%202.3   2.4   2.2   2.8   0.1
  5. 0.so-6-1-0.XL4.IAD8.ALTER.NE  0.0%202.8   2.8   2.6   3.0   0.1
  6. 0.xe-8-1-0.BR1.IAD8.ALTER.NE  0.0%205.1   8.4   3.0  40.3   9.4
  7. 64.212.107.1570.0%20  203.2  14.0   3.0 203.2  44.6
  8. ???  100.0200.0   0.0   0.0   0.0   0.0

Hop 7 alternates between 64.212.107.157 (GBLX) and 204.255.169.202 (MCI dba
Verizon) and dies after that. 83.222.32.0/19 seems to route correctly.

Can anyone else confirm?  Bad BGP Announcement?

Beckman
---
Peter Beckman  Internet Guy
beck...@angryox.com http://www.angryox.com/
---

Re: 83.222.0.0/19 Unroutable on Verizon

2009-09-03 Thread Christopher Morrow 
On Thu, Sep 3, 2009 at 5:20 PM, Peter Beckmanbeck...@angryox.com wrote:
 I can't reach 83.222.0.0/19 from Verizon, but I can via Cox Communications
 Business Fiber as well as Level3.  Dies at a peering point it seems:

 HOST: home                        Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. mph                           0.0%    20    0.7   0.6   0.5   0.7   0.1
  2. 10.1.41.89                    0.0%    20    2.3   3.6   1.7  26.4   5.6
  3. G2-0-3-891.WASHDC-LCR-08.ver  0.0%    20    2.1   1.9   1.6   2.2   0.2
  4. so-1-1-0-0.RES-BB-RTR2.veriz  0.0%    20    2.3   2.4   2.2   2.8   0.1
  5. 0.so-6-1-0.XL4.IAD8.ALTER.NE  0.0%    20    2.8   2.8   2.6   3.0   0.1
  6. 0.xe-8-1-0.BR1.IAD8.ALTER.NE  0.0%    20    5.1   8.4   3.0  40.3   9.4
  7. 64.212.107.157                0.0%    20  203.2  14.0   3.0 203.2  44.6
  8. ???                          100.0    20    0.0   0.0   0.0   0.0   0.0

it's actually being handed off to the next provider... so, maybe this
thread is mis-named? this looks like GBLX route filtering or traffic
filtering. From twtelecom I see this die inside 'retn.net' 111ms from
ashburn-ish. (so, in emea somewhere)

-chris


 Hop 7 alternates between 64.212.107.157 (GBLX) and 204.255.169.202 (MCI dba
 Verizon) and dies after that. 83.222.32.0/19 seems to route correctly.

 Can anyone else confirm?  Bad BGP Announcement?

 Beckman
 ---
 Peter Beckman                                                  Internet Guy
 beck...@angryox.com                                 http://www.angryox.com/
 ---

Re: 83.222.0.0/19 Unroutable on Verizon

2009-09-03 Thread Cord MacLeod 


On Sep 3, 2009, at 2:20 PM, Peter Beckman wrote:

I can't reach 83.222.0.0/19 from Verizon, but I can via Cox  
Communications

Business Fiber as well as Level3.  Dies at a peering point it seems:


route-views.oregon-ix.netsh ip bgp 83.222.0.0
BGP routing table entry for 83.222.0.0/19, version 14706715
Paths: (34 available, best #6, table Default-IP-Routing-Table)
  Not advertised to any peer
  1221 4637 3549 9002 25532
203.62.252.186 from 203.62.252.186 (203.62.252.186)
  Origin IGP, localpref 100, valid, external
  3549 9002 25532
208.51.134.254 from 208.51.134.254 (208.178.61.33)
  Origin IGP, metric 14088, localpref 100, valid, external
  3561 9002 25532
206.24.210.102 from 206.24.210.102 (206.24.210.102)
  Origin IGP, localpref 100, valid, external
  16150 9002 25532
217.75.96.60 from 217.75.96.60 (217.75.96.60)
  Origin IGP, metric 0, localpref 100, valid, external
  Community: 16150:63392 16150:65215 16150:65320
  3277 3267 25532
194.85.4.55 from 194.85.4.55 (194.85.4.16)
  Origin IGP, localpref 100, valid, external
  Community: 3277:3267 3277:65100 3277:65320 3277:65326
  3267 25532
194.85.40.15 from 194.85.40.15 (193.232.80.7)
  Origin IGP, localpref 100, valid, external, best
  2914 9002 25532
129.250.0.171 from 129.250.0.171 (129.250.0.79)
  Origin IGP, metric 308, localpref 100, valid, external
  Community: 2914:410 2914:2202 2914:3200
  3582 4600 11537 9002 25532
128.223.253.8 from 128.223.253.8 (128.223.253.8)
  Origin IGP, localpref 100, valid, external
  Community: 3582:567 4600:199
  6079 9002 25532
207.172.6.1 from 207.172.6.1 (207.172.6.1)
  Origin IGP, metric 0, localpref 100, valid, external
  2828 3561 9002 25532
65.106.7.139 from 65.106.7.139 (66.239.189.139)
  Origin IGP, metric 3, localpref 100, valid, external
  2905 702 9002 25532
196.7.106.245 from 196.7.106.245 (196.7.106.245)
  Origin IGP, metric 0, localpref 100, valid, external
   9002 25532
193.0.0.56 from 193.0.0.56 (193.0.0.56)
  Origin IGP, localpref 100, valid, external
  701 3549 9002 25532
157.130.10.233 from 157.130.10.233 (137.39.3.60)
  ^^^


  Origin IGP, localpref 100, valid, external
  812 174 3561 9002 25532
64.71.255.61 from 64.71.255.61 (64.71.255.61)
  Origin IGP, localpref 100, valid, external
  7660 2516 3549 9002 25532
203.181.248.168 from 203.181.248.168 (203.181.248.168)
  Origin IGP, localpref 100, valid, external
  Community: 2516:1030
  3257 3549 9002 25532
89.149.178.10 from 89.149.178.10 (213.200.87.91)
  Origin IGP, metric 10, localpref 100, valid, external
  Community: 3257:8012 3257:30070 3257:50001 3257:54900 3257:54901
  6079 9002 25532
207.172.6.20 from 207.172.6.20 (207.172.6.20)
  Origin IGP, metric 117, localpref 100, valid, external
  6453 3549 9002 25532
207.45.223.244 from 207.45.223.244 (66.110.0.124)
  Origin IGP, localpref 100, valid, external
  6453 3549 9002 25532
195.219.96.239 from 195.219.96.239 (195.219.96.239)
  Origin IGP, localpref 100, valid, external
  852 174 3549 9002 25532
154.11.11.113 from 154.11.11.113 (154.11.11.113)
  Origin IGP, metric 0, localpref 100, valid, external
  Community: 852:180
  1668 3561 9002 25532
66.185.128.48 from 66.185.128.48 (66.185.128.50)
  Origin IGP, metric 511, localpref 100, valid, external
  4826 9002 25532
114.31.199.1 from 114.31.199.1 (114.31.199.1)
  Origin IGP, localpref 100, valid, external
  852 174 3549 9002 25532
154.11.98.225 from 154.11.98.225 (154.11.98.225)
  Origin IGP, metric 0, localpref 100, valid, external
  Community: 852:180
  8075 9002 25532
207.46.32.34 from 207.46.32.34 (207.46.32.34)
  Origin IGP, localpref 100, valid, external
  2914 9002 25532
129.250.0.11 from 129.250.0.11 (129.250.0.51)
  Origin IGP, metric 393, localpref 100, valid, external
  Community: 2914:410 2914:2202 2914:3200
  2497 9002 25532
202.232.0.2 from 202.232.0.2 (202.232.0.2)
  Origin IGP, localpref 100, valid, external
  7018 3561 9002 25532
12.0.1.63 from 12.0.1.63 (12.0.1.63)
  Origin IGP, localpref 100, valid, external
  Community: 7018:5000
  3356 9002 25532
4.69.184.193 from 4.69.184.193 (4.68.3.50)
  Origin IGP, metric 0, localpref 100, valid, external
  Community: 3356:2 3356:22 3356:100 3356:123 3356:507 3356:2076  
65000:0

  286 3549 9002 25532
134.222.87.1 from 134.222.87.1 (134.222.86.1)
  Origin IGP, localpref 100, valid, external
  Community: 286:18 286:19 286:28 286:29 286:800 286:888 286:3049  
286:4017 3549:350 3549:4811 3549:31752

  6539 9002 25532
66.59.190.221 from 66.59.190.221 (66.59.190.221)
  Origin IGP, localpref 100, valid, external
  3303 9002 25532
164.128.32.11 from 164.128.32.11 (164.128.32.11)
  Origin IGP, localpref 100, valid, external
  Community: 3303:1004 3303:1006 3303:3054
  7500 2497 9002 25532

Re: 83.222.0.0/19 Unroutable on Verizon

2009-09-03 Thread Joe Provo 

[comment: subject is irksome - Unroutable? That is meaningless]

On Thu, Sep 03, 2009 at 05:20:23PM -0400, Peter Beckman wrote:
 I can't reach 83.222.0.0/19 from Verizon, but I can via Cox Communications
 Business Fiber as well as Level3.  Dies at a peering point it seems:
 
 HOST: homeLoss%   Snt   Last   Avg  Best  Wrst StDev
   1. mph   0.0%200.7   0.6   0.5   0.7   0.1
[snip]

Presumably ICMP probes - those are frequently rate-limited as
counter-measures you realize?  And which Verizon? 701 clearly shows it
in its tables and packets go there. Since your mtr or whatever shows the
traffic reaching a GBLX address, so you likely want to reach out to them.

 Can anyone else confirm?  Bad BGP Announcement?

What does your table say? How does that compare to data in RIS, route-views,
etc?  Independent investigation with table data -if your concern is the
state of someone's routing- would help.

Cheers,

Joe

-- 
 RSUC / GweepNet / Spunk / FnB / Usenix / SAGE