April 2001 - Test - lists.nanog.org

Young Network Operators (was RE: California power ... unplugged)
by Sean Donelan 29 Apr '01

29 Apr '01

On Sat, 28 April 2001, "James S. Smith" wrote: > Perhaps you just need some properly built nuclear plants. :) Ontario has New nuclear plant design has some interesting differences from the old plants. What caused these changes? Of course, there were several incidents which woke people up. But another change also occurred. Nuclear engineering fell out of favor among college students. There were fewer youngsters entering the industry after TMI, so the average age of nuclear engineers has increase. With age comes wisdom, or just senility? Older designs were "big" in every sense of the word. If you can only build one plant, you better make it the biggest plant you can. Old designs reflected a deep belief that you could maintain control. Control systems kept the system safe. The engineers were smart people, and had confidence in their ability to engineer their way out of trouble. Is this an error of youth? A young driver believes he can control the car in any situation, an older driver keeps the car out of situations requiring control beyond his ability. What does this have to do with network operators? With the downturn in the high-tech job market, and the apparent end of the 21-year old CEO getting $100 million in venture capital, will we see a similar increase in the average age of network engineers? And with the increase in age, will we see more conservative network operations coming out of companies? Or will we adopt the extreme slow conservatism of the telephone industry? Sometimes you need to accept some risk in order to innovate. If you never deploy something until it is perfect, it will take a very long time.

1 0

California power ... unplugged.
by Roeland Meyer 28 Apr '01

28 Apr '01

This is a follow-up of something I posted last November. The Enviro-Nazis are at it again, demonstrating why no new power plants have been built here, in the past 15 years. Hunter's Point: San Francisco proposed doubling capacity of the Hunter's Point facility by building a duplicate plant right next to the existing one. Local groups are protesting on environmental grounds. Coyote Valley: San Jose finally approved the construction of the CalPine power plant, needed to support the Santa Teresa, Coyote Valley, and Morgan Hill areas. But, local slow-growth advocates and enviro-nazis are protesting and threatening to sue San Jose. San Jose is asking the state to help smooth things over so that the plant can get built. Between the enviro-nazis and the no-nukes folks (they *are* different groups), California has been dead-locked on power plant construction for almost 20 years. The winning strategy; get locals to buy into the "not in my backyard" sentiment (an easy sell, it worked in stopping prison construction, as well). This, in a population so brainwashed, it actually wants to pay more taxes, even when they are already taxed at the 60% level. Further, this same population thinks that electric cars are the answer to the environmental problem, since they produce no pollution (a fallacy and contradiction of known facts, for those that don't know). In 20 years, CA has gone from a 300% over-capacity to the present shortage. In the past 8 months, energy costs have sky-rocketed 700-900% on only 3% increased usage. The reason; CA doesn't produce enough of its own power and, in the last year, has crossed over to being dependent on energy imports, rather than a supplier of energy. This is a crucial transition that CA was warned about over 25 years ago, when the no-nukes folks were very active here. Obviously, they didn't listen. Estimates are that, it takes two years to bring a fossil-fuel plant online and 3-4 years for a nuclear plant. However, fossil-fuel plants like all plants, have to meet the California Clean Air Act. This means that they may not be allowed to operate, due to environmental constraints, even if they were magically built tomorrow. Remember that California has its own, much stricter, environmental guidelines. These are guidelines that only nuclear plants can approach. Yet, this is in a state that is littered with "nuclear-free" zones. Bottom-line: 1) Expect the paralysis to continue for quite a while and then wait 3-4 years for plants to come online. Reasonable estimates are out past 5 years. 2) Expect increasing levels of power outages, both Summer and Winter (Stage 3, rolling blackouts). 3) Expect increasing energy bills, both in gasoline and electricity, on the order of 300-500%, in the next 5 years. 4) Expect a coming exodus of industry, to anywhere but California. 5) Expect ever more totalitarian regulations, to manage the long-term emergency (you'll have to get a license to plug a toaster into the power-grid). These regulations will not go away, even if we get enough power plants online. 6) Dick Cheney was correct, we need to start building nuclear plants out here. 7) Data centers and colo providers will come under increasing pressure to pay their "fair share" of power generation (this means that they get charged double or even triple). 8) Backup power generators will have to be replaced with units that can stand increased duty-cycles or even provide sustained long-term operation. 9) New colo facilities will have to face increased regulatory pressure and approval cycles. colo prices will go up, as a direct result of these increased costs. 10) Expect to see the return of the wind-fall profits tax, on a permanent basis. Caveats: 1) If the enviro-nazis get "nuked" tomorrow, this will only change the time table, by a year or two. Energy plants are not built by magic. 2) This entire scenario could reduce energy usage growth to about 1-2%. Usage will continue to increase. Thus, exacerbating the problem. 3) Houston could get "nuked", by the feds. -- MHSC is looking forward to doing business outside of California. :) -- ROELAND M.J. MEYER Managing Director Morgan Hill Software Company, Inc. TEL: +001 925 373 3954 FAX: +001 925 373 9781 http://www.mhsc.com mailto: rmeyer(a)mhsc.com

