Article View: aus.acsnet
Article #40Re: Death of ACSnet
From: Frank Crawford
Date: Wed, 22 Apr 1992 04:35
Date: Wed, 22 Apr 1992 04:35
43 lines
2753 bytes
2753 bytes
In article <1992Apr14.064848.4228@bohra.cpg.oz.au> als@bohra.cpg.oz.au (Anthony Shipman) writes: >The word I have been hearing of late is that there are few (and getting fewer) >people left around the ridges with any understanding of ACSnet and SUNIII >software (or even MHSnet?). The backbones are mostly AARnet these days. As >time goes by and links fail it gets harder to find someone who can put things >right. > >For us ACSnet has broken down for the second time this year. When our >machine bohra in Hawthorn sends a message to munnari, only 10-20kms away, it >goes fairly directly in only 2 hops. Return messages go via Sydney! Real distances don't alway equate to what the network thinks is the shortest distance! >Somewhere along this long return route messages are inclined to go astray. >At the moment we can get no response from munnari.oz. The last time this >happened it was shown to be a fault with the return path >munnari->basser->perch->ditmela. At the moment the return path is supposed to >be munnari->basser->ditmela. Yep currently most of your messages are ending up at ANSTO, where I have to manually reroute them to pta (which has a link to yarra, which is in Melbourne). I can't work it out either! Part of the problem seems to lay with metro, because messages bounce between basser and metro, before being rerouted (manually?) via atom. I have no idea why munnari wants to send things via basser. >Anyway it's still broken. For us ACSnet is as good as gone. Fortunately we >get mail and news via AARnet avoiding the bulk of ACSnet. >To fetch files I can use ftpmail via uow, and they will be getting a lot of >business from me. As of today, I've rerouted about 100 messages from metro, some for bohra, but most for monu6. At a guess, someone came back after Easter and found all these looping messages and has now rerouted them to me! >I wonder how long until ACSnet fragments really badly, or will some kind >soul look into it? This doesn't seem too different to the past. It is just that some major nodes are a little slower to respond to ACSnet problems these days. Frank
Technical Details
Message-ID:
<74@quark.ansto.gov.au>Path:
arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!metro!quark!iris.ansto.gov.au!frankReferences:
<1992Apr14.064848.4228@bohra.cpg.oz.au>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1057be,eac49271d2c1b532 X-Google-Attributes: gid1057be,public X-Google-ArrivalTime: 1992-04-21 21:35:59 PST Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!metro!quark!iris.ansto.gov.au!frank From: frank@iris.ansto.gov.au (Frank Crawford) Newsgroups: aus.acsnet Subject: Re: Death of ACSnet Message-ID: <74@quark.ansto.gov.au> Date: 22 Apr 92 04:35:59 GMT References: <1992Apr14.064848.4228@bohra.cpg.oz.au> Sender: news@quark.ansto.gov.au Organization: Australian Nuclear Science and Technology Organisation Lines: 43