- Test - lists.nanog.org

Qwest NOC/Peering
by German Martinez 15 Apr '02

15 Apr '02

Somebody from Qwest NOC that can contact me off-line. Thanks German

1 0

RE: Korean server security?
by Marc Pierrat 15 Apr '02

15 Apr '02

Story here: http://story.news.yahoo.com/news?tmpl=story&cid=70&ncid=738&e=6&u=/cn/20020… Rules here: http://www.woksdome.org ---------- Original Message ---------------------------------- From: "Niedens, Travis" <tniedens(a)ebay.com> Date: Mon, 15 Apr 2002 11:58:15 -0700 > >A URL for the info would be nice :) > >Travis > >-----Original Message----- >From: Bruce Williams [mailto:brucewms@pacbell.net] >Sent: Monday, April 15, 2002 12:01 PM >To: Nanog (E-mail) >Subject: Korean server security? > > > >"April 15 - A Korean company is offering $100,000 in a 48-hour hacking >competition, to be run this week. Korea Digital Works (KDWorks) will launch >the competition, which will involve gaining root access to a server, on >April 16 at 11 a.m. Korean Standard Time." > > >Bruce Willians >Anything not worth doing is not worth doing well - Elias Schwartz > >

1 0

RE: Korean server security?
by Niedens, Travis 15 Apr '02

15 Apr '02

A URL for the info would be nice :) Travis -----Original Message----- From: Bruce Williams [mailto:brucewms@pacbell.net] Sent: Monday, April 15, 2002 12:01 PM To: Nanog (E-mail) Subject: Korean server security? "April 15 - A Korean company is offering $100,000 in a 48-hour hacking competition, to be run this week. Korea Digital Works (KDWorks) will launch the competition, which will involve gaining root access to a server, on April 16 at 11 a.m. Korean Standard Time." Bruce Willians Anything not worth doing is not worth doing well - Elias Schwartz

2 1

Korean server security?
by Bruce Williams 15 Apr '02

15 Apr '02

"April 15 A Korean company is offering $100,000 in a 48-hour hacking competition, to be run this week. Korea Digital Works (KDWorks) will launch the competition, which will involve gaining root access to a server, on April 16 at 11 a.m. Korean Standard Time." Bruce Willians Anything not worth doing is not worth doing well - Elias Schwartz

1 0

RE: UUNET service
by Bradley Corner 15 Apr '02

15 Apr '02

