Hi, in the config snippets below I added the export filter, see the "<<<<" signs. The goal is to set the med. When running "configure" this change triggers this warning: <WARN> Channel nextlayer_ndc1_v4.ipv4 hits route export limit (1), action: disable Which suggests that this config change causes a misconfiguration and route leak, correct? I only expect to announce a single prefix. How would you actually set the med instead? thank you! Christoph protocol static mynet4 { ipv4; route 109.70.100.0/24 reject; } filter set_med20 { bgp_med = 20; accept; } template bgp bgp_base4 { local as 208323; strict bind on; prefer older yes; graceful restart on; graceful restart time 300; ipv4 { import filter transit_in; import keep filtered on; import table on; export where proto = "mynet4"; export limit 1; }; } protocol bgp nextlayer_ndc1_v4 from bgp_base4 { hold time 120; keepalive time 20; neighbor 2.2.2.2 as 1764; source address 1.1.1.1; authentication md5; include "../peers-secrets/....conf"; multihop; ipv4 { <<<< export filter set_med20; <<<< }; <<<< }
On Thu, Feb 12, 2026 at 06:27:21PM +0100, Christoph via Bird-users wrote:
I assume this line from the template:> export where proto = "mynet4";
gets overwritten by this line in the specific bgp concection:
export filter set_med20; <<<<
which causes more exports than I intended and triggers the export limit.
Yes, that's exactly that. BIRD can't merge these filters well when templating, and instead they are replaced. Also, it's impossible to guess whether the user would like to AND the filters, OR them, and in which order. Happy routing! Maria -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.
participants (2)
-
Christoph -
Maria Matejka