iBGP

[Miłosz Oller]

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)
	Type: static unicast univ
                   via 91.231.205.193 on eth0 [bgp_syscom 15:27] (100)
[i]
	Type: BGP unicast univ
	BGP.origin: IGP
	BGP.as_path: 
	BGP.next_hop: 91.231.205.193
	BGP.local_pref: 100

Why static route is unreachable? On both routers are two prefixes in
static protocol. On second router is the same problem.

-- 
Miłosz Oller 

Dnia 2012-12-30, nie o godzinie 14:14 +0200, Roman Skopenko pisze:
> On 30.12.2012 14:02, Miłosz Oller wrote:
> > Session on router no.2:
> > protocol bgp bgp_r1_ibgp {
> >      description "iBGP";
> >      import all;
> >      export all;
> >      next hop self;
> >      local as 198611;
> >      neighbor 91.231.205.193 as 198611;
> >      source address 91.231.205.194;
> > }
> >
> > bird> show route 91.231.205.0/24 all
> > 91.231.205.0/24    unreachable [static1 14:36] * (200)
> >     Type: static unicast univ
> >                     unreachable [bgp_r2_ibgp 14:37 from 91.231.205.193]
> > (100/-) [i]
> >     Type: BGP unicast univ
> >     BGP.origin: IGP
> >     BGP.as_path:
> >     BGP.next_hop: 91.231.205.193
> >     BGP.local_pref: 100
> >
> > Any ideas?
> >
> 
> I am not sure...
> try (if neigbour unreach)
>    gateway direct;
> or/and (if prefixes do not pass thru)
>    rr client;
>