On 03/08/2013 12:43 PM, Andre Nathan wrote:
On Fri, 08 Mar 2013, Hans van Kranenburg wrote:
And how do they end up in your t_bgp table? Via p_bgp_to_wzyx pipe,
or learned from quagga via iBGP?
The come from quagga via iBGP:
bird> show route for a.b.0.0/24 table t_bgp
a.b.0.0/24 via x.y.z.2 on eth1 [iBGP Mar05] * (100) [i]
bird> show route for a.b.1.0/24 table t_bgp
a.b.1.0/24 via x.y.z.2 on eth1 [iBGP Mar05] * (100) [i]
From the p_bgp_to_wzyx pipe I get this (as expected):
bird> show route for a.b.0.0/24 table t_wzyx
a.b.0.0/24 unreachable [originate_to_wzyx Mar05] * (200)
bird> show route for a.b.1.0/24 table t_wzyx
a.b.1.0/24 unreachable [originate_to_wzyx Mar05] * (200)
Ok, well I think it's best then not to try fix quagga, but create a
temporary import filter that only allows what you want to accept.
I don't know exactly about quagga, I do know I got very frustrated
with it and switched to bird. :)
Tell me about it :) That's why I'm switching to bird. But I want to get
everything right in the first router before reinstalling the second one.
--
Hans van Kranenburg - System / Network Engineer
+31 (0)10 2760434 | [email protected] | www.mendix.com
