- NANOG - lists.nanog.org

The Pillsbury Doughboy vs. Engineers
by Jeff.Hodges＠kingsmountain.com 21 Jan '01

21 Jan '01

The Pillsbury Doughboy vs. Engineers http://slashdot.org/articles/01/01/20/227233.shtml Posted by timothy on Saturday January 20, @05:10PM from the who-would-you-bet-on? dept. Anonymous Coward writes: "Just when you thought things could not get more st[u]pid. Salon is reporting in this story that Pillsbury is sending cease-and-desist letters this week to universities and Sun Microsystems among others ordering engineers to stop holding what the doughboy company considers illegal "bake-offs." ... see also: Pillsbury Doughboy mauls techies http://www.salon.com/tech/log/2001/01/19/pillsbury/index.html] Structure of Protiens & DNA: Shake & Bake http://www.psc.edu/science/Hauptman/Hauptman.html

1 0

Re: nobody @home
by Dan Hollis 20 Jan '01

20 Jan '01

On Sat, 20 Jan 2001, Basil Kruglov wrote: > On Sat, Jan 20, 2001 at 02:10:18PM -0500, Jim Mercer wrote: > > i've always found the list at http://puck.nether.net/netops/nocs.cgi to be > > most helpful, including reaching noc@home. > Only when it comes to routing issues/problems, not security - > "[d]DoS-in-progress" issues. :| > 90% of those "NOCs" are help desk phone numbers, and it takes at least > good 30-60min+ to get to the real NOC/people, if ever. Youre lucky. Ive noticed an increasing trend that the NOC phone numbers listed on corporate web pages come back as disconnected/RNA, and the emails bounce "no such user". Real cute, especially when you're being ddos'd. whois data is even worse. I suspect upwards of 25% of whois contact data is worthless. -Dan

1 0

Re: nobody @home
by Daniel L. Golding 20 Jan '01

20 Jan '01