2 1

OT (possibly)
by Scott Walker 28 Apr '01

28 Apr '01

I'm looking for a good referance on using ipf on solaris 8. I have to setup a firewall and would like to use solaris. OTherwise it's off to linux for me.

2 1

RE: RIP and RIPv2, "The glue that makes the internet work"
by Roeland Meyer 28 Apr '01

28 Apr '01

That was last month's issue. I chuckled too. But, for a small end-point LAN, it's not bad. Consider it appropriate tech, applied in appropriate places. Even fully static routes aren't bad, on small enough networks. > -----Original Message----- > From: John M . Brown [mailto:jmbrown@ihighway.net] > Sent: Tuesday, April 24, 2001 6:51 PM > To: nanog(a)merit.edu > Subject: RIP and RIPv2, "The glue that makes the internet work" > > > > Latest Linux Mag has this really nice long article about how > RIP and its new version RIPv2 is the GLUE that makes the internet > work. > > I almost fell down on that. > > Oh, wait, I do know a couple of exchange points that wanted to or are > running RIP. No REALLY!! > > jmbrown > >

5 4

Re: RIP and RIPv2, "The glue that makes the internet work"
by bmanning＠vacation.karoshi.com 28 Apr '01

28 Apr '01

> > > > What was/is the largest production network (in number of end nodes) that > > used/uses RIP as the IGP? > > Xerox routed a few thousand subnets of 13/8 with RIP (v1!) as late as 1998. > Dunno if that's large enough. > > Bill > Its pretty big. Most of the data is not verifiable, but a profile of 100-10,000 subnets, between 5-2000 nodes per subnet w/ RIPv1 seems to be emerging for sites like Xerox as well as old NSFnet regionals. On the other hand, reports of large, multinational networks running static routing in their cores seem to indicate a desire to have routing in the core more stable than any dynamic protocol will allow. With the growth in the number of injected prefixes and varient paths, one might say that the "value proposition" of dynamic routing is not what it once was... Or it could be that the folks running the big networks are more comfortable with manual/static routing systems? Such environments certainly provide easier means to set enforcable service level agreements. But my muse has gotten the better of me. --bill

2 1

RE: California power ... unplugged.
by Roeland Meyer 28 Apr '01

28 Apr '01

> From: Subodh Nijsure [mailto:subodh@best.com] > Sent: Saturday, April 28, 2001 11:17 AM > Oh come on you are falling for media spin put out by the politicians. Actually, most of the media spin does not bring up these issues. In fact, these points are conspicuously absent. They completely glossed over the impact of the Cal Clean Air Act. On your other point, I invite you to note the name of my company and visit my about page. > And if you think you don't like clean air take a trip to China or India > which have 1/10th amount of cars compared to US and see what happens > when nobody pays attention to environmental regulations. Then you will thank > the so called "enviro-nazis". I never said that I don't like clean air :). What I hoped the article pointed out was the conflicts between rabid enviro-nazis, no-nukes folks, and California energy needs. Yes, the Sierra Club supported the California Clean Air Act (CCAA). This is probably the most draconian, uncompromising, environmental measure that has ever been passed into law, IMHO. They celebrated when it was passed. Yet, they took no stance on energy deregulation until well after the fact, when it was too late. They helped create the quandry we are in today. That was my point. -- ROELAND M.J. MEYER Managing Director Morgan Hill Software Company, Inc. TEL: +001 925 373 3954 FAX: +001 925 373 9781 http://www.mhsc.com mailto: rmeyer(a)mhsc.com

