February 2009 - Test - lists.nanog.org

New ISP to market, BCP 38, and new tactics
by Steve Bertrand 08 Feb '09

08 Feb '09

Although I've posted to this list before, I don't want to waste your time. This is an ops question, so I'm looking for direction, off-list if necessary. We are a *very* small I-SP, and am just now being put in the position to be a backup transit for a client. Currently, our 'upstream' advertises our route for us, 208.70.104.0/21 from my AS 14270 (SBE96-ARIN). As I've wanted to do this myself for some time, the upstream has had issues allowing me to do so. I've also been advertising 2607:f118::/32 via BGP peering to kind people who have been sensitive to the lack of my 'upstream's' inability to provide me with native access. Now, I am about to force my 'upstream' to allow me to bring my advertisement (v4) back to me, I would like off-list feedback of any/all documentation that I should be aware of regarding filtering. I've proven that my 'upstream' doesn't do pull-up routes, doesn't filter BOGON, and given that they have no clients other than myself that have their own IP space, most likely is not capable of doing anything beyond a simple peering session. I've done much research on RPSL, BCP 38, and other basic filter methods (and from a systems standpoint, I always follow an allow,allow,default-deny approach) , and I am willing to follow all standards and recommended practises to ensure compliance with current Internet standards. Although we are small with minimal resources, I feel that touching this list is my best approach to ensure that when I do begin advertising routes, I conform to the most practical, realistic and best current common standards regarding IPv4 route advertisement and filtering. I hate being a 'rat', so I won't state who does what for AS14270 (on the v4 side of things). I have a 100Mbps fibre link from Cobourg Ontario, to _provider_ in 151 Front Toronto. My 'new' connection (which I control), is a direct link to Hydro One. I am open to bandwidth/connection options regarding this feed to Toronto, if you are commercially inclined, Thanks, Steve

5 9

Re: One /22 Two ISP no BGP
by Charles Regan 07 Feb '09

07 Feb '09

Quick questions. If both ISP publish my /22, what will happen if ISP1 goes down ? Half the internet won't be able to reach me ? I'll have to call them to remove the route manually ? Charles. On Fri, Feb 6, 2009 at 12:54 PM, Charles Regan <charles.regan(a)gmail.com> wrote: > Hmmm, McNamara descendent ? > > On Fri, Feb 6, 2009 at 12:32 PM, Charles Ragan <ciscojock2002(a)yahoo.com> wrote: >> yup... >> >> too funny heh. >> >> Charles Regan wrote: >> >> >From Irish descendent ? >> >> On Fri, Feb 6, 2009 at 12:31 PM, Charles Ragan <ciscojock2002(a)yahoo.com> >> wrote: >> >> >> ha - hey charles...i subscribe to nanog and saw your email come across and >> had to send a note...too funny. Charles Ragan here... >> >> Charles >> >> Charles Regan wrote: >> >> >> I want to advertise my /22 to two different ISP on different POP. >> >> I can't use BGP as ISP1 doesn't support it. >> >> Any suggestions ? >> >> Thanks, >> Charles >> >> >> >> >> >> >> >> >

5 9

Re: [Update] Re: New ISP to market, BCP 38, and new tactics
by Steve Bertrand 06 Feb '09

06 Feb '09

> On 4/02/2009, at 2:43 PM, Steve Bertrand wrote: > >> Nathan Ward wrote: >>> On 4/02/2009, at 2:33 PM, Steve Bertrand wrote: >>> >>>> - Currently, (as I write), I'm migrating my entire core from IPv4 to >>>> IPv6. I've got the space, and I love to learn, so I'm just lab-ing >>>> it up >>>> now to see how things will flow with all iBGP v4 routes being >>>> advertised/routed over v6. >>> >>> >>> Don't advertise v4 prefixes in v6 sessions, keep them separate. This entire discussion went off topic, in regards to bcp and filtering. Off-list, I had someone point out: http://tools.ietf.org/html/draft-kumari-blackhole-urpf-02 ...which is EXACTLY in line with what my end goal was originally, and by reading it, I feel as if I was getting there free-hand. This document helps standardize things a bit, and I will follow it to a certain degree, whether or not it is considered under the standards track, or IANA considers approving the request for the BGP Extended Communities Attribute. What really spooks me after the last week of research, is how easy it would be for a client under my control (or hosts under control of an attacker) to stage/originate an inconspicuous attack (to anywhere), using standard IDS insertion/evasion tactics (even via a tunnel) from hosts within a network bordering my AS. Just by manually viewing logs of ingress traffic, there are just too many holes. We're too small to mitigate a bandwidth-saturating attack inbound, but I can guarantee that I will ensure to the best of my ability that our network won't be part of any form of attack on yours. Thank you everyone, for all of the off, and on-list feedback. Steve

