From wei.wen0 at gmail.com Tue Dec 2 06:56:37 2014 From: wei.wen0 at gmail.com (Wei Wen) Date: Tue, 2 Dec 2014 09:56:37 -0500 Subject: [Xorp-users] testing XORP modules Message-ID: Hello, I saw that there are tests directory with each module in the source code. So I think about doing some testing myself. The first problem I encountered is the ".h" file. When using g++, it cannot find where the header files are located. After I had that resolved, and compile the source code again with g++, I still got a lot of error messages. Could someone please let me know if there is some way to test the code? Since the testing code is already written, I am sure there should be a way to run the testing code. Thank you very much. Best regards, Wei Wen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20141202/36291904/attachment.html From xorp at iancoetzee.za.net Sun Dec 7 22:24:06 2014 From: xorp at iancoetzee.za.net (Ian Coetzee) Date: Mon, 8 Dec 2014 08:24:06 +0200 Subject: [Xorp-users] Ospf imports with the wrong metric into the kernel Message-ID: Good day to all, We have started using xorp as a replacement for bird for the ospf on our servers however we have noticed an interesting phenomenon. Any routes imported via ospf gets a kernel metric < 110 which is a breach of the protocol. I have defined an import policy to automagically change it to the right metric but maybe there is just a config rule that I am just missing? This is a pastebin with all the gory details http://pastebin.com/Lhjk5qJA Kind regards From greearb at candelatech.com Wed Dec 10 14:32:13 2014 From: greearb at candelatech.com (Ben Greear) Date: Wed, 10 Dec 2014 14:32:13 -0800 Subject: [Xorp-users] Ospf imports with the wrong metric into the kernel In-Reply-To: References: Message-ID: <5488C9ED.4080205@candelatech.com> On 12/07/2014 10:24 PM, Ian Coetzee wrote: > Good day to all, > > We have started using xorp as a replacement for bird for the ospf on > our servers however we have noticed an interesting phenomenon. > > Any routes imported via ospf gets a kernel metric < 110 which is a > breach of the protocol. I have defined an import policy to > automagically change it to the right metric but maybe there is just a > config rule that I am just missing? > > This is a pastebin with all the gory details http://pastebin.com/Lhjk5qJA You specified the policy in Xorp? I didn't see it in the pastebin. Either way, if doing a policy works, then I would just do that unless someone has time to dig into the code and figure out how to have it choose better defaults. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From xorp at iancoetzee.za.net Wed Dec 10 22:17:20 2014 From: xorp at iancoetzee.za.net (Ian Coetzee) Date: Thu, 11 Dec 2014 08:17:20 +0200 Subject: [Xorp-users] Ospf imports with the wrong metric into the kernel In-Reply-To: <5488C9ED.4080205@candelatech.com> References: <5488C9ED.4080205@candelatech.com> Message-ID: Hi Ben, Yes I did put the policy in xorp, however I forgot to commit the settings change and unknowingly the configs was reloaded. If you want I can upload the changed configs. I can keep it like it is for now. I would just suggest that someone just put something in the documentation, because sometimes the routes gets imported with a kernel metric of one, which could cause havoc if you use static routes in conjuction with xorp. Is there a place where I can log a bug? Kind regards 2014-12-11 0:32 GMT+02:00 Ben Greear : > On 12/07/2014 10:24 PM, Ian Coetzee wrote: > > Good day to all, > > > > We have started using xorp as a replacement for bird for the ospf on > > our servers however we have noticed an interesting phenomenon. > > > > Any routes imported via ospf gets a kernel metric < 110 which is a > > breach of the protocol. I have defined an import policy to > > automagically change it to the right metric but maybe there is just a > > config rule that I am just missing? > > > > This is a pastebin with all the gory details > http://pastebin.com/Lhjk5qJA > > You specified the policy in Xorp? I didn't see it in the pastebin. > > Either way, if doing a policy works, then I would just do that unless > someone > has time to dig into the code and figure out how to have it choose better > defaults. > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20141211/bf790ce4/attachment.html