Thread View: aus.acsnet
2 messages
2 total messages
Started by Operator
Wed, 08 Jul 1992 22:46
Routing loops to munnari
Author: Operator
Date: Wed, 08 Jul 1992 22:46
Date: Wed, 08 Jul 1992 22:46
30 lines
1655 bytes
1655 bytes
We have been getting the following for some weeks. The key appears to be the suggestion that there are routing loops to munnari. Can someone experienced in decoding ACSnet badhandler messages suggest where the problem might be. Thanks, Greg OConnell ---------------------------------------------------------- Date: Wed, 8 Jul 92 22:01:36 CST From: acsnet@csaadel.adl.csa.oz (ACSnet Networking Software) Subject: ACSnet badhandler at csaadel.adl.csa.oz Apparently-To: root Status: R Invoked by "router" Link "lux" Error message <<EOF Returned message discarded: Handler "/usr/spool/net/_lib/fileserver\ " unavailable EOF End of message in "/usr/spool/net/_bad/0ro+eKi+c+jBp" <<EOF RR1=Routing loop detected to node "munnari"\036ROUTE=\254csaadel\275\ 0\254lux\27516\254sirius\27518\254augean\2751\254mun\ nari\27528\254goanna\2751246\254munnari\2756216\254go\ anna\2753209\000\0004040\000,goanna=0,munnari=16,augean\ =3,sirius=1,lux=4020\000\000\0354278\000\000\000\000\ \000 EOF
Re: Routing loops to munnari
Author: Piers Lauder
Date: Thu, 09 Jul 1992 05:26
Date: Thu, 09 Jul 1992 05:26
51 lines
2826 bytes
2826 bytes
In article <1992Jul8.224642.4009@csaadel.adl.csa.oz>, root@csaadel.adl.csa.oz (Operator) writes: > We have been getting the following for some weeks. The key appears to be > the suggestion that there are routing loops to munnari. Can someone experienced > in decoding ACSnet badhandler messages suggest where the problem might be. > > Thanks, > Greg OConnell > ---------------------------------------------------------- > Date: Wed, 8 Jul 92 22:01:36 CST > From: acsnet@csaadel.adl.csa.oz (ACSnet Networking Software) > Subject: ACSnet badhandler at csaadel.adl.csa.oz > > Invoked by "router" > > Link "lux" > > Error message <<EOF > Returned message discarded: Handler "/usr/spool/net/_lib/fileserver\ > " unavailable > EOF This just means that you don't have a handler for the message type involved -- since the message is returning, it is junked (otherwise it would have been saved and mail sent to NCC_MANAGER > End of message in "/usr/spool/net/_bad/0ro+eKi+c+jBp" <<EOF > RR1=Routing loop detected to node "munnari"\036ROUTE=\254csaadel\275\ > 0\254lux\27516\254sirius\27518\254augean\2751\254mun\ > nari\27528\254goanna\2751246\254munnari\2756216\254go\ > anna\2753209\000\0004040\000,goanna=0,munnari=16,augean\ > =3,sirius=1,lux=4020\000\000\0354278\000\000\000\000\ > \000 > EOF The bytes after the ROUTE string show the original route (before being returned) as csaadel,lux,sirius,augean,munnari,goanna,munnari,goanna. So it looks like goanna and munnari disagree about the route to wherever it was originally destined. (As you seem to have truncated the error message before the part with the destination address, it is hard to tell). Anyway, as both munnari and goanna are running SUNIII, this is probably one of the usual SUNIII routing bugs emerging. Contact the managers at these sites with details of the original destination you were trying to reach, and try persuading them to hack their routing tables to get around the loop. -- Piers Lauder NET: piers@cs.su.oz.au Computer Science TEL: +61 2 692 3423 Madsen Building, F09 FAX: +61 2 692 3838 Sydney University, Sydney, NSW 2006, Australia.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads