Re: Running Bird bgp through GRE tunnel

[Ondrej Zajicek]

On Wed, Sep 09, 2015 at 09:34:20PM +0530, Ajay Raut ( Tech Ops ) wrote:
> Hi Baptiste,
> 
> Thanks for the Response,
> 
> Done the changes as you specified on gre-vpn interface configuration.
>
...
> 
> Though i see the same issue of No Route to host, Please let me know which
> part i have missed here.

Hi

To find the problem, it would be useful to know outputs of these commands:

ip addr list
ip route list
birdc show interfaces

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."


signature.asc
Description: Digital signature

Re: Running Bird bgp through GRE tunnel

[Baptiste Jonglez]

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


pgpj1TeJMMKkE.pgp
Description: PGP signature