Great. Every NOC in the country has just been slashdotted, as well as this list. Some of the key suggestions posted on that fine forum include: 1) Calling the NOC (i.e. http://puck.nether.net/netops/ was posted as a link) if you have a problem as an individual user. 2) Launch DDOS attack on offending ISPs 3) Post emails to NANOG to find clueful network engineer types, to help you with your email problems. Needless to say, prepare for calls and emails from some "E1it3 Dud3Z". After all, they read it on Slashdot... :) Oh well, information wants to be free. Daniel Golding NetRail,Inc. "Better to light a candle than to curse the darkness" On Sat, 20 Jan 2001, Philippe Landau wrote: > > http://slashdot.org/article.pl?sid=01/01/19/081222&mode=thread > Contacting Network Admins Of Large Internet Companies? > > kind regards philippe, http://InternetRoot.com/ >

1 0

Re: Cisco PIX
by abt 20 Jan '01

20 Jan '01

http://www.interhack.net/pubs/fwfaq/ rc. ----- Original Message ----- From: "Dave McKay" <dave(a)sneakerz.org> To: <deen(a)slt.lk> Cc: <nanog(a)merit.edu> Sent: Saturday, January 20, 2001 5:53 AM Subject: Re: Cisco PIX > > http://www.cisco.com/warp/public/110/38.html > > deen(a)slt.lk (deen(a)slt.lk) wrote: > > > > > > Hi!! > > > > Has anybody configured the Cisco PIX F/w as a VPN. Any feelers will be welocome. > > -- > Dave McKay > dave(a)sneakerz.org > Microsoft Global Network Architect >

1 0

Sprint / C&W peering issues?
by jlewis＠lewis.org 20 Jan '01

20 Jan '01

The past few days, I've been noticing packet loss, apparently at the points where Sprint and C&W exchange traffic. Today, I emailed a note about this including the output from a few mtr's in each direction to noc(a)sprint.net, and though I got no reply, an hour or so later, I noticed packets were taking a slightly different route (apparently going through a different peering connection in a different city if you believe the hostnames) and the packet loss was gone and round trip times much better. I left the office for a bit, and now that I'm back, I see the packets are back to using the old peering connection that I can only assume must be overloaded. Anyone know what the deal is? Matt's traceroute [v0.42] orldfl-ns-1.atlantic.net Fri Jan 19 18:58:51 2001 Keys: D - Display mode R - Restart statistics Q - Quit Packets Pings Hostname %Loss Rcv Snt Last Best Avg Worst 1. orldflwcom-br-1-fe0-0.atlantic.net 0% 30 30 0 0 0 1 2. sl-gw8-orl-3-0-TS11.sprintlink.net 0% 30 30 1 0 1 1 3. sl-bb11-orl-5-2.sprintlink.net 0% 30 30 1 1 1 2 4. sl-bb21-atl-9-1.sprintlink.net 0% 30 30 11 11 11 12 5. sl-bb2-atl-0-0-0.sprintlink.net 0% 30 30 12 11 30 190 6. core3-serial2-0-0.Atlanta.cw.net 20% 24 30 37 33 37 41 7. corerouter1.Atlanta.cw.net 27% 22 30 34 33 36 50 8. acr1-loopback.Atlantaald.cw.net 20% 24 30 36 32 37 39 9. bar7-loopback.Atlantaald.cw.net 27% 22 30 48 33 37 48 10. ??? Hop 10 is a router with some packet filtering...no response is expected there. -- ---------------------------------------------------------------------- Jon Lewis *jlewis(a)lewis.org*| I route System Administrator | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________

2 1

Too big to fail?
by Sean Donelan 19 Jan '01

19 Jan '01

Remember during the last deregulation cycle. When the Savings & Loan and Bank industries were "deregulated" one open question was: are there banks considered too big to fail. The problem with that doctrine is it warps management's risk analysis. Instead of appropriate investments, management makes excessively risky decisions in an attempt to achieve short-term returns and maximize shareholder value. Is PG&E too big to fail? On Thu, 18 January 2001, "Steven M. Bellovin" wrote: > If PG&E files for bankruptcy, control of the company passes to a > federal judge. If you subscribe to the NY Times site, see > http://www.nytimes.com/2001/01/18/national/18ENER.html > Here's the first paragraph: > > LOS ANGELES, Jan. 17 - Politicians and > power company executives have bickered > for months about how best to solve > California's energy problems, but ultimately it > may come down to this: a bankruptcy court > judge may be the only person with the authority > to ask for the rate increases and cost cuts that a > growing chorus of analysts say are necessary, > but that nobody in the state has been able to > agree upon. > > > --Steve Bellovin, http://www.research.att.com/~smb

2 1

Troubles inside ALTER.NET?
by Vladimir Litovka 19 Jan '01

19 Jan '01

Hello, are there any looking glasses inside of ALTER.NET? We are currently experiencing problems accessing to icq.com, cnn.com and many others: traceroute to 205.188.5.208 (205.188.5.208), 30 hops max, 38 byte packets 1 cisco1 (212.109.32.131) 6.797 ms 39.415 ms 19.684 ms 2 cisco0.kiev.sovam.net.ua (212.109.32.138) 4.373 ms 1.936 ms 5.050 ms 3 ccr-1.Moscow.ST.NET (194.186.157.25) 147.366 ms ccr-1.Moscow.ST.NET (194.186.157.121) 230.353 ms ccr-1.Moscow.ST.NET (194.186.157.189) 146.084 ms [ ... ] 21 0.so-4-0-0.TR2.NYC9.ALTER.NET (152.63.15.182) 201.163 ms 240.414 ms 213.036 ms 22 125.at-5-0-0.TR2.DCA6.ALTER.NET (152.63.2.201) 211.353 ms 240.997 ms 247.147 ms 23 0.so-3-0-0.XR2.DCA6.ALTER.NET (152.63.11.90) 279.065 ms 245.794 ms 200.880 ms 24 184.ATM5-0.GW2.IAD2.ALTER.NET (152.63.36.221) 221.368 ms 282.156 ms 217.497 ms 25 * * * 26 * * * but traceroute from route-views.oregon-ix.net or route-server.exodus.net is ok. Looks like internal problem in ALTER.NET? traceroute above - from 212.109.32.15 Thank you. -- Vladimir Litovka <doka(a)kiev.sovam.com> | "I've seen the future and it's . Phone/Fax: +380 44 4900111 | Cisco switches!" . ICQ/none, talk/none ;) | Cat Alyst

1 0

Re: Announcement: RIPE Whois Database Version 3.0beta2 released
by Nipper, Arnold 19 Jan '01

19 Jan '01

