This is my attempt :

https://github.com/vyos/vyatta-cfg-quagga/pull/10

It does generate what I expect. Although for it to work I had to remove the "match ip next-hop acl_to_gw" ... but that's unrelated I think, still investigating this.

Ok, so the main issue is that the route-map is only applied to routes installed _after_ it's been setup ... so you have to remove / readd all the static routes which obviously doesn't work when you reboot :(

You need "create" section in your templates/policy/route-map/node.tag/rule/node.tag/set/src/node.def to make things survive reboots, I think.

Changing the priorities, I managed to make it work and it's loaded fine on reboot.

But if you modify them at run-time, changes are not applied ... worse, if you want the policy, then edit static routes, quagga doesn't even properly changes the old routes ...

At the moment, I'm living with that limitation, but I think the best option would be to just hide the 'route-map' stuff from the user for the 'static' protocol and create them under the hood and just have a 'src' node configurable when creating static route.

This way, the sequencing of removing route-maps / routes and reapplying them can be enforced so that quagga doesn't get confused.

Can you push your recent changes to github?

I pushed the priority changes I had to do on my T132 branch.

However I'll probably try to implement the alternate version I described above. That'll have to wait a couple weeks though ... traveling abroad ATM.