On Sat, Oct 11, 2025 at 08:46:00AM +1100, William via Bird-users wrote:

Hi Ondrej,

Thanks for the fast reply!  Just noticed the assorted typo's in the email.

On 10/10/2025 11:42 pm, Ondrej Zajicek wrote:

On Fri, Oct 10, 2025 at 06:52:28PM +1100, William via Bird-users wrote:

Hi BIRDians,
Been tinkering with EPVN in (built from git on Debian 13.1) hooked into an
Arista vEOS-LAB network, with an IPv6 underlay.

Hi

I am glad to hear someone is playing with it. Do you use the 'evpn' branch?

Yes I'm using the evpn branch:

BIRD v2.13.1-161-gc5c9bd81-x ready.

You could also try more recent branch 'oz-evpn' (although the following
patch related to VNIs is also not included there).


There are some configuration changes in this branch, encapsulation-specific options are in its own subblock:

protocol evpn {
    eth { table etab2; };
    evpn;

    encapsulation vxlan {
        tunnel device "vxlan2";
        router address 10.1.1.1;
    };

    rd 1:12;
    route target (rt, 1, 0);

    tag 2;
    vni 12;
};

<snip>

Gotta love standards!  So that brings an interesting side case I wouldn't have
thought of - the "usable" VNI range is trimmed due to this?

No, not really. It is just that EVPN/MPLS (RFC 7432) uses high 20 bits
out of 24, while EVPN/VXLAN uses full 24 bits. But the BIRD EVPN BGP does
not really care about whether it is MPLS or VXLAN (it could be any encapsulation
if it is just an EVPN route reflector).

The attached patch switches BGP code to use full 24 bits.

<snip>

rd / route distinguisher? It works for me even there:

protocol evpn {
    ...
#   rd 1:13;
    rd 1005001:10040;
    route target (rt, 1, 0);
    ...
}

Virus-free.www.avast.com