L3 mode means there is no L2 header. Both ends need to agree to that.
/neale
From: vpp-dev@lists.fd.io on behalf of David Gohberg via
lists.fd.io
Date: Sunday, 6 February 2022 at 15:57
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VXLAN overlay routing
Hi,
I'm not interested in bridging so
I've managed to setup VXLAN forwarding using the BVI approach, and have a
question regarding the overlay VRF.
when I create a vxlan tunnel using:
create vxlan tunnel src 11.11.11.3 dst 100.0.0.2 vni 50 encap-vrf-id 1
decap-next l2
encap-vrf-id 1 is the underlay VRF. From what I can see, after
Hi,
I'm not interested in bridging so I tried creating the tunnels in L3 mode
and perform routing between VNI 50 and VNI 70 using 2 linux namespaces :
>
> create loopback interface
> set interface mac address loop0 02:10:18:34:9f:cd
> set interface ip address loop0 11.11.11.3/24
> set int l2
Date: Friday, 4 February 2022 at 15:15
To: David Gohberg
Cc: vpp-dev
Subject: Re: [vpp-dev] VXLAN overlay routing
Hi,
as in the article mentioned at the link
https://wiki.fd.io/view/VPP/Using_VPP_as_a_VXLAN_Tunnel_Terminator - you can
use bridge domain with BVI.
Petr
pá 4. 2. 2022 v 14:52
Hi,
as in the article mentioned at the link
https://wiki.fd.io/view/VPP/Using_VPP_as_a_VXLAN_Tunnel_Terminator - you
can use bridge domain with BVI.
Petr
pá 4. 2. 2022 v 14:52 odesílatel David Gohberg napsal:
> Hello,
>
> All of the VXLAN use cases I've found make VPP act as a VXLAN endpoint,
Hello,
All of the VXLAN use cases I've found make VPP act as a VXLAN endpoint, example:
https://wiki.fd.io/view/VPP/Using_VPP_as_a_VXLAN_Tunnel_Terminator
The packet is either going through vxlan encap or decap. What I want is to have
a packet
flow that:
1. performs vxlan decap -> routing on
