[Xorp-users] Ospf imports with the wrong metric into the kernel

[Ian Coetzee]

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 <greearb at 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 <greearb at candelatech.com>
> 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