<div dir="ltr"><div><div><div><div>Hi <span><font color="#888888">Baptiste,<br><br></font></span></div><span><font color="#888888">Thanks for the Response,<br><br></font></span></div><span><font color="#888888">Done the changes as you specified on gre-vpn interface configuration.<br><br>auto gre-vpn<br>iface gre-vpn inet tunnel<br> mode gre<br> address 10.200.206.249<br> endpoint 10.200.206.4<br> local 10.200.206.5<br> ttl 255<br> netmask 255.255.255.254<br><br><br><br><br><br></font></span></div><span><font color="#888888"><b><span style="color:rgb(0,0,0)">Birdc status</span></b><br><br>BIRD 1.4.5 ready.<br>bird> show protocols all v1<br>name proto table state since info<br>v1 BGP master start 21:28:24 Active Socket: No route to host<br> Preference: 100<br> Input filter: ACCEPT<br> Output filter: ACCEPT<br> Routes: 0 imported, 0 exported, 0 preferred<br> Route change stats: received rejected filtered ignored accepted<br> Import updates: 0 0 0 0 0<br> Import withdraws: 0 0 --- 0 0<br> Export updates: 0 0 0 --- 0<br> Export withdraws: 0 --- --- --- 0<br> BGP state: Active<br> Neighbor address: 10.200.206.250<br> Neighbor AS: 65531<br> Start delay: 5/5<br> Last error: Socket: No route to host<br><br><br><br><br></font></span></div><span><font color="#888888"><b><span style="color:rgb(0,0,0)">Bird Configuration</span></b><br><br>protocol kernel {<br>persist; # Don't remove routes on bird shutdown<br>scan time 20; # Scan kernel routing table every 20 seconds<br>export all; # Default is export none<br>}<br><br>protocol direct direct1 {<br>export all;<br>}<br><br>protocol device {<br>scan time 10; # Scan interfaces every 10 seconds<br>export all;<br>}<br></font></span><div><span><font color="#888888"><br>protocol bgp v1 {<br>#table clos;<br>local as 65530;<br>source address 10.200.206.249;<br>neighbor 10.200.206.250 as 65531;<br>multihop 10;<br>import all;<br>export all;<br>}<br><br><br></font></span></div><div><span><font color="#888888"><b><span style="color:rgb(0,0,0)"><span style="font-family:comic sans ms,sans-serif">Logs:</span></span><br></b>15-09-09 21:31:50 <TRACE> v1: Initializing<br>2015-09-09 21:31:50 <TRACE> v1: Starting<br>2015-09-09 21:31:50 <TRACE> v1: State changed to start<br>2015-09-09 21:31:50 <TRACE> v1: Started<br>2015-09-09 21:31:50 <TRACE> v1: Connect delayed by 5 seconds<br>2015-09-09 21:31:55 <TRACE> v1: Connecting to 10.200.206.250 from local address 10.200.206.249<br>2015-09-09 21:31:55 <TRACE> v1: Connection lost (No route to host)<br>2015-09-09 21:31:55 <TRACE> v1: Connect delayed by 5 seconds<br>2015-09-09 21:31:59 <TRACE> v1: Connecting to 10.200.206.250 from local address 10.200.206.249<br>2015-09-09 21:31:59 <TRACE> v1: Connection lost (No route to host)<br>2015-09-09 21:31:59 <TRACE> v1: Connect delayed by 5 seconds<br>2015-09-09 21:32:05 <TRACE> v1: Connecting to 10.200.206.250 from local address 10.200.206.249<br>2015-09-09 21:32:05 <TRACE> v1: Connection lost (No route to host)<br>2015-09-09 21:32:05 <TRACE> v1: Connect delayed by 5 seconds<br></font></span></div><div><span><font color="#888888"><br><br><br></font></span></div><div><span style="color:rgb(0,0,0)">Though i see the same issue of No Route to host, Please let me know which part i have missed here.<br><br><br></span></div><div><span style="color:rgb(0,0,0)">Thanks,<br></span></div><div><span style="color:rgb(0,0,0)">Ajay<br></span></div><div><div><span><font color="#888888"><br></font></span></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 8, 2015 at 1:06 AM, Baptiste Jonglez <span dir="ltr"><<a href="mailto:baptiste@bitsofnetworks.org" target="_blank">baptiste@bitsofnetworks.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<span class=""><br>
On Mon, Sep 07, 2015 at 08:33:15PM +0530, Ajay Raut ( Tech Ops ) wrote:<br>
</span><span class="">> I m trying to run BGP through the GRE tunnel, Tunnel is working fine.<br>
<br>
</span><span class="">> auto gre-vpn<br>
> iface gre-vpn inet tunnel<br>
> address 10.200.206.249<br>
> mode gre<br>
> endpoint 10.200.206.6<br>
> dstaddr 10.200.206.250<br>
> local 10.200.206.4<br>
> ttl 255<br>
> netmask 255.255.255.252<br>
<br>
</span>You have redundant information here: "dstaddr 10.200.206.250" will insert<br>
a /32 route towards 10.200.206.250. But since you configured<br>
<a href="http://10.200.206.249/30" rel="noreferrer" target="_blank">10.200.206.249/30</a> on the interface, you should already be able to reach<br>
10.200.206.250, since the kernel will create the route <a href="http://10.200.206.248/30" rel="noreferrer" target="_blank">10.200.206.248/30</a><br>
through the tunnel.<br>
<br>
This could be the source of your issue, since (IIRC) Bird sometimes has<br>
trouble with peers that are reachable with a /32 route.<br>
<br>
If removing the /32 route doesn't work, maybe adding a "protocol device"<br>
and "protocol direct" would solve the issue.<br>
<span class="HOEnZb"><font color="#888888"><br>
Baptiste<br>
</font></span></blockquote></div><br></div>
<br>
<p>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------</p><p>This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although Flipkart has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments</p>