[Xorp-users] xorp1.6 fails to run on Debian Etch 2.6.18-5-486

[AWalton]

I have to say you have me somewhat confused now. Which version shall I 
try? What makes you think that either xorp-ct or svn of the official 
xorp tree will actually compile and run especially as 1.6 did not.

Dont forget this is a 486 VIA fanless processor that I must compile on. 
It takes a long time to try anything.
Aidan

Ben Greear wrote:
> On 05/06/2010 10:37 AM, Adam Greenhalgh wrote:
>> Aidan,
>>
>> There have been some fairly significant changes in how xorp is run
>> since 1.4, and its back being a community project again. A number of
>> changes have occured to the stack. The current svn on sourceforge is
>> going to be the basis of the 1.7 release, it isn't a huge change over
>> 1.6 , with the major change being the adoption of scons. Ben has been
>> porting some of his basic changes back from his xorp.ct tree into
>> sourceforge svn to fix bugs and a few other things. The idea is to
>> roll the 1.7 release fairly shortly because of the inclusion of scons
>> . 1.8 will follow fairly shortly after and be an adotpion of a lot
>> more ben's tree (maybe all).
>>
>> My suggestion would be for you to try the sourceforge svn code on a
>> test box and see if that works for you, and help us iron any bugs out
>> in it before we roll the 1.7 release.
>
> I am certain there are some un-caught exceptions in 1.7 BGP, because
> I hit them while fixing up the harness code in xorp.ct, and also 
> reproduced
> some of them when configuring bgp as virtual routers.
>
> But, fixing the harness was a good bit of patches and also includes
> some logic that depends on other xorp.ct patches, so I'm not sure if
> it's worth trying to backport it into 1.7.  From what I understand
> about 1.7 changes, it's likely those same BGP exception issues exist 
> in 1.6.
>
> I'm not sure if these are the same issues that Aidan is hitting or not.
>
> If we're going to attempt to release 1.7 with as few changes as possible,
> I think we should just go ahead and release, and pour all effort into
> 1.8.
>
> If I am allowed to push most or all of xorp.ct into 1.8, then I can
> give developers ( and non-profits, students, etc) licenses to our 
> virtual-router
> software so people can easily configure large virtual router networks 
> using xorp.
> This makes it trivial to test many large network scenarios that would 
> otherwise
> take lots of effort and/or hardware (like two clouds of OSPF routers 
> joined
> by two BGP routers, etc).
>
> Thanks,
> Ben
>