December 1999 - Test - lists.nanog.org

Re: The Cidr Report
by john heasley 25 Dec '99

25 Dec '99

On Fri, Dec 24, 1999 at 02:35:29PM -0800, dopacki(a)adotout.com wrote: > > Save your breath.. I have been trying for weeks to get Tony to take 64/8 > off of the "bogus routes" section. IPMA was very responsive, but Tony has > not ack'd any of my e-mails on the subject :( > > -Dennis Opacki demand a refund!

2 1

Fiber versus 24inch water main
by Sean Donelan 25 Dec '99

25 Dec '99

On Thursday traffic was backed up around my house. A contractor installing fiber along the highway bored through a 24inch water main. You can see the results in this picture. http://www.stlnet.com/postnet/stories.nsf/ByDocID/049A42145BD8D1F8862568510…

3 2

The Cidr Report
by Tony Bates 24 Dec '99

24 Dec '99

This is an auto-generated mail on Fri Dec 24 12:00:00 PST 1999 It is not checked before it leaves my workstation. However, hopefully you will find this report interesting and will take the time to look through this to see if you can improve the amount of aggregation you perform. The report is split into sections: 0) General Status List the route table history for the last week, list any possibly bogus routes seen and give some status on ASes. 1) Gains by aggregating at the origin AS level This lists the "Top 30" players who if they decided to aggregate their announced classful prefixes at the origin AS level could make a significant difference in the reduction of the current size of the Internet routing table. This calculation does not take into account the inclusion of holes when forming an aggregate so it is possible even larger reduction should be possible. 2) Weekly Delta A summary of the last weeks changes in terms of withdrawn and added routes. Please note that this is only a snapshot but does give some indication of ASes participating in CIDR. Clearly, it is generally a good thing to see a large amont of withdrawls. 3) Interesting aggregates Interesting here means not an aggregate made as a set of classful routes. Thanks to xara.net for giving me access to their routing tables once a day. Please send any comments about this report directly to me. Check http://www.employees.org/~tbates/cidr-report.html for a daily update of this report. ------------------------------------------------------------------------------ CIDR REPORT for 24Dec99 0) General Status Table History ------------- Date Prefixes 171299 68465 181299 68472 191299 68445 201299 68620 211299 68566 221299 68665 231299 68991 241299 69384 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 64.4.64.0/19 from AS7398 *** Bogus 64.4.128.0/19 from AS13932 *** Bogus 64.4.192.0/19 from AS6214 *** Bogus 64.5.0.0/19 from AS14107 *** Bogus 64.5.64.0/19 from AS6601 *** Bogus 64.6.32.0/20 from AS13740 *** Bogus 64.6.64.0/20 from AS10726 *** Bogus 64.6.96.0/20 from AS8049 *** Bogus 64.6.160.0/23 from AS11354 *** Bogus 64.6.160.0/20 from AS11354 *** Bogus 64.6.162.0/24 from AS11354 *** Bogus 64.6.192.0/21 from AS14215 *** Bogus 64.6.200.0/23 from AS14215 *** Bogus 64.6.204.0/23 from AS14215 *** Bogus 64.6.206.0/23 from AS14215 *** Bogus 64.7.0.0/24 from AS6461 *** Bogus 64.7.1.0/24 from AS3967 *** Bogus 64.7.2.0/23 from AS3967 *** Bogus 64.7.4.0/23 from AS3967 *** Bogus 64.7.32.0/20 from AS8010 *** Bogus 64.7.64.0/20 from AS2914 *** Bogus 64.7.128.0/20 from AS11647 *** Bogus 64.7.160.0/20 from AS13549 *** Bogus 64.8.0.0/20 from AS7843 *** Bogus 64.8.24.0/21 from AS7843 *** Bogus 64.9.0.0/19 from AS7843 *** Bogus 64.9.32.0/20 from AS701 *** Bogus 64.9.48.0/20 from AS1239 *** Bogus 64.9.128.0/18 from AS5003 *** Bogus 64.10.0.0/16 from AS816 *** Bogus 64.10.10.0/24 from AS705 *** Bogus 64.10.11.0/24 from AS705 *** Bogus 64.13.0.0/20 from AS6921 *** Bogus 64.13.0.0/19 from AS6921 *** Bogus 64.13.16.0/21 from AS6921 *** Bogus 64.13.24.0/21 from AS6921 *** Bogus 64.14.0.0/19 from AS3967 *** Bogus 64.14.32.0/19 from AS3967 *** Bogus 64.14.64.0/20 from AS3967 *** Bogus 64.14.80.0/20 from AS3967 *** Bogus 64.14.96.0/20 from AS3967 *** Bogus 64.14.112.0/20 from AS3967 *** Bogus 64.14.128.0/20 from AS3967 *** Bogus 64.16.0.0/19 from AS14078 *** Bogus 64.21.0.0/18 from AS8001 *** Bogus 219.5.47.0 from AS2548 *** Bogus 219.91.160.0/22 from AS7742 *** Bogus 219.91.164.0/23 from AS7742 AS Summary ---------- Number of ASes in routing system: 6329 Number of ASes announcing only one prefix: 3363 (1845 cidr, 1518 classful) Largest number of cidr routes: 674 announced by AS701 Largest number of classful routes: 959 announced by AS701 1) Gains by aggregating at the origin AS level --- 24Dec99 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS271 383 141 242 63.2% BCnet Backbone AS7046 400 258 142 35.5% UUNET-CUSTOMER AS2609 126 11 115 91.3% EUnet-TN AS9269 134 21 113 84.3% Hong Kong CTI AS1221 638 525 113 17.7% TELSTRA-AS AS7657 274 178 96 35.0% The Internet Group Limited AS7545 153 60 93 60.8% TPG Internet Pty Ltd AS1653 129 38 91 70.5% SUNET Swedish University Network AS6429 203 116 87 42.9% RDC-INTERNET AS4293 238 151 87 36.6% Internal ASN for C&W AS174 567 482 85 15.0% Performance Systems International AS9706 104 23 81 77.9% Pusan Metropolitan City Office of AS7496 121 41 80 66.1% Power Up AS577 259 181 78 30.1% Bell Canada Backbone AS3749 135 62 73 54.1% TECNET AS705 229 163 66 28.8% ALTERNET-AS AS4200 171 105 66 38.6% AGIS (Apex Global Information Ser AS9304 78 20 58 74.4% Hutchcity AS4740 342 284 58 17.0% Ozemail Pty Ltd (ASN-OZEMAIL) AS816 234 178 56 23.9% UUNET Canada (ASN-UUNETCA-AS4) AS209 346 291 55 15.9% Qwest Communications AS684 92 46 46 50.0% Manitoba Regional Network Backbon AS1 522 482 40 7.7% GTE Internetworking AS4755 109 70 39 35.8% Videsh Sanchar Nigam Ltd. India AS701 959 921 38 4.0% Alternet AS6528 45 7 38 84.4% WORLD-LYNX AS7390 50 14 36 72.0% NLSLAN AS7029 77 41 36 46.8% ALLTELNET AS6172 150 114 36 24.0% HOME-NET-1 AS1727 117 82 35 29.9% MRMS-WEST For the rest of the previous weeks gain information please see http://www.employees.org:80/~tbates/cidr-report.html 2) Weekly Delta Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report 3) Interesting aggregates Please see http://www.employees.org:80/~tbates/cidr-report.html for this part of the report

