- Test - lists.nanog.org

Re: Operational Issues with 69.0.0.0/8...
by Todd A. Blank 06 Dec '02

06 Dec '02

The list of inaccessible sites continues to grow: Add to the list www.oandp.com - that looks like someone's firewall filtering in front of their DNS server, because we can't even resolve the DNS. We still can't get to www.ocas.com, www.lavalife.com, and www.indofilms.com even after calling and posting repeatedly. There are undoubtedly others out there. Repeated problems posted by myself and others show the extent of the problem with the 69.0.0.0/8 CIDR, and its lack of dependability - it's a human thing. It used to be restricted, so there are a lot of access lists out there - with all the stuff going on in the last year or so, half the people blocking it probably don't even know how to unblock it - i.e. that person no longer works here... If you look at the address space on IANA, http://www.iana.org/assignments/ipv4-address-space you will see that the last CIDR ARIN took before 69/8 was over a year prior to the 69/8 assignment. A lot happened in our industry in that year. Somewhere, this process is broken since the last CIDR was assigned to ARIN. My question is as follows - We are losing customers because of this problem. It is costing us reputation and money. It is out of our control. If you were us, what would you do? We have already asked ARIN to reassign us to a "friendlier" CIDR, and they refuse. Suggestions are welcome. Sincerely, Todd A. Blank CTO IPOutlet LLC 614.207.5853

1 0

The Cidr Report
by cidr-report＠potaroo.net 06 Dec '02

06 Dec '02

This report has been generated at Fri Dec 6 21:44:40 2002 AEST. The report analyses the BGP Routing Table of an AS4637 (Reach) router and generates a report on aggregation potential within the table. Check http://www.cidr-report.org/as4637 for a current version of this report. Recent Table History Date Prefixes CIDR Agg 29-11-02 117628 84925 30-11-02 117500 84864 01-12-02 117450 84897 02-12-02 117617 84818 03-12-02 117623 84175 04-12-02 116419 84197 05-12-02 116693 84459 06-12-02 116870 84561 AS Summary 14128 Number of ASes in routing system 5562 Number of ASes announcing only one prefix 1716 Largest number of prefixes announced by an AS AS3908 : SUPERNETASBLK SuperNet, Inc. 72949248 Largest address span announced by an AS (/32s) AS568 : SUMNET-AS DISO-UNRRA Possible Bogus AS AS63000 Announced by: AS14522 EC-SASA-LACNIC SatNet S.A. Aggregation Summary The algorithm used in this report proposes aggregation only when there is a precise match using the AS path, so as to preserve traffic transit policies. Aggregation is also proposed across non-advertised address space ('holes'). --- 06Dec02 --- ASnum NetsNow NetsAggr NetGain % Gain Description Table 116820 84482 32338 27.7% All ASes AS3908 1716 975 741 43.2% SUPERNETASBLK SuperNet, Inc. AS701 1712 1227 485 28.3% ALTERNET-AS UUNET Technologies, Inc. AS18566 395 5 390 98.7% COVAD Covad Communications AS7018 1389 1034 355 25.6% ATT-INTERNET4 AT&T WorldNet Services AS4323 522 185 337 64.6% TW-COMM Time Warner Communications, Inc. AS7843 644 307 337 52.3% ADELPHIA-AS Adelphia Corp. AS6197 458 124 334 72.9% BATI-ATL BellSouth Network Solutions, Inc AS1221 1162 843 319 27.5% ASN-TELSTRA Telstra Pty Ltd AS4355 404 136 268 66.3% ERMS-EARTHLNK EARTHLINK, INC AS6347 351 83 268 76.4% DIAMOND SAVVIS Communications Corporation AS22927 289 22 267 92.4% AR-TEAR2-LACNIC TELEFONICA DE ARGENTINA AS1239 924 663 261 28.2% SPRINTLINK Sprint AS7046 584 323 261 44.7% UUNET-CUSTOMER UUNET Technologies, Inc. AS705 434 195 239 55.1% ASN-ALTERNET UUNET Technologies, Inc. AS4814 248 15 233 94.0% CHINANET-BEIJING-AP China Telecom (Group) AS1 663 439 224 33.8% GNTY-1 Genuity AS6198 417 198 219 52.5% BATI-MIA BellSouth Network Solutions, Inc AS4151 351 135 216 61.5% USDA-1 USDA AS17676 232 28 204 87.9% GIGAINFRA XTAGE CORPORATION AS852 653 464 189 28.9% ASN852 Telus Advanced Communications AS690 508 321 187 36.8% MERIT-AS-27 Merit Network Inc. AS4134 299 115 184 61.5% ERX-CHINALINK Data Communications Bureau AS6595 243 59 184 75.7% DODDSEUR DoD Education Activity Network Assistance Center AS209 520 338 182 35.0% ASN-QWEST Qwest AS2048 262 88 174 66.4% LANET-1 State of Louisiana AS6140 279 127 152 54.5% IMPSAT-USA ImpSat AS6327 183 34 149 81.4% SHAWFIBER Shaw Fiberlink Limited AS2386 374 229 145 38.8% INS-AS AT&T Data Communications Services AS17557 314 172 142 45.2% PKTELECOM-AS-AP Pakistan Telecom AS3215 309 169 140 45.3% AS3215 France Telecom Transpac Total 16839 9053 7786 46.2% Top 30 total Please see http://www.cidr-report.org for the full report ------------------------------------ Copies of this report are mailed to: nanog(a)merit.edu eof-list(a)ripe.net apops(a)lists.apnic.net routing-wg(a)ripe.net afnog(a)afnog.org

