The circuit costs here are set to 4 for LAN and 3 for tunnels. The issue may be that if a node (at the end of the chain so to speak) has 2 tunnel links of the same cost and that the final destination costs the same I could see where DECnet *might* get confused. Let's look at the following contrived example: FRUGAL:: connects to LEGATO:: - cost of 3 FRUGAL:: connects to SG1:: - cost of 3 LEGATO:: connects to GORVAX:: - cost of 3 SG1:: connects to GORVAX:: - cost of 3 Fred, on node FRUGAL:: tries to copy a (large) file from GORVAX:: to FRUGAL:: *may* see some issues. On the other hand if Fred chooses to favor SG1:: over LEGATO:: (cost wise) he should not see any problems: Ex: FRUGAL:: connects to LEGATO:: - cost of 3 FRUGAL:: connects to SG1:: - cost of 2 The route is guaranteed to be the same for the entire transaction. It will be (using poor man's routing to demonstrate) FRUGAL::SG1::GORVAX:: at a cost of 5, not FRUGAL::LEGATO::GORVAX:: at a cost of 6. -Steve ________________________________ From: owner-hecnet at Update.UU.SE on behalf of hvlems at zonnet.nl Sent: Thu 1/5/2012 10:43 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Multinet circuit costs PS I can copy to Legato alright. PPS I did check the netserver.log files and found nothing out of the order.