Are they all assigned to a system that's on a network that's directly connected to the router?
On Jan 17, 2008 3:59 PM, Shane McKinley <[EMAIL PROTECTED]> wrote: > > > > None of these next-hop addresses are assigned to an interface on the router. > > Shane > > > -----Original Message----- > From: Justin Fletcher [mailto:[EMAIL PROTECTED] > Sent: Thu 1/17/2008 6:46 PM > To: Shane McKinley > > Cc: vyatta-users@mailman.vyatta.com > Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... > > Are the next hops directly connected? There was an issue with > recursive route lookup -- > > On Jan 17, 2008 2:56 PM, Shane McKinley <[EMAIL PROTECTED]> wrote: > > I have found the static routes causing the issue: > > > > route XZ.85.142.64/26 { > > next-hop: XX.128.129.18 > > metric: 1 > > } > > route XX.128.136.216/29 { > > next-hop: XZ.85.140.254 > > metric: 1 > > } > > route XX.128.140.16/29 { > > next-hop: XX.128.140.26 > > metric: 1 > > } > > > > Now, the question is why? How can I dig further to find out why these > > are causing the rtrmgr to crash? > > > > Shane McKinley > > Habersham EMC > > > > -----Original Message----- > > From: Dave Roberts [mailto:[EMAIL PROTECTED] > > Sent: Thursday, January 17, 2008 5:16 PM > > > > To: Shane McKinley; vyatta-users@mailman.vyatta.com > > Subject: RE: [Vyatta-users] Waiting for xorp_rtrmgr... > > > > > (SIDE NOTE: (No offense meant) Why should changing interface notations > > > > > and static routes cause anything to crash?) > > > > It shouldn't. That's one of the big things we're fixing in Glendale. The > > Routermanager process did not handle errors well at all. It has been > > eliminated entirely in Glendale. > > > > -- Dave > > > > _______________________________________________ > > Vyatta-users mailing list > > Vyatta-users@mailman.vyatta.com > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > > > _______________________________________________ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
