Changing OSPF attributes in pipe filter - Bug?

[Ondrej Zajicek]

On Sat, Jun 12, 2021 at 12:51:37PM -0400, Paul Donohue wrote:
> I'm importing BGP and OSPF routes from several interfaces, and I would
> like to use the OSPF metrics as-is on the local router.  However, I'm
> exporting these routes via OSPF on several other interfaces, and I'd like
> to selectively override the OSPF metric on some (but not all) of the
> routes before performing route selection and exporting them via OSPF on
> the other interfaces.
> 
> ...
> 
> However, that isn't working; ospf_metric1 is not changing.
> 
> Am I doing something wrong, or is this a bug?

Hi

It seems that there is a bug that causes a class of attributes not work
properly when set in pipe filters. Some attributes (i.e. OSPF ones for
OSPF route) are stored directly in the route structure and not in a
separate attribute list. They are expanded to attribute list and they
are not properly stored back when passed through pipe. BGP attributes
or OSPF attributes on non-BGP routes are always in attribute list, so
they are handled properly. Will check that and fix that.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."