4 3

From San Jose to Google.com - via Europe
by Paul Ferguson 06 Feb '09

06 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was kind of wondering why my connectivity slowed to a crawl a little while ago... Any idea what is up with this? From Comcast in San Jose: %tracert www.google.com Tracing route to www.l.google.com [74.125.39.103] over a maximum of 30 hops: [snip] 5 24 ms 13 ms 9 ms te-9-1-ur06.sanjose.ca.sfba.comcast.net [68.87.1 92.54] 6 11 ms 11 ms * te-0-3-0-4-ar01.oakland.ca.sfba.comcast.net [68. 87.226.229] 7 * 23 ms 13 ms pos-0-2-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.90.141] 8 15 ms 26 ms 17 ms pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net [6 8.86.85.181] 9 18 ms 21 ms 14 ms xe-8-3-0.edge1.sanjose1.level3.net [4.71.118.13] 10 33 ms 13 ms 16 ms vlan89.csw3.sanjose1.level3.net [4.68.18.190] 11 21 ms 18 ms 36 ms ae-84-84.ebr4.sanjose1.level3.net [4.69.134.249] 12 105 ms * * ae-2.ebr4.newyork1.level3.net [4.69.135.186] 13 121 ms 108 ms 111 ms ae-94-94.csw4.newyork1.level3.net [4.69.134.126] 14 126 ms 109 ms 109 ms ae-93-93.ebr3.newyork1.level3.net [4.69.134.109] 15 93 ms 93 ms 102 ms ae-3-3.ebr2.washington1.level3.net [4.69.132.89] 16 190 ms 184 ms 192 ms ae-42-42.ebr2.frankfurt1.level3.net [4.69.137.53 ] 17 184 ms 210 ms 185 ms ae-62-62.csw1.frankfurt1.level3.net [4.69.140.18 ] 18 182 ms 181 ms * ae-1-69.edge3.frankfurt1.level3.net [4.68.23.11] 19 184 ms 195 ms 181 ms 62.67.33.114 20 185 ms 184 ms 184 ms 209.85.254.108 21 198 ms 185 ms 184 ms 209.85.240.134 22 182 ms 192 ms 184 ms 209.85.254.134 23 181 ms 183 ms 181 ms fx-in-f103.google.com [74.125.39.103] Trace complete. 62.67.33.114: inetnum: 62.67.32.0 - 62.67.33.255 netname: FRANKFURT-SERIAL1 descr: DE transfer network1 country: DE admin-c: LTHM tech-c: LTEE status: ASSIGNED PA mnt-by: LEVEL3-MNT source: RIPE # Filtered role: LEVEL3 Hostmaster address: Level (3) Communications address: 100 Leman Street address: London address: E1 8EU - - ferg -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.6.3 (Build 3017) wj8DBQFJjMlLq1pz9mNUZTMRAkRxAJ44p1olXBSJATT3IFf+vkKyAvmOxQCdES0P 9EwfbAHSX0ioHiKE2rLRV2c= =9v8s -----END PGP SIGNATURE----- -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawgster(at)gmail.com ferg's tech blog: http://fergdawg.blogspot.com/

3 4

Re: One /22 Two ISP no BGP
by Leo Bicknell 06 Feb '09

06 Feb '09

