Is that how the Vyatta company operates? Leave bugs unpatched and hope someone will pay for support? It would seem to make more sense to hold features back instead of bugs.
I am more than willing to pay for support, but I wanted to make sure the product would work for me first. I have a better idea -- Patch the bugs, and allow the software to be functional for the purpose it was created. Then we are talking. Unfortunately it seems Vyatta is unlikely an acceptable replacement for my Cisco 7500. So far I have ran into 3 detrimental issues and the routing bugs bring me just short of a dead end. 1. VRRP Limitations 2. Policy System Limitations 3. Routing Bugs I am still going to try to work around this issue, but maybe the Vyatta company can re-think the bug-fix-holding for monetary purposes philosophy. With all due respect, Shane McKinley Habersham EMC -----Original Message----- From: Justin Fletcher [mailto:[EMAIL PROTECTED] Sent: Thursday, January 17, 2008 9:01 PM To: Shane McKinley Cc: vyatta-users@mailman.vyatta.com Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... I think you've hit bug 2390: RIB: xorp_rib crashed after a static route with a nextop through an unxisted interface or a route being configured and committed See https://bugzilla.vyatta.com/show_bug.cgi?id=2390 ; it's fixed in the supported version. Best, Justin On Jan 17, 2008 5:19 PM, Shane McKinley <[EMAIL PROTECTED]> wrote: > > > > #1 - No, but I do have a static interface-route with XX.128.128.0/20 - > the actual interface is XX.128.128.0/24 -- the reason I have this is > for proper BGP exporting > #2 - Invalid, my mistake > #3 - Dido to #1 > > My interface-routes are last on my static routes list in the config > -- could this be the issue? > > -Shane > > > > > 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