1 0

Re: Bin Laden Associate Warns of Cyberattack
by Michael.Dillon＠radianz.com 06 Dec '02

06 Dec '02

>It is a great example of how well Al-Quedah manipulates the media. >There are more ways to wreak havoc than script kiddies and DOS attacks. When was the last time you took a sample and tested for the presence of fertilizer *BEFORE* you let the truck driver put that diesel into your generator tanks? And did anyone else notice how the NY Times article gave some clear instructions on how to identify the building in Tribeca even though they didn't include the street address? The best defence against all of these potential terrorist attacks is to do what the military does, i.e. spread out. Never put more than a fraction of your eggs in one basket. Use the network to connect diverse and widespread assets so that they can function as a unit even though they are physically separated. This philosophy works whether your assets are combat soldiers or network PoPs. And again, there is a role for government here. How about tax reductions for companies who harden their networks by removing single points of failure that are vulnerable to terrorist attack? --Michael Dillon

13 18

OT The origin of the Internet
by Kevin Oberman 06 Dec '02

06 Dec '02

O.K. This is less off-topic than half the posts this week. For the REAL origin of the Internet, see http://www.uclick.com/client/byr/nq/ (Make sure that you see the entry for 12/5/02.)

2 1

paix
by Scott Granados 05 Dec '02

05 Dec '02

Anybody else seeing a loss of paix? My peering dropped. as well as everyone else in sf. While writing this my phone rang and it was paix. Seems mfn did an unreported bit of maintenance. Anyone else on the peering by paix switch at e-xchange at least will have lost service but it should be restored.

2 1

More studies: Estimates were wrong
by Sean Donelan 05 Dec '02

05 Dec '02

David Wessel's column in the Wall Street Journal covers the debate over how much electricity does the Internet use. (paid subscription) http://online.wsj.com/article/0,,SB1039040314228813793,00.html?mod=technolo… Mark Mills wrote a paper how the US was running short on power, and the Internet was consuming 13% of it. Jonathan Koomey writes research papers that the number is about 3%. To quote the column: "It's an instructive case study in how a simple assertion of questionable accuracy can be repeated so often that it is accepted as fact by people in the press, in government and on Wall Street who ought to be more discerning."

1 0

mrtg graph
by Sameer R. Manek 05 Dec '02

05 Dec '02

Could someone please send me an mrtg graph of any router that handles sufficient traffic, and goes back at least a year? I need it for a school project. Thanks ------------------------------------------------------------------------- Sameer R. Manek Email: manek(a)ghur.net "What one has not experienced, one will never understand in print." --Isadora Duncan -------------------------------------------------------------------------

2 1

Packets on the floor..
by Robert Mathews 04 Dec '02

