On Mon, Dec 05, 2011 at 07:53:03PM -0500, dspazman@epicup.com wrote:
Let's say you have two routing tables (T1, T2), one for each interface (eth0, eth1), so you can route traffic out each one separately.
https://git.nic.cz/redmine/projects/bird/wiki/BGP_example_2
I'm assuming there would have to be some changes to that BGP script to support both routing tables. I'm not sure how to support multiple routing tables with bird. Would someone be able to show that? Seems like it would be a useful example in general, and be a pretty simple modification to that example for someone who knows what they are doing.
I didn't see anything on any of the examples on git.nic.cz that showed using multiple tables, as a configuration like http://lartc.org/howto/lartc.rpdb.multiple-links.html shows you'd be using for multiple outgoing connections, which you would typically have in a BGP situation.
Though maybe https://git.nic.cz/redmine/projects/bird/wiki/Policy_routing explains it. I plan on keep looking into that example as well.
Yes, that is an example for using multiple routing tables. You can prefer one uplink in one table and the other in the second table. You can specify that internal traffic from eth0 go through the first one and from eth1 through the second one, but: - The OSPF config (mentioned before) does not automatically split that traffic, 'cost' work in a different way. - Even if traffic from eth0 and eth1 is sufficiently splited, that will hel just split outgoing traffic on uplinks, splitting incoming is harder. -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@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."