1 0

Misconfigured BGP
by Marshall Eubanks 28 Apr '01

28 Apr '01

Hello; I sent a previous version of this message Friday morning to the admin contact for AS 1237, but I have as yet received no response. I am not sure if this is a real problem - I can still ping them - but it looks ugly to me. ------------------------------------------------------------------------------------- The BGP announcements for System Engineering Research Institute (SERI) (ASN-EUNSOL) R&D Net Group Eoeun-dong 1, Daejon KR Autonomous System Name: KREONET Autonomous System Number: 1237 appear to be misconfigured : *> 150.183.34.0/24 157.130.46.53 0 701 6453 1237 9270 1237 i etc. This is a routing loop; although it may work in practice, it is not a proper use of BGP and may not do what you intended. A list of all of the (many) affected address blocks follows. Regards Marshall Eubanks Multicast Technologies, Inc. 10301 Democracy Lane, Suite 410 Fairfax, Virginia 22030 Phone : 703-293-9624 Fax : 703-293-9609 e-mail : tme(a)on-the-i.com http://www.on-the-i.com Test your network for multicast : http://www.multicasttech.com/mt/ ----------------------------------------------------------------------------------------------------------- will search for routing loops ROUTING LOOP Detected for ASN 1237 Prefix = 150.183.34.0/24 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 150.183.35.0/24 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 150.183.38.0/24 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.230.118.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.230.119.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.230.120.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.230.121.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.230.122.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.230.123.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.230.124.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.230.125.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.230.126.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.32.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.34.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.37.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.39.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.40.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.41.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.42.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.43.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.45.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.47.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.49.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.51.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.60.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.61.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.237.62.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.241.175.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.247.194.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.247.197.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.247.198.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.247.199.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.247.201.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.247.202.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.247.203.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.250.189.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.250.191.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 203.253.247.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.98.47.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.98.58.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.98.59.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.130.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.131.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.144.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.145.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.146.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.147.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.148.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.149.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.150.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.151.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.152.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.154.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.155.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.156.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.157.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.158.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.159.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.210.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.211.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.212.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.213.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.214.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.215.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.216.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.217.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.218.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.219.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.220.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.221.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.110.223.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.119.59.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.119.60.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.119.61.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.119.62.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.119.63.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.119.85.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.119.90.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.119.91.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.125.48.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.125.49.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.125.50.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.125.51.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.125.52.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.125.53.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.125.54.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.125.55.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = 210.219.57.0 : PATH = : 1239 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 1237 Prefix = : PATH = : 701 6453 1237 9270 1237 ROUTING LOOP Detected for ASN 11303 Prefix = 216.52.158.0 : PATH = : 1239 11853 11303 11301 11303 ROUTING LOOP Detected for ASN 11303 Prefix = : PATH = : 701 11853 11303 11301 11303

1 0

The Cidr Report
by Tony Bates 28 Apr '01

28 Apr '01

