May 2004 - Test - lists.nanog.org

Reminder: PGP Key Signing in San Francisco
by Joe Abley 23 May '04

23 May '04

There will be a PGP Key Signing Party at the NANOG 31 meeting in San Francisco, which will also include a very brief tutorial on what key signing is all about, which I hope will make things go even more smoothly than usual :-) When: Monday 24 May 2004, 9pm Where: Italian Room Foyer, just outside the Colonial Room Before 6pm on the day of the keysigning, you need to mail me with your public keys, or (preferably) add your public keys directly to the NANOG 31 keyring using the following URL: http://www.biglumber.com/x/web?keyring=3554 For full details, see <http://www.nanog.org/pgp.html>, or drop me a note. Joe

1 0

Network Solutions Contact
by Williams, Ken 22 May '04

22 May '04

Can someone from network solutions please contact me ASAP off-list. Ken Williams Network Security Engineer Sony Pictures Digital Entertainment

1 0

information about equiptment
by Ingo 22 May '04

22 May '04

Hi perhaps someone could tell me something about corecess equiptment. Kind regards, Ingo

4 3

Road Runner contact needed
by Mark Jones 21 May '04

21 May '04

Does anyone have a Road Runner contact, or can a RR.com representative contact me offlist? Thanks. I've had no response (other than auto-ack) from removal(a)security.rr.com or similar channels for more than a month. Mark A Jones Systems Administrator netINS, Inc. http://netins.net (515) 830-0698 markjo(a)netins.net

2 2

Dell power connect switches.
by Joel Perez 21 May '04

21 May '04

Good afternoon, We are planning to deploy several Dell PowerConnect 3324, 3348 and 6024 switches on our network. We currently have between 200-300 users and servers that these switches will service. We are also planning to add about 300-400 more users in the next 2-3 mos. 85% of the users are for our call center where they all use Terminal clients and connect to W2K TS. The rest is regular staff and our application servers. Can anyone tell me any good/bad points about them? I originally proposed using RiverStone as L2 switches but price was a factor in our decision to go with Dell. That is my main concern at this point. The Dell switches are very cheap compared to other L2 switches out there. Will this be a case of "you get what you pay for" or are they really good performing units? I really have not been able to find any lists or other sources with comments on these units. I'd appreciate any info you guys might have. Regards, ------------------------------------- Joel Perez | Network Engineer jperez(a)uspgi.com | www.USPGI.com -------------------------------------

6 6

issues with AOL Time Warner
by Niaz, Wajahat 21 May '04

21 May '04

Is anyone seeing issues with AOL CNN ?

5 4

RE: issues with AOL Time Warner
by Owens, Loren 21 May '04

21 May '04

South East (Central Florida specifically) is seeing major problems as well. Cfl.rr.com has stopped routing through ATDN all together and is now going out through bbnplanet and level3. Shane -----Original Message----- From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Gabriel Sent: Friday, May 21, 2004 4:18 PM Cc: 'nanog(a)merit.edu' Subject: Re: issues with AOL Time Warner Same here... We saw all our AIM clients go down for about five minutes. Traceroutes showed lots of apparent troubles in atdn.net, also coming from the west coast. >>Is anyone seeing issues with AOL CNN ? -- Gabriel Cain www.dialupusa.net Senior Systems Administrator gabriel(a)dialupusa.net PGP fingerprint: C0B4 C6BF 13F5 69D1 3E6B CD7C D4C8 2EA4 2B08 1C6D Technology for the sake of business.

2 1

Re: Qwest Utah fiber cut
by sgorman1＠gmu.edu 21 May '04

21 May '04

