iBGP

Miłosz Oller milosz at sys-com.pl
Sun Jan 6 15:47:32 CET 2013


Hi

I configured ibgp witch two routers. On R1 "main" prefix is
91.237.68.0/22 (with gw on 68.1 for client network), on R2 "main" is
91.231.205.0/24 (with gw on 205.1 for client network).

If protocol static is configured on both routers like:
protocol static {
         route 91.231.205.0/24 reject;
         route 91.237.68.0/22 reject;
}

From R1 network 91.231.205.0/24 is unreachable and from R2
91.237.68.0/22 is unreachable.
Whithout announce two prefixes on both routers I can't configure VRRP.

-- 
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.
> 




More information about the Bird-users mailing list