vrf configuration with same addresses

[Semion Lisyansky]

Most chances that BGP session was initiated from BIRD

cat /etc/issue
Ubuntu 18.04 LTS \n \l
uname -r
4.19.0-041900rc7-generic

#VRF vrf01
ipv4 table table_vrf01;

protocol kernel kernel_vrf01 {
        vrf "vrf01";
        kernel table 101;
        scan time 2;
        ipv4 {
                table table_vrf01;
                import none;    # Default is import all
                export all;     # Default is export none
        };
        merge paths yes;
        learn on;               # Learn all alien routes from the kernel
}

protocol direct direct_vrf01 {
        vrf "vrf01";
        ipv4 { table table_vrf01; };
        interface  "swp32.101";
        interface  "swp17.201";
        interface  "swp18.301";
        interface  "vrf01";
}

protocol static static_vrf01 {
        vrf "vrf01";
        ipv4 { table table_vrf01; };
}

protocol bgp bgp_vrf01_n1 {
        vrf "vrf01";
        local as 65034;
        bfd yes;
        graceful restart;
        neighbor 191.34.1.4 as 65001;
        ipv4 {
                table table_vrf01;
                import all;
#                export all;
                export where source = RTS_BGP;
        };
}

protocol bgp bgp_vrf01_n2 {
        vrf "vrf01";
        local as 65034;
        bfd yes;
        graceful restart;
        neighbor 192.34.1.4 as 65001;
        ipv4 {
                table table_vrf01;
                import all;
#                export all;
                export where source = RTS_BGP;
        };
}

protocol bgp bgp_vrf01_ixia1 {
        local as 65034;
#        bfd yes;
        neighbor 190.34.32.101 as 65134;
        graceful restart;
        ipv4 {
                table table_vrf01;
                import all;
                export all;
        };
}

Don't have possibility to compile new version

--
Semion Lisyansky


On Mon, Nov 5, 2018 at 4:49 PM Ondrej Zajicek <santiago at crfreenet.org>
wrote:

> On Mon, Nov 05, 2018 at 03:05:17PM +0200, Semion Lisyansky wrote:
> > Hi,
> >
> > Please find below requested info. Some omitted because of size
> > You may clearly see the issue on 1st show
>
> Thanks for info.
>
> You are using single-hop EBGP, therefore next hop is not resolved
> through a routing table, but directly through interface table,
> but still it should take into account VRF protocol specified
> by the BGP protocol.
>
> I guess setting 'gateway recursive' BGP option would fix the issue,
> but that is just workaround, it should work even without it.
>
> Could you try compile and run current 'int-new' branch from GIT?
> It has plenty of fixes related to neighbor cache, which may be
> related.
>
> Could you also show your config for bgp_vrf01_ixia1 protocol?
> That was not in the config from original post.
>
> It may be useful to know if your established BGP sessions were incoming
> or outgoing. Could you check that using netstat/ss?
>
> Also, what is your kernel versions? Older kernels have limited support
> for VRF, but not sure if that is related.
>
> --
> Elen sila lumenn' omentielvo
>
> Ondrej 'Santiago' Zajicek (email: santiago at 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."
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20181105/d966d930/attachment.html>