2 1

Re: Y2k silly season
by Hank Nussbacher 24 Dec '99

24 Dec '99

At 03:52 22/12/99 -0800, Sean Donelan wrote: In regards to self fulfilling prophecies: The phone companies won't admit it but they are scared that at 1 second past midnight, everyone will say to themselves, "Hmmm, lights are still on, I wonder if the phones have stopped working?" and then within 1 minute, millions of people will be lifting their phones off the hooks to check dial-tone. You know what happens when that happens. :-) -Hank > >As Alan points out, it looks like silly season will be in full swing. Here >is a site claiming it will check the top web sites in the world, and if 5% >aren't responding at 1 minute before midnight (pick your time zone) a major >disaster has happened. > >http://biz.yahoo.com/prnews/991222/inferno200_1.html > >As has been pointed out before, many sites plan to shutdown their web sites or >disconnect from the Internet over the New Year's weekend. Which I guess is >a self-fulling prediction. The Internet is still considered an "extra" and >not a necessary connection like the telephone or ATM. I haven't heard anyone >suggesting they would turn off their ATMs, even though they are Y2K ready, just >to be safe. > >You can read ATM as representing either acronym. > > > >

2 1

Re: Y2k silly season
by George Herbert 24 Dec '99

24 Dec '99

I don't know about where you live, but around here they've been saying "please don't pick up the phone right after midnight just to test it, if everyone does that it will crash...". Loudly, on TV, getting the local stations to spread the word... -george william herbert gherbert(a)crl.com

1 0

Further Y2K silliness
by Hank Nussbacher 24 Dec '99

24 Dec '99

