<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>I tried the configuration with a second table and the "igb table" in bgp protocol.<br>And it is working fine.<br><br>Thank you for your help and your explanation.<br><br><br>Best regards<br><br><br><br><div>> Date: Tue, 12 Apr 2016 15:25:00 +0200<br>> From: santiago@crfreenet.org<br>> To: pandawithrobotlegs@outlook.com<br>> CC: bird-users@network.cz<br>> Subject: Re: iBGP unreachable<br>> <br>> On Tue, Apr 12, 2016 at 11:21:15AM +0200, Panda RoboLegs wrote:<br>> > Hello,<br>> > <br>> > there is no IGP. I thought that I can resolve the BGP-Next-Hop via static default gateway (0.0.0.0/0).<br>> > It seems that is not possible.<br>> > Does anyone have a link where it is written that BGP next-hop is not resolvable via static default gw?<br>> <br>> Hi<br>> <br>> The default route could be used, but the problem here is that next hops<br>> are resolved by more specific routes that arrive through BGP, so you get<br>> a cycle.<br>> <br>> One solution is to put BGP routes to a different routing table than<br>> default route / IGP routes and use 'igp table' option in BGP protocols to<br>> specify the second table.<br>> <br>> Another workaround is just to override gw or bgp_next_hop in the import<br>> filter, as you already found.<br>> <br>> -- <br>> Elen sila lumenn' omentielvo<br>> <br>> Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org)<br>> OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)<br>> "To err is human -- to blame it on a computer is even more so."<br></div> </div></body>
</html>