next_hop issue on iBGP peer

[Ondrej Zajicek]

On Tue, Mar 11, 2014 at 02:56:09PM +0200, MrBr @  GMail wrote:
> 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?

Hello

You should use "direct" option to switch from multihop to singlehop.

It is possible to use "gateway recursive" to switch gateway behavior
for singlehop sessions (default 'gateway direct'), but not in the
other way.

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20140325/37bd477a/attachment-0001.asc>