I just got the following email from a fairly large multinational company: GROUP WatchDog Server: MHUB001/MHSVR/xxxxxxx ----------------------------------------------------------------------- The following attachments were removed in accordance with Firm policy effective 12/20/99. Attachments with file types .EXE, .COM, .JPG, .MPG, .AVI, .SCR, .GIF, and .BMP. will be stripped from internet messages until 1/10/2000. ---------------------- Oh well, I guess there are gonna be many "retransmissions" during the first week of January if this is gonna be corporate policy thruout the net. :-) -Hank

1 0

Re: After Y2K, critical infrastructure
by Sean Donelan 23 Dec '99

23 Dec '99

At 08:49 PM 12/23/99 -0500, Deepak Jain wrote: >Sorry to ruin your sleep. NT is ONLY C2 certified as a standalone >workstation. I.e. NO NETWORKING DRIVERS ENABLED Good grief Charlie Brown, it was a joke. C2 certification means about as much as Y2K certification. There are so many qualifications they are meaningless in any real world situation. It's another checkmark you have to make on the paperwork before winning the bid. I know my laptop is ready because it came with a Y2K-ready sticker on it. After I brought it home, I only needed to download a half-dozen different patches for Y2K, security, and just plain bugs. The issue of being C2 certified only as a standalone workstation is hardly unique to Microsoft NT. As far as I know, ALL the C2 certified operating systems Unix, VMS, VM, etc are only in standalone mode. Others, such as Linux, aren't certified even in standalone mode (well, maybe in the unplugged, encased in concrete, and dropped to the bottom of the ocean mode). If that wasn't a troll, I don't know what is.

2 1

After Y2K, critical infrastructure
by Sean Donelan 23 Dec '99

23 Dec '99

> I don't know how big of a deal is being made about 2.038K on a corporate > management level, but it would seem that the ensuing months would be just > about a perfect time to address this issue. After all, many companies have > teams for the date-field issue right now, and we've gotten pretty good in > the past couple of years at analyzing this problem. It would only make > sense to immediately move on to the 2038 work after Y2K settles down. Let's > just not wait until 2035 to deal with it this time, huh? After Y2K settles down, the most likely next bandwagon will be so-called critical infrastructure or Cyber-assurance. If you look behind the curtain, you will find many of the people involved in the Y2K hype are actually from the the critical infrastructure programs which got side-lined this year due to Y2K. I expect when they return to their "regular" jobs, they will want to keep the extra money they got this year for Y2K as part of their regular budget next year. I'm hoping the "hackers" will party and get drunk over New Year's, and leave the so-called critical infrastructure alone. If you think you filled out a lot of paperwork for Y2K, and you ain't seen anything yet. I for one sleep much better knowing Microsoft NT is certified C2 ready :-)

6 5

Re: Silly season
by Richard Steenbergen 23 Dec '99

23 Dec '99

On Wed, Dec 22, 1999 at 01:55:17PM -0900, Aaron Dewell wrote: > > Or February 6, 2106 at 6:28:14 if your UNIX system keeps an unsigned 32-bit > time_t. I Y2.038k tested my Solaris 7 box, it kept time past 3:14 AM 1/19/38, > but the date command would not set it. Which implies that the kernel itself is > unsigned, while the date command uses a signed number. Wasting an entire 2 billion seconds to check for a -1 error condition instead of the one's complement 0xFFFFFFFF is remarkably stupid imho. But it would break a lot of userland programs to change. As far as I know in BSD it is still a signed long, at least in machine/ansi.h. -- Richard A. Steenbergen <ras(a)above.net> http://users.quadrunner.com/humble PGP Key ID: 0x60AB0AD1 (E5 35 10 1D DE 7D 8C A7 09 1C 80 8B AF B9 77 BB) AboveNet Communications - AboveSecure Network Security Engineer, Vienna VA "A mind is like a parachute, it works best when open." -- Unknown

9 12

Floods Telcos and FCC outage reports
by Sean Donelan 23 Dec '99

23 Dec '99

The New Jersey state utility commission completed its investigation into the Rochelle Park, NJ central office failure due to flooding this fall. Bell Atlantic originally reported the cause as a dam breaking and water entering through doors left open by AT&T. AT&T disputed the report filed with the FCC. The state board investigators found no dam had broken and water had entered by a number of entrances, including cable vaults, basement plumbing fixtures, as well as the rear door. Bell Atlantic's report didn't mention the flood water entering through other entrances. The state board couldn't conclude whether any one source was the cause of the shutdown of the power plant at the central office. The board ordered both Bell Atlantic and AT&T to make improvements, investigate the flood risk at other locations, and report back to the board. Bell Atlantic stands by its report, except they now agree no dam broke. The FCC's investigation is continuing. Source: Bergen County Record http://www.bergen.com/news/flood23199912234.htm

1 0