From http://en.wikipedia.org/wiki/Smiley The two original text smileys, :-) to indicate a joke and :-( to mark things that are not a joke were invented on September 19, 1982 by Scott E. Fahlman, a research professor at Carnegie Mellon University's Department of Computer Science. His original post at the CMU CS general board, where he suggested the use of the smileys, was retrieved on September 10, 2002 by Jeff Baird from an October 1982 backup tape of the spice vax (cmu-750x) as proof to support the claim.[14] In a message written on Fri, Feb 06, 2009 at 03:36:14PM -0500, Dean Anderson wrote: > I doubt NANOG/BIND Cartel mafia can shame anyone, given its (members and > administrators) shameful and possibly illegal activities. > > --Dean > > > On Fri, 6 Feb 2009, Leo Bicknell wrote: > > > In a message written on Fri, Feb 06, 2009 at 01:14:52PM -0400, Charles Regan wrote: > > > I'll explain. We are a small ISP on a very remote Island. > > > We have a /22 from ARIN. We have a 20mbits pipe from ISP1 and 20mbits from ISP2. > > > > Perhaps you could post the IP addresses on your end of both of these > > links? > > > > I believe then NANOG may be able to shame the appropriate folks into > > doing BGP for you. :) > > > > > > -- > Av8 Internet Prepared to pay a premium for better service? > www.av8.net faster, more reliable, better service > 617 344 9000 > -- Leo Bicknell - bicknell(a)ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/

1 0

Re: One /22 Two ISP no BGP
by Michael Smith 06 Feb '09

06 Feb '09

Ebgp multi-hop is a great idea. Have others seen this done for non-bandwidth customers? ...a 'bgp-only' service...?... ...catalog that right along with v6 and multicast tunnels... ----- Original Message ----- From: Joe Maimon <jmaimon(a)ttec.com> To: Jason Biel <jason(a)biel-tech.com> Cc: nanog(a)nanog.org <nanog(a)nanog.org> Sent: Fri Feb 06 13:13:14 2009 Subject: Re: One /22 Two ISP no BGP Jason Biel wrote: > Charles, > > As I mentioned earlier, you'll want to have one provider announce the /22 > unweighted and the other announce it weighted. Just pick the better of the > two providers as the primary. Don't base it soley off bandwidth, but check > your SLA and any recent outage occurances. > > Traffic will flow in via the primary until that link to you drops, the > provider will remove the route, and traffic will come in the back up route. Perhaps ebgp-multihop with this ISP's upstream provider might offer you an advantage combined with this approach. Probably worth a try. > > > > On Fri, Feb 6, 2009 at 11:14 AM, Charles Regan <charles.regan(a)gmail.com>wrote: > >> I'll explain. We are a small ISP on a very remote Island. >> We have a /22 from ARIN. We have a 20mbits pipe from ISP1 and 20mbits from >> ISP2. >> >> They are the only two we can get bandwidth. >> >> So we are stuck with ISP1 that doesn't support BGP. >> >> On Fri, Feb 6, 2009 at 12:48 PM, Azinger, Marla >> <marla.azinger(a)frontiercorp.com> wrote: >>> im curiouse. you probably had a reason for wanting to do that. So cant >> you find another ISP that will do what you want? >>> Cheers >>> Marla >>> >>> -----Original Message----- >>> From: Charles Regan [mailto:charles.regan@gmail.com] >>> Sent: Friday, February 06, 2009 8:29 AM >>> To: nanog(a)nanog.org >>> Subject: One /22 Two ISP no BGP >>> >>> I want to advertise my /22 to two different ISP on different POP. >>> >>> I can't use BGP as ISP1 doesn't support it. >>> >>> Any suggestions ? >>> >>> Thanks, >>> Charles >>> >>> >> > >

2 1

Weekly Routing Table Report
by Routing Analysis Role Account 06 Feb '09

