iBGP

[Miłosz Oller]

Hi

I have now updated BIRD routers to 1.3.9.
I configured VRRP with keepalived/Debian, but it's not working properly.

My network:
OP1 = R01 -iBGP- R02 = OP2

R01 is "main" router for 91.237.68.0/22
R02 is "main" router for 91.231.205.0/24

91.237.68.1 (vip1) and 91.231.205.1 (vip2) are Virtual IP in Keepalived
with VRRP. vip1 is switching to R02, then keepalived runs notify script
with "configure soft.." to load other config with new protocol static. 
Then routing to prefixes is gone. 
Is the right way? Both prefixes must be all the time on both servers in
protocol static?

How to configure ibgp with vrrp properly?

-- 
Miłosz Oller 


Dnia 2013-01-01, wto o godzinie 12:35 +0100, Ondrej Zajicek pisze:
> On Sun, Dec 30, 2012 at 03:37:25PM +0100, Miłosz Oller wrote:
> > After add comment next hop self and add gateway direct:
> > 
> > protocol static {
> >         route 91.231.205.0/24 reject;
> >         route 91.237.68.0/22 reject;
> > }
> > 
> > [..]
> > #    next hop self;
> > gateway direct;
> > [..]
> > 
> > bird> show route 91.231.205.0/24 all
> > 91.231.205.0/24    unreachable [static1 15:27] * (200)
> 
> > Why static route is unreachable?
> 
> Hello
> 
> A route with 'reject' target is unreachable by definition [*]. In future
> versions we will even support and prefer 'unreachable' keyword instead
> of 'reject' keyword in static protocol for such routes.
> 
> 
> [*] If such route is exported to the kernel and the kernel routes a
> packet according to that route, the packet is rejected with ICMP
> 'destination unreachable' message.
>