Now it makes sense - we were missing the fiber route along US HWY 89. We have data on their nation wide OC-192 network and metro fiber, but figured there was something we were missing. Also explains why other providers were not affected - it must be a unique right of way. Appreciate the help. sean ----- Original Message ----- From: "Aaron D. Gifford" <agifford(a)infowest.com> Date: Friday, May 21, 2004 3:39 pm Subject: Re: Qwest Utah fiber cut > sgorman1(a)gmu.edu wrote: > > > > I was hoping someone might be able to shed some light on the > Utah cut. > > > > The news report said that the cut happened near Monroe Utah, > which is several miles off of I 70. Yet the cities that were > reported effected included St. George, Cedar City, and Salt Lake, > which all are adjacent to I 15. > > > > The puzzling part is that in our "best effort" database Qwest > does not have long haul fiber running down I 70, but it does have > a lot of fiber running down I 15. There is Qwest fiber on I 15, > all the cities affected are on I 15 yet the reported cut was near > Monroe off of I 70. > > > > I'm not familiar with Utah geogrpahy and this comes simply from > looking at our maps. Just trying to sort out the seeming > discrepency. Any insight? > > > <<snip>> > > According to this map at > http://atlas.utah.gov/staticmapbin/urta_network.gif the Qwest > fiber in > question runs southward along I-15 from Salt Lake City, through > Utah > Valley (Provo, Utah, etc.) to Nephi, Utah, then turns eastward > away from > the I-15 corridor until it reaches highway 89, which it follows > southward parallel to I-15 but one mountain range to the east. It > continues southward along 89 until I-17, then follows I-70 until > it ends > where it meets I-15, where the fiber continues southward along I- > 15 to > St. George, Utah (where I'm at), the end-of-the-one-lane-dead-end > road. > This route would be consistent with the news reports saying the > cut was > near Monroe, Utah or near Richfield, Utah. > > Such a route would agree with the telecommunication territories as > mapped out at http://atlas.utah.gov/telcom/viewer.htm which shows > Qwest > territories along I-15 except for the central Utah areas where > Qwest's > fiber follows highway 89 (which area IS a Qwest territory). > > While the news articles only mention that cellular, long distance, > 911, > and internet services were affected but local calling was not, > this is > not entirely true. As one affected by the cut, I can attest that > the > resulting additional load on the local switches (perhaps as people > were > calling each other to find out what was happening -- I don't know) > made > many phones utterly useless, including my own. > > A similar cut happened some years go around Springville, Utah. I > had > thought that Quest had since worked with local public safety folks > to > set up emergency 911 services that rely on the fiber to > automatically > fall-over to Qwest's older and lower bandwidth microwave network. > Apparently that plan fell by the wayside, or else I misheard it in > the > first place. > > Local area public safety personnel resorted to using the Emergency > Broadcast System over radio (television translators were also > affected > as many of them receive their video feeds over that same fiber) to > tell > citizens the direct-dial numbers, and in cases (like my home > phone) > where the phone system wasn't working at all (probably due to > overload), > local public safety folks told people to go to their nearest fire > station for emergency help. > > Messages over local radio indicated that the outage not only > affected > southwestern Utah counties (almost 1/3 of the state by area), but > Lincoln County, Nevada, and Mohave and Coconino Counties in > Arizona > (north of the Grand Canyon). I don't know how accurate that > message was. > > Aaron out. > >

2 1

New IPv6 Allocation to ARIN
by Doug Barton 21 May '04

21 May '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is to inform you that the IANA has allocated the following IPv6 /23 block to ARIN: 2001:3C00::/23 ARIN For a full list of IANA IPv6 allocations please see: http://www.iana.org/assignments/ipv6-tla-assignments - -- Doug Barton General Manager, Internet Assigned Numbers Authority -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFArmPzwtDPyTesBYwRAlMcAJ0QbmVVh32h0UX7CLfeum6I8qGB+wCfRmOi XD6hR9kQpwWB/3sIMqrLhLk= =RHGH -----END PGP SIGNATURE-----

1 0

Re: handling ddos attacks
by Paul Vixie 21 May '04

21 May '04

> Ok, I 'll buy that right now; we have a DDoS Attack on our core nameservers > from 66.165.10.24. Where do we start, do I call the police in Bellingham or > Washington State Police. We have blocked their ips but, we know they will > come in another way. the best thing is if you call the FBI, or NIPC. if you call your local FBI field office and say you're experiencing a cyberattack and could they give you the number for NIPC then it'll probably produce the results you want, even if NIPC has been renamed one or more times since i last talked to them, or if this old functionality within FBI is now handled by DHS, or both.

4 3