hi julien, using different tables is probably the only wat to get it done as you get seperate rib and in that way you can guarantee symmetrical paths but hou don't have upstream redundancy.
kurt Op zo 6 jan. 2019 01:11 schreef Ondrej Zajicek <santi...@crfreenet.org: > On Sat, Jan 05, 2019 at 10:57:45PM +0100, Julien Sansonnens wrote: > > Hi Kurt, > > > > Thanks a lot for your reply. > > > > I understand the logic, but I'm sure there must be a way to choose the > > routes one want to export? > > > > Imagine I have two upstreams, and two peered networks (say: customers). > > Both upstreams provide me with a (kind of) full table. > > > > I would like to export the table I get from upstream 1 to peer 1, and the > > table from upstream 2 to client 2 (regardless if it's the best route or > > not...) > > Hi > > It seems that you want something like policy routing, see example in wiki: > > https://gitlab.labs.nic.cz/labs/bird/wikis/Policy_routing > > -- > Elen sila lumenn' omentielvo > > Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org) > OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) > "To err is human -- to blame it on a computer is even more so." >
