- NANOG - lists.nanog.org

Earthquake in Northern California
by Dennis Dayman 28 Sep '04

28 Sep '04

6.0 and we have had 47 small ones since the larger one... 160 miles south of SFO airport... Police and fire are reporting broken pipes and damage to streets. No idea about internet access... http://quake.wr.usgs.gov/recenteqs/Maps/120-36.htm -Dennis

3 2

Re: Earthquake in Northern California
by Aviva Garrett 28 Sep '04

28 Sep '04

Hi Dennis, It looks like the epicenter is near Parkfield. Where are you? Thanks, ..Aviva In message <101B331C5846(a)ddsob.com>you write: > > 6.0 and we have had 47 small ones since the larger one... > > 160 miles south of SFO airport... > > Police and fire are reporting broken pipes and damage to streets. No idea > about internet access... > > http://quake.wr.usgs.gov/recenteqs/Maps/120-36.htm > > -Dennis

2 1

RE: Website contact for www.cisco.com
by Burton, Chris 28 Sep '04

28 Sep '04

All very true; but I prefer take away from everything complicated and make it simple (This is my opinion, YMMV). Since nothing in my environment has changed, no broken equipment or software issue, and all the routes were correct (including CEF/dCEF) and I was able to access Cisco's site from several other IP address from my network as well as outside networks I made a logical assumption (or at least I think it was logical) that it was "possible" that Cisco blocking this one particular /32. I still do not know the answer to this question as by the time Cisco replied to me with a canned answer access to Cisco's website from that IP address was working again. Chris Burton Network Engineer Walt Disney Internet Group - Network Services The information contained in this e-mail message is confidential, intended only for the use of the individual or entity named above. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this e-mail in error, please contact Walt Disney Internet Group at 206-664-4000. -----Original Message----- From: Petri Helenius [mailto:pete@he.iki.fi] Sent: Sunday, September 26, 2004 1:53 PM To: joe mcguckin Cc: Burton, Chris; crist.clark(a)globalstar.com; Temkin, David; NANOG Subject: Re: Website contact for www.cisco.com joe mcguckin wrote: >Or CEF/DCEF if a linecard 'loses' a forwarding entry. > > > Would that affect just one /32 out of a /22 if the subnet is not directly connected? (it probably would if you run some kind of ACL's that require flow state to be retained, but other than that, it should not) Obviously load balancers count as content switching devices which can also cause random brokenness. Pete >On 9/26/04 1:03 PM, "Petri Helenius" <pete(a)he.iki.fi> wrote: > > > >>Burton, Chris wrote: >> >> >> >>>I also ran into this problem yesterday, I contacted Cisco and >>>they said that they were not block any of my addresses or ranges which I >>>found to be strange since from what I could tell out of an entire /22 >>>only one IP address was affected. As of around 0500 PDT this morning I >>>was able to access Cisco's website again though. >>> >>> >>> >>> >>> >>"Content switching", when partially broken, can do fancy effects. >> >>Pete >> >> >> > > >

2 1

IETF anti-spam MARID group disbands
by Hank Nussbacher 28 Sep '04

28 Sep '04

http://www.nwfusion.com/news/2004/092704ietfspam.html See spam at 11:00 o'clock for further details. -Hank

2 2

Fw: [IP] Senate Hearing on ICANN Set for Thursday
by Matthew McGehrin 27 Sep '04

27 Sep '04

----- Original Message ----- Date: September 27, 2004 3:18:34 PM EDT http://commerce.senate.gov/hearings/witnesslist.cfm?id=1324 ICANN Oversight and Security of Internet Root Servers and the Domain Name System (DNS) Communications Hearing Thursday, September 30 2004 - 2:30 PM - SR - 253 Webcast: Click here to view a live webcast of this hearing. Description: Members will hear testimony examining the Internet Corporation for Assigned Names and Numbers (ICANN), international cooperation in management and governance of the Domain Name Syatem (DNS), and the security of the Internet's root servers and the DNS. 508 Dirksen Senate Office Bldg | Washington, DC 20510-6125 | Tel: 202-224-5115 Privacy Policy

3 2

Bogus Root DNS server Traffic.
by Jason Giglio 27 Sep '04

27 Sep '04

Hello, This bug is in SuSe, Debian, every version of Red Hat I tested. tcpdump -nl -i any -s 2048 dst port 53 ssh user@host 14:53:30.239173 65.114.174.99.32778 > 205.171.3.65.domain: 64500+ AAAA? host.domain.com. (46) (DF) 14:53:30.267398 65.114.174.99.32778 > 205.171.3.65.domain: 64501+ AAAA? host. (26) (DF) 14:53:30.286020 65.114.174.99.32778 > 205.171.3.65.domain: 64502+ A? host.domain.com. (46) (DF) That middle query is causing bogus root DNS server traffic every time someone sshs to an unqualified hostname within their LAN. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131610 SSH people won't take responsibility for this bug. The Fedora people won't take responsibility for this bug. I'm sick of trying to report this bug, so here it is. I figured the administrators of root DNS servers should know about this, which is why I copied to NANOG. Who knows how much bogus traffic this issue is causing. My guess is lots. -- Jason Giglio IT Coordinator Smyth Bedford, VA, USA Phone: 540-586-2311x113

3 2

Script to parse IANA Protocol-Numbers
by Dan Lockwood 27 Sep '04

27 Sep '04

I don't suppose that anyone has a script that they use to parse IANAs Protocol-Numbers and Port-Numbers text files? I have been trying to write my own but the docs are not very well formatted. Thanks, Dan

1 0

WSJ article on Ivan's Telecom Impacts
by sgorman1＠gmu.edu 27 Sep '04

27 Sep '04

Fleshes out some of Sean's earlier statistics: Storms Cause Greater Outages In New Fiber-Optic Networks As BellSouth Races to Recover By PETER GRANT Staff Reporter of THE WALL STREET JOURNAL September 17, 2004; Page B1 CHARLOTTE, N.C. -- Ron Royster stepped out yesterday for only a few minutes from BellSouth Corp.'s command center here, where technicians closely monitor the havoc Hurricane Ivan is wreaking on its phone network. But as soon as Mr. Royster, the center's director, returned, he could tell conditions had deteriorated. It was midmorning. Until then, Ivan's impact had been manageable. But an alarm in the Network Reliability Center indicated a fire may have erupted at a central phone office in Marion, Ala. Another office reported that its backup electrical generator had stopped working, forcing it to go on batteries. Most worrisome, the storm had severed fiber-optic lines -- the lifeline of modern communications networks -- in Pensacola, Fla., and on the Alabama-Mississippi state line. "Things went downhill pretty fast," said Mr. Royster, who hasn't had a day off since Aug. 29 as the Southeast has been pounded by three back-to-back hurricanes. It was round one in Ivan vs. BellSouth, which provides local phone service to tens of millions of people in nine Southeastern states -- all in Ivan's path. And it isn't exactly a fair fight. BellSouth's disaster-recovery resources already have been stretched thin by the two hurricanes that hit Florida, Charley and Frances. Furthermore, because of fiber optics and other new technologies BellSouth has added to upgrade its networks over the past decade, the systems are, ironically, more vulnerable to disasters. The key problem: Many phone networks that used to rely on their own electricity now depend partly on commercial power. That means that when the utility company's power lines go down, the phones may go down, too. Like other regional Bell companies, BellSouth prides itself on its ability to maintain service during disasters and restore it quickly when it fails. Phone executives love to tell stories of the numerous times that people have been able to use their telephones during power failures. These stories are about more than bragging rights. In today's fiercely competitive telecommunications market, dealing with adversity is a major selling point. Phone companies have been quick to point out that many of the new phone services offered by some cable companies and others using Internet technology often go out in power outages. Now, with their new local fiber networks, phone companies are more vulnerable on this score. To improve reliability, BellSouth in 1995 consolidated 42 recovery facilities into two, one in Charlotte and the other in Nashville. The recent spate of hurricanes has put those centers through their toughest test yet. "It's been pretty intense," Mr. Royster says. "First Charlie, then Frances and now this." Phone companies had unparalleled reliability records when their networks consisted of copper wires that stretched from central offices to homes and workplaces with nothing in between. The copper lines not only carry calls but low-voltage electrical power as well. That is why phones generally have continued to work even when the local power company's lines went out. In addition, the central offices have their own backup power supplies that kick in during power outages. As a result, most service failures have been due to lines that were downed by fallen trees or car accidents. But in the past decade, phone companies added fiber optics and devices known as "digital loop carriers," small file-cabinet-sized pieces of equipment, between central offices and homes. The devices have greatly boosted the capacity of the lines, cutting costs and making new services including high-speed Internet connections possible. The digital-loop devices also run on electricity from the local power company's network, however. While they are equipped with batteries, that backup lasts only about eight hours -- and less if there's a lot of Internet traffic over the network. Once the batteries run out, phone and Internet service goes dead unless a backup generator can be installed. While some digital-loop carriers have a generator, BellSouth says it would be economically unfeasible to put a generator at all 65,000 of them. BellSouth officials say they are exploring ways to make the batteries last longer. "We constantly look for technological advances that would allow us to have a better safety margin," says Richard Burns, the vice president responsible for BellSouth's network-operations support. "But it's only in these huge, widespread natural disasters that commercial power failures last long enough, and are widespread enough, to have a significant impact." Initially, Hurricane Frances knocked out phone service for 775,000 BellSouth subscribers -- 13% of its Florida customer base. Most of that was due to power losses, not from downed lines. By contrast, only 350,000 customers lost service at the height of Hurricane Andrew in 1992, before many of the BellSouth networks were upgraded. A large part of the difference is because Andrew hit only two counties, while Frances hit all of BellSouth's Florida operations. But Frances's larger impact also was due to the system's new susceptibility to power outages, BellSouth executives say. Wireless phone service was also affected. While cellphone towers are built to withstand hurricane-force winds -- and most did -- they use power to transmit their signals. And in areas where the power went out, the towers' backup power, a combination of generators and batteries, also sometimes failed. In Mobile, Ala., 38% of Cingular Wireless's coverage area lost service, in Biloxi, Miss., 32% lost service, while in Birmingham, Ala., about 23% lost service, says Calie Shackleford, a Cingular spokeswoman. Cingular is owned by BellSouth and SBC Communications Corp. Power was very much on the minds of the 50 or so technicians who manned the BellSouth disaster recovery center in Charlotte yesterday. They watched as the number of central offices on backup generators climbed to 118 at midafternoon, from 63 at about noon. Even more worrisome were those that were relying on batteries, meaning their generators had failed and they had about eight hours of juice left. If one died, thousands of homes and offices would lose their phone service. Fortunately, all the central offices that switched to batteries did so for only a few minutes while generators were refueled. During one tense moment, Wayne Bell, a technician, stared at a screen that indicated that one generator didn't start after being refueled. That only lasted for a moment, though. "They got it back," he said, clasping his hands in a prayer motion over his head and looking up in thanks. But other problems erupted. On other screens technicians monitored the number of digital-loop carriers that were on batteries and the number that had failed, meaning their batteries had died. By midafternoon, 397 had failed and 1,193 were running on batteries. Each one conducts service to as many as 500 households. The ones that fail won't be fixed until the commercial power goes back on or crews attach backup generators. As Ivan moved north, BellSouth officials moved forward quickly with their recovery plan for areas hit first. A fleet of trucks with 600 emergency generators that had been parked at a staging area south of Valdosta, Ga., began to move out. By noon, 11 tankers with diesel and unleaded gas -- to fuel the generators and repair trucks -- were rolling from Jasper, Fla., to three sites in Alabama. By midafternoon, 114 digital-loop carriers were working on generators. As of late afternoon yesterday, 350,600 customers had lost their phone service due to Hurricane Ivan -- most of that due to the loss of local power. BellSouth executives say that the recovery process still under way in Florida didn't have a major impact on the company's ability to move resources into Ivan's disaster zone. All of the company's 1,100 generators were used to restore phone service knocked out by Frances. But by the time Ivan hit, hundreds of them had been freed up because commercial power had been restored. As of yesterday, BellSouth had reactivated service for all but 50,900 of the customers whose phones went out during Frances. Write to Peter Grant at peter.grant(a)wsj.com <http://online.wsj.com/article/0,,SB109537424767920279,00.html> ------------------------------------- You are subscribed as ucfnmad(a)ucl.ac.uk To manage your subscription, go to http://v2.listbox.com/member/?listname=ip

1 0

RE: Website contact for www.cisco.com
by Burton, Chris 26 Sep '04

26 Sep '04

I also ran into this problem yesterday, I contacted Cisco and they said that they were not block any of my addresses or ranges which I found to be strange since from what I could tell out of an entire /22 only one IP address was affected. As of around 0500 PDT this morning I was able to access Cisco's website again though. Chris Burton Network Engineer Walt Disney Internet Group - Network Services The information contained in this e-mail message is confidential, intended only for the use of the individual or entity named above. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this e-mail in error, please contact Walt Disney Internet Group at 206-664-4000. -----Original Message----- From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Crist Clark Sent: Thursday, September 23, 2004 9:47 AM To: Temkin, David Cc: nanog Subject: Re: Website contact for www.cisco.com Temkin, David wrote: > Can someone responsible for either security or operations of > www.cisco.com please contact me? We are seeing an issue where you may > be blocking one of our source IP addresses from accessing the website. Hmmm... Weird. We're having a similar issue. If you are at liberty to, could you please publicly or privately let me know what's going on here and whether it is a bug or feature? -- Crist J. Clark crist.clark(a)globalstar.com Globalstar Communications (408) 933-4387

3 3

Graphical displays of latency/packet loss for Top Internet backbones
by Don Lundquist 26 Sep '04

26 Sep '04

Does anyone have a list of a few sites on the Internet which display graphical and/or statistical information on packet loss and latency for major Internet providers? Specifically I am looking for comparisons for major providers such as AT&T/MCI/Qwest/Level3/Savvis etc... Thanks in advance, Don Lundquist Peak 10, Inc.

6 6