06 Feb '09

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.apnic.net. If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Routing Table Report 04:00 +10GMT Sat 07 Feb, 2009 Report Website: http://thyme.apnic.net Detailed Analysis: http://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 278566 Prefixes after maximum aggregation: 132796 Deaggregation factor: 2.10 Unique aggregates announced to Internet: 136538 Total ASes present in the Internet Routing Table: 30495 Prefixes per ASN: 9.13 Origin-only ASes present in the Internet Routing Table: 26529 Origin ASes announcing only one prefix: 12914 Transit ASes present in the Internet Routing Table: 3966 Transit-only ASes present in the Internet Routing Table: 97 Average AS path length visible in the Internet Routing Table: 3.6 Max AS path length visible: 29 Max AS path prepend of ASN (12026) 22 Prefixes from unregistered ASNs in the Routing Table: 527 Unregistered ASNs in the Routing Table: 179 Number of 32-bit ASNs allocated by the RIRs: 92 Prefixes from 32-bit ASNs in the Routing Table: 15 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 229 Number of addresses announced to Internet: 1996544544 Equivalent to 119 /8s, 0 /16s and 218 /24s Percentage of available address space announced: 53.9 Percentage of allocated address space announced: 63.0 Percentage of available address space allocated: 85.5 Percentage of address space in use by end-sites: 75.5 Total number of prefixes smaller than registry allocations: 136565 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 64198 Total APNIC prefixes after maximum aggregation: 22979 APNIC Deaggregation factor: 2.79 Prefixes being announced from the APNIC address blocks: 61033 Unique aggregates announced from the APNIC address blocks: 27621 APNIC Region origin ASes present in the Internet Routing Table: 3521 APNIC Prefixes per ASN: 17.33 APNIC Region origin ASes announcing only one prefix: 948 APNIC Region transit ASes present in the Internet Routing Table: 549 Average APNIC Region AS path length visible: 3.5 Max APNIC Region AS path length visible: 19 Number of APNIC addresses announced to Internet: 397493152 Equivalent to 23 /8s, 177 /16s and 67 /24s Percentage of available APNIC address space announced: 79.0 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079 APNIC Address Blocks 58/8, 59/8, 60/8, 61/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 123281 Total ARIN prefixes after maximum aggregation: 65154 ARIN Deaggregation factor: 1.89 Prefixes being announced from the ARIN address blocks: 92814 Unique aggregates announced from the ARIN address blocks: 35503 ARIN Region origin ASes present in the Internet Routing Table: 12756 ARIN Prefixes per ASN: 7.28 ARIN Region origin ASes announcing only one prefix: 4905 ARIN Region transit ASes present in the Internet Routing Table: 1225 Average ARIN Region AS path length visible: 3.3 Max ARIN Region AS path length visible: 24 Number of ARIN addresses announced to Internet: 414233632 Equivalent to 24 /8s, 176 /16s and 180 /24s Percentage of available ARIN address space announced: 79.6 ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 ARIN Address Blocks 24/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 108/8, 173/8, 174/8, 184/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 62962 Total RIPE prefixes after maximum aggregation: 37144 RIPE Deaggregation factor: 1.70 Prefixes being announced from the RIPE address blocks: 57789 Unique aggregates announced from the RIPE address blocks: 38547 RIPE Region origin ASes present in the Internet Routing Table: 12611 RIPE Prefixes per ASN: 4.58 RIPE Region origin ASes announcing only one prefix: 6637 RIPE Region transit ASes present in the Internet Routing Table: 1914 Average RIPE Region AS path length visible: 4.0 Max RIPE Region AS path length visible: 21 Number of RIPE addresses announced to Internet: 387972704 Equivalent to 23 /8s, 31 /16s and 254 /24s Percentage of available RIPE address space announced: 82.6 RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-49151 RIPE Address Blocks 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 178/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 23192 Total LACNIC prefixes after maximum aggregation: 5739 LACNIC Deaggregation factor: 4.04 Prefixes being announced from the LACNIC address blocks: 21390 Unique aggregates announced from the LACNIC address blocks: 11857 LACNIC Region origin ASes present in the Internet Routing Table: 1063 LACNIC Prefixes per ASN: 20.12 LACNIC Region origin ASes announcing only one prefix: 338 LACNIC Region transit ASes present in the Internet Routing Table: 176 Average LACNIC Region AS path length visible: 4.0 Max LACNIC Region AS path length visible: 17 Number of LACNIC addresses announced to Internet: 60553600 Equivalent to 3 /8s, 155 /16s and 249 /24s Percentage of available LACNIC address space announced: 60.2 LACNIC AS Blocks 26592-26623, 27648-28671, plus ERX transfers LACNIC Address Blocks 186/8, 187/8, 189/8, 190/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 4437 Total AfriNIC prefixes after maximum aggregation: 1371 AfriNIC Deaggregation factor: 3.24 Prefixes being announced from the AfriNIC address blocks: 3977 Unique aggregates announced from the AfriNIC address blocks: 1388 AfriNIC Region origin ASes present in the Internet Routing Table: 280 AfriNIC Prefixes per ASN: 14.20 AfriNIC Region origin ASes announcing only one prefix: 86 AfriNIC Region transit ASes present in the Internet Routing Table: 57 Average AfriNIC Region AS path length visible: 4.0 Max AfriNIC Region AS path length visible: 29 Number of AfriNIC addresses announced to Internet: 9909248 Equivalent to 0 /8s, 151 /16s and 52 /24s Percentage of available AfriNIC address space announced: 29.5 AfriNIC AS Blocks 36864-37887 & ERX transfers AfriNIC Address Blocks 41/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4766 1646 6412 378 Korea Telecom (KIX) 17488 1521 110 97 Hathway IP Over Cable Interne 4755 1202 428 180 TATA Communications formerly 9583 1068 107 363 Sify Limited 4134 904 16247 368 CHINANET-BACKBONE 18101 751 198 25 Reliance Infocom Ltd Internet 7545 718 158 96 TPG Internet Pty Ltd 9498 681 297 53 BHARTI BT INTERNET LTD. 24560 664 226 178 Bharti Airtel Ltd. 9829 627 479 15 BSNL National Internet Backbo Complete listing at http://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 6389 4375 3434 344 bellsouth.net, inc. 209 2829 4037 620 Qwest 1785 1787 732 145 PaeTec Communications, Inc. 4323 1640 1080 374 Time Warner Telecom 20115 1593 1423 726 Charter Communications 7018 1445 5878 999 AT&T WorldNet Services 2386 1252 715 893 AT&T Data Communications Serv 6478 1225 295 494 AT&T Worldnet Services 11492 1224 192 12 Cable One 3356 1142 10976 438 Level 3 Communications, LLC Complete listing at http://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8452 1037 188 7 TEDATA 3292 443 1765 388 TDC Tele Danmark 30890 439 88 201 SC Kappa Invexim SRL 12479 396 578 6 Uni2 Autonomous System 3301 338 1669 304 TeliaNet Sweden 3320 337 7064 288 Deutsche Telekom AG 8866 336 109 22 Bulgarian Telecommunication C 3215 333 2898 102 France Telecom Transpac 29049 331 26 3 AzerSat LLC. 8551 312 288 40 Bezeq International Complete listing at http://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 1486 2834 230 UniNet S.A. de C.V. 10620 737 161 94 TVCABLE BOGOTA 11830 687 299 9 Instituto Costarricense de El 22047 619 302 14 VTR PUNTO NET S.A. 7303 508 253 78 Telecom Argentina Stet-France 6471 439 95 42 ENTEL CHILE S.A. 16814 426 27 10 NSS, S.A. 11172 406 118 74 Servicios Alestra S.A de C.V 7738 397 794 28 Telecomunicacoes da Bahia S.A 28573 380 506 23 NET Servicos de Comunicao S.A Complete listing at http://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 613 74 40 LINKdotNET AS number 20858 274 34 3 This AS will be used to conne 3741 268 857 226 The Internet Solution 2018 241 215 141 Tertiary Education Network 33783 150 10 8 EEPAD TISP TELECOM & INTERNET 6713 144 135 11 Itissalat Al-MAGHRIB 29571 128 15 8 Ci Telecom Autonomous system 5536 120 8 17 Internet Egypt Network 33776 118 6 3 Starcomms Nigeria Limited 5713 117 555 66 Telkom SA Ltd Complete listing at http://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 6389 4375 3434 344 bellsouth.net, inc. 209 2829 4037 620 Qwest 1785 1787 732 145 PaeTec Communications, Inc. 4766 1646 6412 378 Korea Telecom (KIX) 4323 1640 1080 374 Time Warner Telecom 20115 1593 1423 726 Charter Communications 17488 1521 110 97 Hathway IP Over Cable Interne 8151 1486 2834 230 UniNet S.A. de C.V. 7018 1445 5878 999 AT&T WorldNet Services 2386 1252 715 893 AT&T Data Communications Serv Complete listing at http://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 209 2829 2209 Qwest 1785 1787 1642 PaeTec Communications, Inc. 17488 1521 1424 Hathway IP Over Cable Interne 4766 1646 1268 Korea Telecom (KIX) 4323 1640 1266 Time Warner Telecom 8151 1486 1256 UniNet S.A. de C.V. 11492 1224 1212 Cable One 18566 1061 1051 Covad Communications 8452 1037 1030 TEDATA 4755 1202 1022 TATA Communications formerly Complete listing at http://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 16927 UNALLOCATED 12.0.252.0/23 7018 AT&T WorldNet Servic 15132 UNALLOCATED 12.9.150.0/24 7018 AT&T WorldNet Servic 32567 UNALLOCATED 12.14.170.0/24 7018 AT&T WorldNet Servic 13746 UNALLOCATED 12.24.56.0/24 7018 AT&T WorldNet Servic 32567 UNALLOCATED 12.25.107.0/24 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.152.0/24 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.154.0/23 7018 AT&T WorldNet Servic 26973 UNALLOCATED 12.39.159.0/24 7018 AT&T WorldNet Servic 32326 UNALLOCATED 12.40.49.0/24 7018 AT&T WorldNet Servic 25639 UNALLOCATED 12.41.169.0/24 7018 AT&T WorldNet Servic Complete listing at http://thyme.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 24.75.116.0/22 10796 ServiceCo LLC - Road Runner 24.75.160.0/19 7843 Adelphia Corp. 24.246.0.0/17 7018 AT&T WorldNet Services 24.246.128.0/18 7018 AT&T WorldNet Services 41.220.16.0/20 8668 TelOne Zimbabwe P/L 41.223.112.0/22 5713 Telkom SA Ltd 41.223.188.0/24 22351 Intelsat 41.223.189.0/24 26452 Local Communications Networks 62.12.96.0/19 15834 MenaNet network Autonomous Sy 62.12.107.0/24 15834 MenaNet network Autonomous Sy Complete listing at http://thyme.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:19 /9:10 /10:20 /11:54 /12:160 /13:309 /14:571 /15:1125 /16:10326 /17:4584 /18:7858 /19:16901 /20:19829 /21:19395 /22:24607 /23:24858 /24:145830 /25:673 /26:808 /27:509 /28:104 /29:8 /30:1 /31:0 /32:7 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6389 2851 4375 bellsouth.net, inc. 209 1569 2829 Qwest 4766 1378 1646 Korea Telecom (KIX) 17488 1302 1521 Hathway IP Over Cable Interne 1785 1208 1787 PaeTec Communications, Inc. 11492 1188 1224 Cable One 18566 1042 1061 Covad Communications 8452 1006 1037 TEDATA 2386 942 1252 AT&T Data Communications Serv 9583 917 1068 Sify Limited Complete listing at http://thyme.apnic.net/current/data/sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 4:13 8:179 12:2193 13:2 15:21 16:3 17:5 20:35 24:1116 32:51 38:539 40:96 41:1734 43:1 44:2 47:11 52:3 55:2 56:3 57:26 58:520 59:608 60:459 61:1101 62:1113 63:2008 64:3414 65:2431 66:3562 67:1468 68:650 69:2462 70:528 71:159 72:1604 73:2 74:1390 75:203 76:296 77:792 78:546 79:319 80:962 81:820 82:552 83:394 84:604 85:1013 86:400 87:621 88:353 89:1364 90:42 91:1936 92:298 93:1105 94:1017 95:292 96:96 97:176 98:192 99:16 110:1 111:1 112:11 113:74 114:163 115:213 116:1160 117:476 118:267 119:628 120:137 121:702 122:927 123:508 124:842 125:1271 128:223 129:222 130:134 131:410 132:71 133:9 134:344 135:35 136:223 137:141 138:145 139:80 140:411 141:105 142:377 143:317 144:319 145:39 146:371 147:146 148:522 149:234 150:141 151:200 152:150 153:132 154:10 155:257 156:171 157:271 158:159 159:239 160:282 161:138 162:274 163:142 164:516 165:505 166:274 167:355 168:672 169:161 170:469 171:40 172:10 173:196 174:55 186:6 187:60 189:326 190:2534 192:5798 193:4184 194:3332 195:2683 196:1070 198:3683 199:3284 200:5535 201:1485 202:7815 203:7968 204:3926 205:2144 206:2354 207:2794 208:3819 209:3482 210:2607 211:1122 212:1513 213:1704 214:68 215:30 216:4575 217:1196 218:371 219:407 220:1209 221:449 222:296 End of report

