- NANOG - lists.nanog.org

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 28 Apr '01

28 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

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

27 Apr '01

On Fri, Apr 27, 2001 at 12:47:09PM -0700, Tony Hain wrote: > > I understand all those points; I was reacting to the comment that the > only jumbo frames were between the routers, so the only ones coming in > would be 1500. Look at John's notes from 4/25 8:10pm & 4/26 9:40am. > There is no way I know of for a larger frame by itself to increase the > speed of a packet. What was missing was the subsequent comment about > tunneling those packets (thus increasing the size beyond 1500) across > the GE links to the distribution router. Avoiding fragmentation > clearly has performance gains, but fragmentation is unnecessary if the > packet size remains the same from end to end. The original scenario > was simply standard-size feeders into a router, with jumbo frame GE > between the core routers, then standard-size distribution on the other > end. The claim was that jumbo frames in the middle made it go faster. > If this is true I want to know how. It is also possible that he has packets entering and leaving his network by SONET, ATM, FDDI, or anything else which is not Ethernet. By supporting jumbo frames on his GigE router links, he is potentially providing a path with larger MTU support. -- 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)

1 0

Re: jumbo frames
by Stephen Sprunk 27 Apr '01

27 Apr '01

Thus spake Tony Hain: > > Hence my original question. Packets across the GE will be 1500 > unless you are packing them. 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. > Assuming you are just passing the packets as received from the > aggregation switch, this would only happen if your router hardware > was better at managing jumbo buffer allocations than 1500B ones. > Clearly it will waste large chunks of memory, so do you have > measurements to show the actual performance increase? Routers usually have separate buffer pools for common packet sizes (or use buffer vectors), so the MTU of the interface does not noticeably affect memory usage. 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. > Tony S -- Stephen Sprunk "So long as they don't get violent, I want to CCIE #3723 let everyone say what they wish, for I myself have K5SSS always said exactly what pleased me." --Albert Einstein

2 1

OT: Apologies
by Karyn Ulriksen 27 Apr '01

27 Apr '01

Wasn't aware of the charter about posting positions on NANOG. Never saw anything about it and didn't read the charter (or knew that a formal one existed). Color me chastised and apologetic. I figured if I post this apology, maybe some else who didn't know about it will learn. It was nicely pointed out that if recruiting was pursued at NANOG, that our companies wouldn't send us. Good point. Apologies all around. --------------------------------------------------------------------- Best regards, Karyn Ulriksen Network Operations Manager SiteStream, A VitalStream Company 1 Jenner, Suite 100 Irvine, California 92618 USA Phone: (949) 743-2000 email: kulriksen(a)vitalstream.com URL: http://www.vitalstream.com ===========================================

1 0

Re: Compatible Systems Spare Parts ?
by SMcGrath＠dhhs.state.nh.us 27 Apr '01

27 Apr '01

Go to www.mouser.com Mouser Electronics and/or call them on the phone as that is a standard voltage wall wart other sources are Digi-key and Arrow Electronics

1 0