Hello, Kevin, You can create a RIB for every peer you have and filter prefixes between that RIBs on pipes, as it is described in https://gitlab.labs.nic.cz/labs/bird/wikis/Route_server_with_community_based... I would recommend this way because it is structured and gives you a lot of control. In your specific case, you can just add one additional RIB to connect your upstream and the customer and get your default route to your master RIB through a pipe. But the previous solution would be much easier to support. -- Best regards, Valery Lutoshkin -----Original Message----- From: Bird-users [mailto:bird-users-bounces@network.cz] On Behalf Of Kevin B Sent: Thursday, May 30, 2019 8:07 AM To: bird-users@network.cz Subject: Forward full view to a downstream Hello, My customer wants me to announce a full IPv4 table via BGP to him, but we don't use it on the BGP node where that customer is peered. We receive the default from our BGP upstream, but can actually ask for and receive a full view as well, but only for a purpose of forwarding it to the customer. What would be a scheme to receive a full-table from a BGP upstream and forward it to a BGP downstream, without importing it to our own routing table? I am not very experienced with Bird, but some guys on Freenode ##networking have suggested using a pipe, can someone help me on this please?