Hi Baptiste,

Thanks for the Response,

Done the changes as you specified on gre-vpn interface configuration.

auto gre-vpn
iface gre-vpn inet tunnel
        mode gre
        address 10.200.206.249
        endpoint 10.200.206.4
        local   10.200.206.5
        ttl 255
        netmask 255.255.255.254

Birdc status

BIRD 1.4.5 ready.
bird> show protocols all v1
name     proto    table    state since       info
v1       BGP      master   start 21:28:24    Active        Socket: No route to host
Preference:     100
Input filter:   ACCEPT
Output filter: ACCEPT
Routes:         0 imported, 0 exported, 0 preferred
Route change stats:     received   rejected   filtered    ignored   accepted
    Import updates:              0          0          0          0          0
    Import withdraws:            0          0        ---          0          0
    Export updates:              0          0          0        ---          0
    Export withdraws:            0        ---        ---        ---          0
BGP state:          Active
    Neighbor address: 10.200.206.250
    Neighbor AS:      65531
    Start delay:      5/5
    Last error:       Socket: No route to host

Bird Configuration

protocol kernel {
persist; # Don't remove routes on bird shutdown
scan time 20; # Scan kernel routing table every 20 seconds
export all; # Default is export none
}

protocol direct direct1 {
export all;
}

protocol device {
scan time 10; # Scan interfaces every 10 seconds
export all;
}

protocol bgp v1 {
#table clos;
local as 65530;
source address 10.200.206.249;
neighbor 10.200.206.250 as 65531;
multihop 10;
import all;
export all;
}

Logs:
15-09-09 21:31:50 <TRACE> v1: Initializing
2015-09-09 21:31:50 <TRACE> v1: Starting
2015-09-09 21:31:50 <TRACE> v1: State changed to start
2015-09-09 21:31:50 <TRACE> v1: Started
2015-09-09 21:31:50 <TRACE> v1: Connect delayed by 5 seconds
2015-09-09 21:31:55 <TRACE> v1: Connecting to 10.200.206.250 from local address 10.200.206.249
2015-09-09 21:31:55 <TRACE> v1: Connection lost (No route to host)
2015-09-09 21:31:55 <TRACE> v1: Connect delayed by 5 seconds
2015-09-09 21:31:59 <TRACE> v1: Connecting to 10.200.206.250 from local address 10.200.206.249
2015-09-09 21:31:59 <TRACE> v1: Connection lost (No route to host)
2015-09-09 21:31:59 <TRACE> v1: Connect delayed by 5 seconds
2015-09-09 21:32:05 <TRACE> v1: Connecting to 10.200.206.250 from local address 10.200.206.249
2015-09-09 21:32:05 <TRACE> v1: Connection lost (No route to host)
2015-09-09 21:32:05 <TRACE> v1: Connect delayed by 5 seconds

Though i see the same issue of No Route to host, Please let me know which part i have missed here.

Thanks,

Ajay

On Tue, Sep 8, 2015 at 1:06 AM, Baptiste Jonglez <baptiste@bitsofnetworks.org> wrote:

Hi,

On Mon, Sep 07, 2015 at 08:33:15PM +0530, Ajay Raut ( Tech Ops ) wrote:
> I m trying to run BGP through the GRE tunnel, Tunnel is working fine.

> auto gre-vpn
> iface gre-vpn inet tunnel
> address 10.200.206.249
> mode gre
> endpoint 10.200.206.6
> dstaddr 10.200.206.250
> local 10.200.206.4
> ttl 255
> netmask 255.255.255.252

You have redundant information here: "dstaddr 10.200.206.250" will insert
a /32 route towards 10.200.206.250. But since you configured
10.200.206.249/30 on the interface, you should already be able to reach
10.200.206.250, since the kernel will create the route 10.200.206.248/30
through the tunnel.

This could be the source of your issue, since (IIRC) Bird sometimes has
trouble with peers that are reachable with a /32 route.

If removing the /32 route doesn't work, maybe adding a "protocol device"
and "protocol direct" would solve the issue.

Baptiste

------------------------------------------------------------------------------------------------------------------------------------------

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