iBGP unreachable

[Panda RoboLegs]

Hello,

there is no IGP. I thought that I can resolve the BGP-Next-Hop via static default gateway (0.0.0.0/0).
It seems that is not possible.
Does anyone have a link where it is written that BGP next-hop is not resolvable via static default gw?



But now the good news:
I found an old mailing list entry with an snippet that solved my problem.

filter test {
 gw = IP-directly-connected-next-hop;
 accept;
}

protocol bgp {
 ...
 import filter test;
}


So now every route has a directly connected default gw. every route is resolvable.


The question above is still unanswered.
why bgp can't resolve the next hop via default gw

Further links will be appreciated.


Best regards



> Subject: Re: iBGP unreachable
> To: bird-users at network.cz
> From: jan.matejka at nic.cz
> Date: Mon, 11 Apr 2016 21:21:24 +0200
> 
> On 04/11/2016 05:13 PM, Panda RoboLegs wrote:
> > Hello,
> > I am new to Bird and I am trying to set up a Looking-Glass.
> > 
> > I have configured a iBGP-Session with a route-reflector to gather the
> > needed routes.
> > 
> > When I do a "show route". Every route I got via BGP is unreachable.
> 
> Is your IGP table correctly feeded?
> 
> > Is there any posibility to solve ths problem without adding an IGP or a
> > static route to every next hop?
> 
> I assume that your iBGP sessions are multihop. Therefore at least your
> kernel should know where to connect … maybe you can add something like
> this (writing without looking into doc, typos may occur):
> 
> protocol kernel {
> 	table igpt;
> 	import all;
> 	export none;
> 	learn;
> }
> 
> protocol bgp {
> 	...
> 	igp table igpt;
> }
> 
> This assumes that your IGP table is feeded by another source than this
> running Bird.
> --
> MQ
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20160412/bc5c00f9/attachment.html>