Hi list, After using bird for some time now, I've found few things that are annoying me, or simply break things that should work flawlessly ;) bird> show protocols all [some BGP protocol] Routes: 19186 imported, 2 exported, 84627 preferred My guess is that it has something to do with pipes. I have multiple pipes that do import filter { if proto="[some BGP protocol]" then accept; reject; }; Problem 2: bird's reality: ng6 up (index=35) PtP Multicast AdminUp LinkUp MTU=1492 local.ip/32 (Primary, opposite 192.168.16.35, scope univ) vlan3372 up (index=36) PtP Multicast AdminUp LinkUp MTU=1492 local.ip/32 (Primary, opposite 192.168.16.171, scope univ) ng7 up (index=37) PtP Multicast AdminUp LinkUp MTU=1492 local.ip/32 (Primary, opposite 192.168.17.123, scope univ) reality's reality: ng4: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 1492 inet local.ip --> 192.168.16.35 netmask 0xffffffff ng6: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 1492 inet local.ip --> 192.168.16.171 netmask 0xffffffff ng7: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 1492 inet local.ip --> 192.168.17.123 netmask 0xffffffff # ifconfig vlan3372 ifconfig: interface vlan3372 does not exist Above happened after I decided that I don't feel like wanting vlan3372 and changed it to something else. In the meantime some customer decided to open PPPoE session, not knowing this will spell his doom :> bird also happily ignores interface name changes, which hinders nice features such as interface "name*" etc. Thanks for reading. :)