Thanks for all the 'wonderful' input. I guess most of you feel that the attitude of UUNET is appropriate. When I read responses on NANOG I am utterly surprised by the total lack of professionalism. I have always prided myself on my education and experience and my Professional attitude towards my peers. I guess I am just being naive. I do agree that the problem is with one of UUNET's customers. I, however, think that UUNET should proactively call there customer to resolve network issues. When I purchase services from a network provider one of my conditions is that they monitor my connection to them and report to me issues that could affect my connection. In fact I feel that they should notify me of problems that persist longer than five minutes. Otherwise my business is affected in an adverse way. Therefore, I feel that they should simply have asked who the problem was with. I would have told them and sent them a traceroute (I feel that more info is better info, my opinion, take it with a grain of salt if you wish.) and they simply would have said 'thank you'. Bradley Corner Northeast Florida Multiple Listing Service, Inc. 7801 Deecreek Club Rd Ste 1 Jacksonville FL 32217 (904) 394-9494 -----Original Message----- From: Bradley Corner [mailto:bac@nefmls.com] Sent: Friday, April 12, 2002 4:05 PM To: (nanog(a)merit.edu) Subject: UUNET service I tried to notify UUNET at their 800-900-0241 number that there was a loop in their network. They told me that if I didnt have an account with them they were not interested in any information that I may have had for them. I stated that I was just calling so that they could pass the information onto an engineer. He repeated himself saying if you do not have an account with us I will not do anything with the information. I guess they think they run the internet and us small ISPs couldnt possibly know anything... In case someone at UUNET reads this here is the traceroute. ================================================== === VisualRoute report on 12-Apr-02 3:04:18 PM === ================================================== Report for online.mmsi-usa.com [162.33.138.132] Analysis: The routing loop (65.195.230.218 / 162.33.130.4 / 162.33.128.249 / 205.197.182.201 / 162.33.138.129 / 65.195.230.217) starting in hops 12-17 is not allowing IP packets to get to their destination. ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------- | Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network | ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------- | 0 | | 10.100.15.40 | BRADLEY.nefmls.com | ... | | | | (private use) | | 1 | | 209.12.49.1 | - | ?Jacksonville, FL 32256 | | 1 | x | Northeast Florida MLS | | 2 | | 206.222.124.121 | - | ?Herndon, VA 20165 | | 3 | x | e.spire Communications, Inc. | | 3 | | 206.222.126.77 | washing2-dc-a5-0-0-10.rt.espire.net | - | | 27 | x-- | e.spire Communications, Inc. | | 4 | | 206.222.127.118 | reston-va-1-pos0-0-0.rt.espire.net | - | | 37 | x--- | e.spire Communications, Inc. | | 5 | | 198.32.187.97 | mae-east-level3.com | Vienna, VA, USA | | 133 | --x- | Exchange Point Blocks | | 6 | | 64.159.18.98 | ae0-54.mp2.Washington1.Level3.net | Washington, DC, USA | -05:00 | 137 | -x--- | Level 3 Communications, Inc. | | 7 | | 64.159.0.110 | so-0-0-0.mp1.Philadelphia1.Level3.net | Philadelphia, PA, USA | -05:00 | 147 | -x------ | Level 3 Communications, Inc. | | 8 | | 64.159.0.150 | gige9-0.hsipaccess2.Philadelphia1.Level3.net | Philadelphia, PA, USA | -05:00 | 137 | -x---- | Level 3 Communications, Inc. | | 9 | | 63.208.101.158 | unknown.Level3.net | - | | 147 | -x------- | Level 3 Communications, Inc. | | 10 | | 162.33.162.25 | 401n--30th-st--phily.coretel.net | ?Annapolis, MD 21401 | | 139 | --x---- | Core Communications, Inc. | | 11 | 10 | 162.33.162.29 | baltamtrak-p.highway.coretel.net | ?Annapolis, MD 21401 | | 146 | -x------ | Core Communications, Inc. | | 12 | | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 142 | -x---- | UUNET Technologies, Inc. | | 13 | | 162.33.130.4 | i97.toad.net | ?Woodbridge, NJ 07095 | | 124 | --x-- | RAM Communications Consultants, Inc. | | 14 | | 162.33.128.249 | tiara-2-balto.ds1.toad.net | ?Woodbridge, NJ 07095 | | 134 | -x---- | RAM Communications Consultants, Inc. | | 15 | | 205.197.182.201 | max2.toad.net | ?Severna Park, MD 21146 | | 146 | -x-- | ToadNet, Inc. | | 16 | | 162.33.138.129 | mmsi-cpe.dsllan.toad.net | ?Woodbridge, NJ 07095 | | 198 | -x--- | RAM Communications Consultants, Inc. | | 17 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 147 | x-- | UUNET Technologies, Inc. | | 18 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 154 | -x---- | UUNET Technologies, Inc. | | 19 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 154 | -x-- | UUNET Technologies, Inc. | | 20 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 170 | --x--- | UUNET Technologies, Inc. | | 21 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 131 | -x-- | UUNET Technologies, Inc. | | 22 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 150 | -x--- | UUNET Technologies, Inc. | | 23 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 159 | -x- | UUNET Technologies, Inc. | | 24 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 171 | -x--- | UUNET Technologies, Inc. | | 25 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 169 | -x- | UUNET Technologies, Inc. | | 26 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 188 | -x---- | UUNET Technologies, Inc. | | 27 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 169 | x-- | UUNET Technologies, Inc. | | 28 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 191 | x----- | UUNET Technologies, Inc. | | 29 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 179 | x--- | UUNET Technologies, Inc. | | 30 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 188 | -x---- | UUNET Technologies, Inc. | | 31 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 179 | -x-- | UUNET Technologies, Inc. | | 32 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 163 | x | UUNET Technologies, Inc. | | 33 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 184 | -x- | UUNET Technologies, Inc. | | 34 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 168 | -x | UUNET Technologies, Inc. | | 35 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 166 | -x | UUNET Technologies, Inc. | | 36 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 185 | -x- | UUNET Technologies, Inc. | | 37 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 161 | -x | UUNET Technologies, Inc. | | 38 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 210 | --x | UUNET Technologies, Inc. | | 39 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 152 | -x | UUNET Technologies, Inc. | | 40 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 167 | -x | UUNET Technologies, Inc. | | 41 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 176 | -x | UUNET Technologies, Inc. | | 42 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 164 | x | UUNET Technologies, Inc. | | 43 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 173 | x | UUNET Technologies, Inc. | | 44 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 158 | -x | UUNET Technologies, Inc. | | 45 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 168 | x | UUNET Technologies, Inc. | | 46 | 50 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 166 | x | UUNET Technologies, Inc. | | 47 | 50 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 159 | x | UUNET Technologies, Inc. | | 48 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 140 | x- | UUNET Technologies, Inc. | | 49 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 145 | x- | UUNET Technologies, Inc. | | 50 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 170 | -x | UUNET Technologies, Inc. | | 51 | 70 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 137 | x- | UUNET Technologies, Inc. | | 52 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 133 | x- | UUNET Technologies, Inc. | | 53 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 142 | x- | UUNET Technologies, Inc. | | 54 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 147 | x- | UUNET Technologies, Inc. | | 55 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 143 | x- | UUNET Technologies, Inc. | | 56 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 156 | -x | UUNET Technologies, Inc. | | 57 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 167 | -x | UUNET Technologies, Inc. | | 58 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 167 | -x | UUNET Technologies, Inc. | | 59 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 170 | -x | UUNET Technologies, Inc. | | 60 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 174 | -x | UUNET Technologies, Inc. | | 61 | 70 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 173 | -x | UUNET Technologies, Inc. | | 62 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 178 | -x | UUNET Technologies, Inc. | | 63 | 60 | 65.195.230.217 | 500.Serial2-11.GW4.BWI1.ALTER.NET | Baltimore, MD, USA | -05:00 | 186 | -x | UUNET Technologies, Inc. | | 64 | 60 | 65.195.230.218 | core62007-gw.customer.alter.net | - | | 183 | x- | UUNET Technologies, Inc. | | ... | | | | | | | | | | ? | | 162.33.138.132 | online.mmsi-usa.com | ?Woodbridge, NJ 07095 | | | | RAM Communications Consultants, Inc. | ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------- Roundtrip time to 65.195.230.218, average = 183ms, min = 152ms, max = 210ms -- 12-Apr-02 3:04:18 PM Bradley Corner Northeast Florida Multiple Listing Service, Inc. 7801 Deecreek Club Rd Ste 1 Jacksonville FL 32217 (904) 394-9494

