I found a bug in my adjacency processing that made other adjacencies use index 0 in the decision database, I think that is what has been causing the Check failures. -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Paul_Koning at Dell.com Sent: 25 August 2012 22:55 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Any DECnet Routing Protocol Experts Out There? You process address 0 exactly as any other level 1 routing message entry. Then in the forwarding process of an L1 router, if the destination is out of area, use entry 0 to decide how to forward the packet. Why do you get failures from Check? I don't see how you could get that. paul On Aug 25, 2012, at 4:36 PM, Rob Jarratt wrote: I am working on a user mode DECnet router and I have a question about the Level 1 Routing message. Specifically, sometimes I receive a level 1 routing message with routing information for destination address 0. The spec says this represents the "nearest level 2 router". What I am not clear about is how this is supposed to be treated in the Decision Process, specifically Section 4.7.3 item F in the specification. The reason I ask is that if I blindly accept address 0 I think it corrupts the hop and cost tables, because the Check process then gets failures. Thanks Rob