1 0

Re: One /22 Two ISP no BGP
by Michael Smith 06 Feb '09

06 Feb '09

...small isp on a very remote island... Sounds like a nice problem to have... :) ----- Original Message ----- From: Charles Regan <charles.regan(a)gmail.com> To: nanog(a)nanog.org <nanog(a)nanog.org> Sent: Fri Feb 06 12:14:52 2009 Subject: Re: One /22 Two ISP no BGP I'll explain. We are a small ISP on a very remote Island. We have a /22 from ARIN. We have a 20mbits pipe from ISP1 and 20mbits from ISP2. They are the only two we can get bandwidth. So we are stuck with ISP1 that doesn't support BGP. On Fri, Feb 6, 2009 at 12:48 PM, Azinger, Marla <marla.azinger(a)frontiercorp.com> wrote: > im curiouse. you probably had a reason for wanting to do that. So cant you find another ISP that will do what you want? > > Cheers > Marla > > -----Original Message----- > From: Charles Regan [mailto:charles.regan@gmail.com] > Sent: Friday, February 06, 2009 8:29 AM > To: nanog(a)nanog.org > Subject: One /22 Two ISP no BGP > > I want to advertise my /22 to two different ISP on different POP. > > I can't use BGP as ISP1 doesn't support it. > > Any suggestions ? > > Thanks, > Charles > >

