next_hop issue on iBGP peer

[MrBr @ GMail]

Hi,
I'm trying to solve an issue of "unreachable" prefix

The scenario is as followin:
BIRD 1.4.0 (RtrB) has iBGP peer with (RtrC) that has route reflector
originating prefix 10.0.2.0/24
RtrB ip is 10.1.1.1
RtrC ip is 10.1.1.2
on RtrC "sh ip bgp 10.0.2.0/24" provides that the next_hop is 10.4.4.4
on RtrB "show route 11.0.2.0/24 table master all" provides BGP.next_hop:
10.4.4.4

adding  "gateway direct;" provides "Multihop BGP cannot use direct gateway
mode"
I'm little bit confused , isn't it a whole purpose of "gateway direct;" to
provide legacy functionality to iBGP peers?

I've tried changing next hop via import filter " bgp_next_hop = 10.4.4.4;"
Next hop of prefix in RtrB changed , however the prefix itself stayed
"unreachable"

The only thing helped configuring static protocol record for 10.4.4.4, but
this is not an option for production environment due to dynamic nature of
prefixes and multiple next hops

Please advise
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20140311/a4339fd9/attachment.html>