04 Dec '02

Has anyone seen problems w/ AS 7170 over the last three days? A trace from two different locales just now (as it has over the past two days at least) indicate that packets are getting dropped on the floor at seattlebr-aip.att-disc.net (135.206.243.11) on its way to the Pacific.. All info appreciated.. All the best.. Robert.

1 0

New ASN allocation from IANA to RIPE
by Rob Thomas 04 Dec '02

04 Dec '02

Hi, NANOGers. As of 03 December 2002 IANA has allocated a block of formerly unallocated ASNs to RIPE. I have adjusted my monitoring accordingly, and you should review any ASN filtering or logging you have in place. The ASN ranges involved are: Was: 28672 - 32767 IANA Now: 28672 - 29695 RIPE 29696 - 32767 IANA My ASN monitoring can be found at the URLs below. http://www.cymru.com/BGP/asnbogusrep.html http://www.cymru.com/BGP/asnreport.html http://www.cymru.com/BGP/ Comments and feedback are welcome and encouraged. Be the first (heck, even second) in your ASN to join the CREDITS section! :) Thanks, Rob. -- Rob Thomas http://www.cymru.com ASSERT(coffee != empty);

1 0

Re: Operational Issues with 69.0.0.0/8...
by Martin J. Levy 04 Dec '02

04 Dec '02

Todd, If this helps. Do something like the following... telnet route-views.oregon-ix.net > /tmp/file term len 0 sh ip bgp 69.0.0.0 255.0.0.0 l quit cut -c62-2000 < /tmp/file | awk '{print $1}' | sort -n | uniq -c | more ...your commands will vary. You will see plenty of routes within 69/8. A closer look with show that around 121 routes are seen in the 69/8 range via most of the feeds into Oregon. There is one big exception... 69.4.64.0/20 ... it shows up via AS-2548 (Digex) and the other feeds, but it's the only route within 69/8 that shows up via AS-2548. This is valuable information. It does not mean there is filtering within AS-2548, but I would recommend you contact them to further this investigation. BTW: This is exactly what Oregon is great for! It shows up issues like this with ease. Thanks! Martin --------------------------- At 01:47 PM 12/2/2002 -0500, Todd A. Blank wrote: >Thanks for the reply, James. > >I wish I could tell you the answer. We see traffic passing through some >of the routers (transit), but on each network, or their downstreams >there seem to be different devices filtering. Sometimes it is a border >or peering router. In other cases, it has been access devices, such as >firewalls. > >One we resolved this morning (with some help from the good folks at >ARIN) was a downstream provider from one of these transit providers that >was filtering in their devices as well. > >I am just trying to raise general awareness that the 69.0.0.0/8 block is >assigned and out there in use, and to get people to re-examine their >filters, access lists, etc. > >You help and response is appreciated. > >Sincerely, > >Todd A. Blank >614.207.5853 > >-----Original Message----- >From: Feger, James [mailto:jfeger@feger.net] >Sent: Monday, December 02, 2002 1:35 PM >To: Todd A. Blank >Subject: Re: Operational Issues with 69.0.0.0/8... > >When you say 'Networks involved' do you mean those providers are >blocking >the traffic, or you see these networks in the transit? > >Thanks, >James > > >On Mon, 2 Dec 2002, Todd A. Blank wrote: > >> >> To all concerned: >> >> We have been assigned a CIDR of 69.1.192.0/19. >> >> We have had numerous problems getting traffic through to various >destinations. >> >> We are finding that many routers are still filtering 69.0.0.0/8. >> >> This block used to be restricted, but was assigned by IANA to ARIN in >August of 2002. >> >> If anyone is still filtering this block in their routers, please >remove the filters! >> >> Here are some of the destinations that are not reachable if your >source is anywhere in the 69.0.0.0/8 CIDR: >> >> www.cplink2.com >> www.ocas.com >> www.indofilms.com >> www.lavalife.com >> >> >> Some of the Networks involved are Cable and Wireless, Allegiance >Internet and AT&T. >> >> Thank you, >> >> Todd A. Blank >> IPOutlet LLC >> 614.207.5853 >>

2 1