1 0

Re: One /22 Two ISP no BGP
by Michael Smith 06 Feb '09

06 Feb '09

That is a possible scenario. If they are willing to tie the static route to their interface toward your net, that static route would be dynamically removed. Also, technologies like cisco's ip-sla would get you part of the way there. If they won't run bgp with you, one of the static route options is probably your only reasonable hope. All of the above are inferior to bgp. The best advice that I've heard thusfar is to deal with this the best way possible, and then start shopping. ----- Original Message ----- From: Charles Regan <charles.regan(a)gmail.com> To: nanog(a)nanog.org <nanog(a)nanog.org> Sent: Fri Feb 06 12:08:53 2009 Subject: Re: One /22 Two ISP no BGP Quick questions. If both ISP publish my /22, what will happen if ISP1 goes down ? Half the internet won't be able to reach me ? I'll have to call them to remove the route manually ? Charles. On Fri, Feb 6, 2009 at 12:54 PM, Charles Regan <charles.regan(a)gmail.com> wrote: > Hmmm, McNamara descendent ? > > On Fri, Feb 6, 2009 at 12:32 PM, Charles Ragan <ciscojock2002(a)yahoo.com> wrote: >> yup... >> >> too funny heh. >> >> Charles Regan wrote: >> >> >From Irish descendent ? >> >> On Fri, Feb 6, 2009 at 12:31 PM, Charles Ragan <ciscojock2002(a)yahoo.com> >> wrote: >> >> >> ha - hey charles...i subscribe to nanog and saw your email come across and >> had to send a note...too funny. Charles Ragan here... >> >> Charles >> >> Charles Regan wrote: >> >> >> I want to advertise my /22 to two different ISP on different POP. >> >> I can't use BGP as ISP1 doesn't support it. >> >> Any suggestions ? >> >> Thanks, >> Charles >> >> >> >> >> >> >> >> >

1 0

Re: One /22 Two ISP no BGP
by Michael Smith 06 Feb '09

06 Feb '09

How did you get a /22, and what isp won't run bgp with you? ----- Original Message ----- From: Charles Regan <charles.regan(a)gmail.com> To: nanog(a)nanog.org <nanog(a)nanog.org> Sent: Fri Feb 06 11:29:28 2009 Subject: One /22 Two ISP no BGP I want to advertise my /22 to two different ISP on different POP. I can't use BGP as ISP1 doesn't support it. Any suggestions ? Thanks, Charles

4 3