rpsl.ripe.net doesn't seem to exist ... whois -h whois rpsl.ripe.net Daniele Arena whois: whois: Unknown host: Datei oder Verzeichnis nicht gefunden Let's have a look ... ;; ANSWER SECTION: rpsl.ripe.net. 1d23h59m55s IN CNAME reimp.ripe.net. reimp.ripe.net. 1d23h59m55s IN CNAME orange.ripe.net. orange.ripe.net. 1d23h59m55s IN A 193.0.1.239 Yeah, don't do that. Don't use CNAME to CNAME. Pls fix, Arnold ----- Original Message ----- From: "RIPE Database Announcements" <db-news(a)ripe.net> To: <lir-wg(a)ripe.net>; <db-wg(a)ripe.net>; <routing-wg(a)ripe.net>; <eng-coord(a)ripe.net>; <db-beta(a)ripe.net>; <reimp-mig-tf(a)ripe.net> Sent: Friday, January 19, 2001 2:33 PM Subject: Announcement: RIPE Whois Database Version 3.0beta2 released > > Dear All, > > This mail is to inform you that version 3.0beta2 of the RIPE Whois > Database software has been released. This is mainly a bugfix release in > respect to the "beta1" version. > > We remind you that the RIPE Database is about to change its data format, > from RIPE181 to RPSL (the Routing Policy Specification Language, see > RFC2622). This will affect all object types, including "person", "domain" > and "inetnum". > > We suggest you to start to get used to RPSL and version 3.0 . > Please check our RIPE-181 to RPSL Migration page at: > > http://www.ripe.net/rpsl/ > > You can test your skills with RPSL and the functionality of the new > beta release in the following ways: > > - Query rpsl.ripe.net at port 43. You will find there > exactly the same objects that are in whois.ripe.net, > mirrored live and in RPSL format. > > - If you have any script that runs by querying whois.ripe.net, > test it by pointing it to rpsl.ripe.net and make it > v3.0-compliant. > > - Try our CGI interface to the RPSL server: you can find it at > http://www.ripe.net/ripencc/pub-services/db/reimp/. > > - Get to know the new update path: use our "sandbox" database for > RPSL updates. Send your updates to <auto-rip(a)ripe.net> and > query the corresponding database at rpsl.ripe.net, port 4343 . > > Remember that in a few months, that's the way the RIPE Database will be > running; so the earlier you start working with it, the less likely you are > to be unpleasantly surprised later. > > For those running Near-Real-Time Mirrors of the RIPE Database, please be > advised that as soon as the RIPE Database changes its data format, you > will not be able to mirror the RIPE Database using the version 2 of the > Software, since it is not RPSL-compliant. You will have to upgrade to > version 3 to mirror the RIPE Database. Please contact <ripe-dbm(a)ripe.net> > for detailed information. > > Please note that the software is still in a "beta" phase. So we need your > feedback! If you happen to find something that looks like a bug when you > are testing the RPSL database, don't hesitate... > Send us a bug report at <dbrip(a)ripe.net> ! > > If you want to actively participate to the migration effort, you could > join the "RIP migration Task force" and let yourself be heard. Just write > to <ripe-dbm(a)ripe.net> and ask to join the Task Force. > > You can download the latest release of the source code at the following URL: > > ftp://ftp.ripe.net/ripe/dbase/reimp/ripe-dbase-3.0beta2.tar.gz > > You can also join a discussion list related to version 3.0 beta of the > RIPE Database Software. To subscribe to this list, send a message to > <majordomo(a)ripe.net> with the line: > > subscribe db-beta > > in the body of your letter. It is a moderated mailing list so some delays > in subscription are possible. > > > Regards, > > Daniele Arena > ___________________ > RIPE Database Group > RIPE NCC > >

1 0

RE: Second day of rolling blackouts starts
by Derek J. Balling 19 Jan '01

19 Jan '01

At 10:45 AM -0800 1/18/01, Roeland Meyer wrote: >What's wrong with this picture? I see the generators, holding a shotgun at >PG&E's neck, and telling the state that they'll pull the triggers if the >state doesn't come up with the dough. They're not even wearing a mask! Yet, >no one is seeing anything wrong with this and they're acting like it's >PG&E's fault. Welcome to the PRC, ... Peoples' Republic of China^WCalifornia. I pointed out to a co-worker that the "state-mandated low-rate,low-supply,high-demand" power problem was tried in most parts of the former Soviet Union... and those citizens prepare for winters by stocking up on heating supplies as they "Expect" power to go out. This was a known-failed experiment before CA tried it. But, California essentially tried the same thing... high-demand, low-rate, and (through AQMD and other fun things) low-supply. They (through doing this) convinced people that they have a "right" to expect power at below-market-value. Who can blame PG&E's suppliers for being on the "winning side" of a supply-side-economics issue? Who can blame PG&E for being handcuffed by the state's rules? The people of California can, for some reason that boggles this CA resident. But maybe that's cuz I'm not a native. It seems that the natives are all upset, and the "non-native" folks I work with tend to blame California residents themselves for voting/etc. that put the price-fixes in place. "You wanted it, you got it, see how stupid it was? Now pay the price and move on instead of whining". Seem to be in the minority here though. ;-) D (This is operational, insofar as its good advice that "if you want to have consistent power for your colo, you should consider states that don't do silly things to power companies". ;-) ) -- +---------------------+-----------------------------------------+ | dredd(a)megacity.org | "Conan! What is best in life?" | | Derek J. Balling | "To crush your enemies, see them | | | driven before you, and to hear the | | | lamentation of their women!" | +---------------------+-----------------------------------------+

7 7

Re: Too big to fail?
by Steven M. Bellovin 19 Jan '01

19 Jan '01

In message <20010118205105.A1059(a)localhost.co-nectschools.net>, Scott Brim writ es: >On Thu, Jan 18, 2001 at 04:31:58PM -0800, Sean Donelan wrote: >> >> Remember during the last deregulation cycle. When the Savings & Loan >> and Bank industries were "deregulated" one open question was: are >> there banks considered too big to fail. The problem with that doctrine >> is it warps management's risk analysis. Instead of appropriate investments, >> management makes excessively risky decisions in an attempt to achieve >> short-term returns and maximize shareholder value. >> >> Is PG&E too big to fail? > >But what would that mean? All the infrastructure is there, the only >issues are cash flow and regulation of prices. If PGE was diddling with >its infrastructure, lending out towers to shady businesses and such, >there might be a parallel :-). During the 19th century, there were a number of railroad bankruptcies. The courts ruled that since all of their assets were good for only one thing -- a railroad -- the only choice was to keep the corporation going. The real change, per the article I cited, is who makes the hard decisions. --Steve Bellovin, http://www.research.att.com/~smb

1 0