3 2

RE: UUNET service
by Turpin, Mark 15 Apr '02

15 Apr '02

Bradley, I believe you received the appropriate reaction. What I don't agree with is your reaction to the feedback. Every person response addressed the issue, not you as an individual. You however post this, and attack others' professionalism? tsk tsk. Perhaps you should review your standpoint. If you think that UU should change its policies, then call their customer service. /mt -These are my opinions, not my employer's.

1 0

Measurement of colo temp and rh
by Sean Donelan 15 Apr '02

15 Apr '02

At the Scottsdale NANOG Spring 2001 I asked for volunteers to install temperature and humidity data loggers in their colocation facilities. I wanted to determine what are "typical" colocation enviromental conditions. I was tired of people asserting all sorts of numbers as the required conditions for a colocation facility. Although I haven't received all the data loggers back (if you have one I still want it back), I have posted the data I collected on my personal web site. http://www.donelan.com/ The sample is too small to be useful, but it is data.

1 0

Sprint problems?
by David M. Ramsey 13 Apr '02

13 Apr '02

Did anyone else out there have routing and/or BGP issues with AS1239 this afternoon (Saturday 13-April, ~11:30 EST - ~15:00 EST) ?? Sprint is one of our upstreams, and for about 3 hours today some remote users were unable to reach us via our Sprint connection. We heard complaints from Road Runner and BellSouth.net DSL users, among others. Sprint's NOC claims they had no issues, but suddenly it started working as I was on the telephone explaining the situation. Nothing changed on our side. It seems to be "over" now, but I'd like some idea of what happened? Thanks for any help/insight/advice/info, David Ramsey CT Communications Charlotte, NC

2 1

RE: genuity - any good?
by Kris Foster 13 Apr '02

13 Apr '02

Quick correct, they are extended access-lists > -----Original Message----- > From: Kris Foster [mailto:Kris.Foster@telus.com] > Sent: Friday, April 12, 2002 11:02 AM > To: 'Roy'; matthew zeier; nanog(a)merit.edu > Subject: RE: genuity - any good? > > > > > reasonable route for your prefixes. According to one of > > their top people, > > prefix-lists were unreliable new technology. We gave up and > > canceled the > > circuit. > > > > Genuity does use prefix lists (at least now). And, in my > experiences with > them is extremely fast in their turn around time to update these. > > Kris > >

3 2

Re: packet reordering at exchange points
by Peter Galbavy 13 Apr '02

13 Apr '02

> Gotta go with the old head scratch on that one... > > Imagine the packet zipping down a wire. It hits a router. It slows > down. Why? Because (until very recently) wire-speed != processing > speed != backplane speed... This is called 'blocking'. The packet > has to wait somewhere while the prior packet is being processed > and fed through the backplane. > > Very recently vendors started offloading tasks from a single processor > to sub-processors and ASICs in a more distributed manner. This has led > to routers that are faster than the wire (in contrast to the above > stated routers that were slower than the wire). In this situation, > buffering allows a greater port density: that is to say, more > channels at a slower speed (the speed of the wire) rather than > less channels at a higher speed (faster than the wire). Apart from the fact that I have been building these (PC/Sparc based) routers since the early '90s is neither here nor there. My point in general was to actualy try to make people explain why there is a 'marketing' relationship between the size of buffers and a magical bandwidth x delay product of (normally) line rate x one second. I fully understand (in case it appeared otherwise) the issues of interface contention when aggregating traffic and also the need for buffering in QoS implementations, but the perceived wisdom of 'you must have at least one seconds buffer on each *interface*' still seems very shoddy and marketing driven. Still haven't heard it (a good reason), but then again I haven't gone to read Van Jacobson's paper that was referenced in an earlier reply. And that paper probably makes too good a point and bears no relation to the marketing drivel we have been getting for many years. BTW The faster than line rate / slower than line rate forwarding engine stuff is an ongoing and iterative thing that has been the simple result of capacity growth and in turn a has spurred the development of each new generation of router - just like any growth industry - and this will continue until we run out of electrons and photons and god-knows-what-else to move around. Peter

1 0