Hello, No, in the template you can set a "default" filter for example. But if you set the filter in the template's child, the setting gets overwritten.
Regards, Alexander On Tue, Mar 3, 2026 at 12:49 PM BASSAGET Cédric < [email protected]> wrote: > Hello, > > I'm trying to simplify my old bird 1.6 config, the aim is migrating to v2 > then v3. > > > I have a config like : > > template bgp private_peering_ipv4 { > local as my_ans; > path metric 2; > ipv4 { > import all; > import filter { > if (net.len > 24 ) then reject; > bgp_large_community.add((my_asn, 1, 1003)); > accept; > }; > export filter export_my_routes_ipv4; > import keep filtered; > }; > } > > protocol bgp PEER_v4_peer1 from private_peering_ipv4 { > router id 195.42.145.x; > neighbor 195.42.144.104 as 6939; > } > protocol bgp PEER_v4_peer2 from private_peering_ipv4 { > router id 195.42.145.x; > neighbor 195.42.144.104 as 6939; > ipv4 { > import filter { > bgp_large_community.add((my_asn, 1, 1009)); > accept; > }; > }; > } > > > > the problem here is that as soon as I define a new import filter for my > second peer, the filter from the template is omitted. > > Is there a way to add inheritance between the templates, or anything else > that wouldn't overwrite the template filters ? > > Regards, > Cédric > >