This is an auto-generated mail on Fri Apr 27 23:00:00 PDT 2001 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 27Apr01 0) General Status Table History ------------- Date Prefixes 200401 100216 210401 100108 220401 100099 230401 100219 240401 100457 250401 100635 260401 100755 270401 100797 Check http://www.employees.org/~tbates/cidr.plot.html for a plot of the table history. Possible Bogus Routes --------------------- *** Bogus 218.6.128.0/17 from AS4134 AS Summary ---------- Number of ASes in routing system: 10591 Number of ASes announcing only one prefix: 6292 (3570 cidr, 2722 classful) Largest number of cidr routes: 1365 announced by AS705 Largest number of classful routes: 1602 announced by AS1221 1) Gains by aggregating at the origin AS level --- 27Apr01 --- ASnum NetsNow NetsCIDR NetGain % Gain Description AS1221 1602 1190 412 25.7% TELSTRA-AS AS701 1409 1222 187 13.3% Alternet AS705 393 258 135 34.4% part of AS assignment AS701 - AS7 AS4151 257 145 112 43.6% part of AS assignment AS4151 - AS AS6429 216 105 111 51.4% ATT LA Internet Chile AS6595 163 62 101 62.0% autonomous system number assigned AS13999 104 8 96 92.3% autonomous system number assigned AS4293 372 279 93 25.0% part of AS assignment AS4287 - AS AS8013 326 239 87 26.7% autonomous system number assigned AS7018 698 613 85 12.2% AT&T WorldNet Service Backbone AS4755 229 144 85 37.1% part of AS assignment AS4608 - AS AS15412 260 183 77 29.6% FLAG Telecom Global Internet AS AS577 238 169 69 29.0% autonomous system number assigned AS6471 113 49 64 56.6% autonomous system number assigned AS5106 101 37 64 63.4% autonomous system number assigned AS3464 153 91 62 40.5% Alabama Research and Education Ne AS3749 120 59 61 50.8% autonomous system number assigned AS724 202 144 58 28.7% part of AS assignment AS721 - AS7 AS3602 253 195 58 22.9% Sprint Canada Inc. AS11252 92 34 58 63.0% autonomous system number assigned AS16758 63 6 57 90.5% autonomous system number assigned AS1 608 551 57 9.4% GTE Internetworking AS6413 67 11 56 83.6% autonomous system number assigned AS226 149 93 56 37.6% Los Nettos AS4323 232 179 53 22.8% Time Warner Telecom Internet AS852 203 155 48 23.6% autonomous system number assigned AS9269 109 62 47 43.1% Hong Kong CTI AS855 145 99 46 31.7% part of AS assignment AS853 - AS1 AS13544 68 22 46 67.6% autonomous system number assigned AS12235 49 3 46 93.9% Cove Software Systems Inc 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

1 0

NOC number for concert.net?
by Jim Mercer 27 Apr '01

27 Apr '01

i've got a nasty attack eminating from concert.net. i attempted to find a NOC number at: http://puck.nether.net/netops/nocs.cgi - nothing http://www.concert.net - got alot of 404's, and no support numbers at all. anyone got a NOC number? -- [ Jim Mercer jim(a)pneumonoultramicroscopicsilicovolcanoconiosis.ca ] [ Reptilian Research -- Longer Life through Colder Blood ] [ aka jim(a)reptiles.org +1 416 410-5633 ]

3 2

Re: jumbo frames
by Richard A. Steenbergen 27 Apr '01

27 Apr '01

On Fri, Apr 27, 2001 at 02:10:48PM -0500, Stephen Sprunk wrote: > > Or unless you actually have >1500 MTU to the hosts, which is quite > possible. A traffic study from MCI's backbone (obviously years ago) > showed nearly 40% (byte-wise) of their traffic was in packets >1500 > bytes. With the death of FDDI, this has probably come down, but > GE-attached servers in colos should push it back up. Probably not since GigE defaults to 1500 bytes and there is no agreed upon standard for jumbo frames. Right now it doesn't make much sense to attempt jumbo frames for packets headed outside of your administrative control, because of PMTU-D problems. > Router performance is, however, directly related to packet size, since > forwarding overhead is per-packet and not per-byte. It is much easier > to fill big pipes with 9000 byte packets than 1500 byte packets. More importantly it's easier to generate the packets in the first place. The amount of overhead that goes into generating a packet on a host is really quite a bit, and operations on 1500 bytes are exactly the opposite of how most hosts are optimized. At gigabit speeds (125MB/sec) it only takes 12 microseconds to transfer 1500 bytes. -- Richard A Steenbergen <ras(a)e-gerbil.net> http://www.e-gerbil.net/ras PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6)

2 2