- NANOG - lists.nanog.org

AT&T DSNOC status
by Rob M VanHooren 16 Apr '98

16 Apr '98

FYI, status on AT&T F/R can be had at +1 732 885-7791, option 2. (But I bet you already knew that...) --R. PS: Interesting, it also lists med-sev tickets on 4 nodes, effective at exactly midnight tonight. All CA-80 gear, too (Cisco/Strata?). If you can decipher Bellcore's CLLI/CLEI conventions from memory better than I can, my guess is you'll find the original nodes that freaked out. Anybody around have a copy of Bellcore's DERG, LIDB-LARG, GEL, or other TRA tables on CD-ROM they'll let me have a peek through? I'd buy them myself, but I'm too poor (and too cheap - heheheh). ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-.._..-*~ Rob M. VanHooren - Chief Plumber, +1 519 679-1155 x33 Packet Pusher, and Resident Mad Scientist(tm) Alarms to 646-4724 Network Engineering Services 171 Queens Avenue, Suite 320 Linkdata Communications Inc. London, CANADA

1 0

NANOG 13 REGISTRATION
by Pam Ciesla 15 Apr '98

15 Apr '98

Our Registration Webpage was acting alittle strange, we have since corrected the problem. Please check the Attendee list if you have registered and are not on the list please re-register. Thanks, sorry for the inconvenience. Attendee list update at 10:30AM EDT 4/15. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Pam Ciesla 734-936-0172 - phone Merit Network, Inc. 734-647-3185 - fax University of Michigan 4251 Plymouth Road Bldg. I, Suite C Ann Arbor, MI 48105-2785 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

1 0

whois server for CA domain (fwd)
by Michael Dillon 15 Apr '98

15 Apr '98

-------- forwarded message --------- From John Demco: Subject: whois server for CA domain fyi.... (Might be interesting in particular to ISPs.) There is now a whois server for the CA domain available at whois.cdnnet.ca. Typical command-line usage would be something like: whois -h whois.cdnnet.ca some-name.ca I'd like to thank to Richard Sexton, Ed Hew, and others for their suggestions and help. --John

2 1

Re: SMURF amplifier block list
by sob＠academ.com 15 Apr '98

15 Apr '98

> As far as .0 and .255 addresses go, I'm no more "asking for trouble" by > using those than I'm asking for trouble by running an IRC server. They > are completely valid addresses. Perhaps those making such comments are > better at getting IP space than we are, but we need to squeeze every IP we > possibly can into use just to provide enough addresses to our customers. Actually, in the old classful days, you were probably asking for trouble to use those addresses. Today, when everyone is running fully classless IP stacks (everyone is doing that, right?), they should be usable. However, I'd personally avoid them for any host that might have to get regular access to other parts of the Internet (those parts that might still be running really old stacks). You can probably insure they will work inside your network, but you may not be able to guarantee they will work elsewhere. -- Stan | Academ Consulting Services |internet: sob(a)academ.com Olan | For more info on academ, see this |uucp: mcsun!academ!sob Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.

1 0

Re: SMURF amplifier block list - READ THIS
by Joe Provo - Network Architect 15 Apr '98

15 Apr '98

[snip] > What we were talking about was forbidding external connections to the > class-C broadcast addresses on a net, and why that useful process made > addressing hosts on .255 boundaries A Bad Idea. You misspelled "useless process". I also think you dropped the final phrase "if you want to talk to my network." [many previous posts in previous discussion on the topic omitted here. see the archives.] Assuming someone else's topology is stupid; we have dynamic protocols to tell our gear things for good reason. you want a dynamic process? get your head out of the cisco rut: use your rbl-like bgp sessions between gated boxen that then squirt the updates into ACLs. feed these ACLs into your configuration update method (if you have one). That one was free. Cheers, Joe

1 0

Re: AT&T outage (was: the whole world disappeared)
by Sean Donelan 14 Apr '98

14 Apr '98

>Well, it's made the news, at least: > >http://www.wired.com/news/news/technology/story/11648.html >http://www.news.com/News/Item/0,4,21061,00.html?st.ne.fd.mdh AT&T has finally put some press releases up on its web page http://www.att.com. Unfortunately, the 1-800 number AT&T lists to hear the chairman's explaination is experiencing heavy calling volume, so I haven't been able to get through. The press release was delayed long enough to miss most of the deadlines for this morning's newspapers. But those reporters are sure going to be mad in tomorrow's editions. -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

3 2

Re: SMURF amplifier block list
by Jeff Weisberg 14 Apr '98

14 Apr '98

| | Then again, filtering any packets to or from x.x.x.255 would have a | similar but more profound effect. Anyone who actually uses a .255 | address for a host is asking for trouble anyways. around here, we use 'em (.0 too). 'course ARIN makes me justify my utilization before they give me more, so I try to use addresses as efficiently as possible. do others not have this constraint? --jeff ---- Dear Mr. Arin, Thank you for the addresses you gave me previously. I now need more. I have efficiently used the ones you gave me. Sort of. I skipped over addresses ending with .0 and .255. Oh, and those ending in .13 too. Thank you, Mr. Isp Guy

1 0

Re: the whole world disappeared?
by Sean Donelan 14 Apr '98

14 Apr '98

> All AT&T InterSpan North American frame services are down. Our 200 > site WAN just went dark. No ETA for repair. I'm starting to feel jinxed. Two months ago Worldcom was in the office explaining how wonderful their network was, a few days later they lost most of their west coast connectivity. Last month SPRINT was in the office explaining how wonderful their network was, that weekend the Sprint network suffers software upgrade meltdown. This afternoon AT&T was in the office explaining how wonderful their network was, and tonight the AT&T network falls over. I think the only thing saving MCI is their salesperson hasn't been able to tell me how wonderful their network is. Anyone else care to try their luck and schedule an appointment to tell me how wonderfull their network is :-) To keep Randy from yelling at me, I am working on a protocol for reporting alerting users to network and other failures. I've decided no one will implement management guidelines, so lets write some software. And someday you may even be able to configure your Cisco, Ascend, etc to grok the protocol. I think it would be a cool addition to lucky IOS release 13. -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

9 8

Re: SMURF amplifier block list
by kline＠uiuc.edu 14 Apr '98

14 Apr '98

> there have been several documented problems over the years with using > these addresses with certain OSes, and it's fairly sure that they will > continue to have problems. One can also make a reasonable case that > it's worth the administrative benefits to not use these addresses. The only subset of documented problems I'd agree with is trying to supernet class C's into larger blocks. But that wasn't what I was talking about. It's a shame that we went through so much trouble to remove classfulness and artificial byte boundaries in address space only to have them be reinserted and carried forth forever with ad hoc policy like this. I understand your point about tradeoffs of administrative benefits, but in this case it seems particularly ill-advised to promulgate brain- damage and justify it by saying "well, broken hosts didn't get fixed fast enough, so we may as well continue the tradition." /cvk

1 0

Re: backbone question
by Curt Howland 14 Apr '98

14 Apr '98

So that the backbone is never a source of problems, and the backbone network operations can point back to the LAN folks and say, "Nya nya!" > Why should the performance of a backbone network generally be higher then > that of the networks it interconnects. > > i would appreciate a reply > > thank you > > salvatore amico >

1 0