recursive route lookup (was: Re: upgrade 1.2.4 - 1.3.1 reverted)

[Timo Weingärtner]

Hallo Ondrej Zajicek,

2012-10-24 um 13:54:37 schriebst Du:
> On Mon, Oct 22, 2012 at 07:52:48PM +0200, Timo Weingärtner wrote:
> > 2011-05-30, 17:04:16 you wrote:
> > > Generally, the IP address from the BGP NEXT_HOP attribute (i.e. the
> > > ones mentioned in 'Next hop address X.X.X.242 resolvable ..' messages
> > > should be resolvable through a route which is not from BGP.
> > 
> > I just stumbled over that when trying to remove "next hop self" after 1.3
> > has recursive lookup.
> > 
> > What's the problem with using iBGP routes for recursive lookups (when
> > using iBGP as IGP)? The message even says that the route is resolvable.
> 
> BIRD does not allow recursive routes to depend on another recursive route.
> If your iBGP is configured to generate non-recursive routes (using
> 'gateway direct' option), then recursive routes (from another BGP)
> could depend on that routes, but i am not sure if such setting could
> be useful, esp. it does not work if you want to use the same iBGP session
> for both recursive and non-recursive routes.

Let me rephrase my question: Why does BIRD not allow recursive routes to 
depend on another recursive route. What could go wrong if it was allowed?


Grüße
Timo
-- 
Timo Weingärtner
Abteilung Technische InfraStruktur
Karlsruher Institut für Technologie (KIT)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20121024/7bca48e5/attachment-0001.asc>